As a developer I can specify custom tokens so that the style editor provides a form to edit those tokens instead of the Liferay-standard ones (token definition schema)

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: Liferay Themes > Classic, Page Templates > Display Page Templates, ~ [Archived] Themes Infrastructure
• Labels:
  • echo-board-out
  • exclude_from_metrics
  • fc_20_06
  • fc_20_07
• Epic Link: fi-theme-styles-support
• Sprint: S03E26 - Cape Town, S03E27- Athens
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/91387

As part of our POC, we've been hardcoding which design tokens should appear in the UI.

The goal of this story is to describe how design tokens should be defined and translated into UI.

Acceptance Criteria:

• We have a clear and simple definition (json, xml...) for design tokens that includes
  • Type of token (colour, string, number)
  • Label
  • Related CSS variable (or custom style template?)
  • Repeatable
  • Layout (see designs)