2024-09-04 Meeting notes
All public Working Group meetings follow the Recording Policy for Open edX Meetings
Date
Sep 4, 2024
https://drive.google.com/file/d/1jVwI-O7rder4GHYvdGG-KeXrBy9qveQF/view?usp=drive_link
https://docs.google.com/document/d/1VcqcvxWd4HO9No81yKHG2OcygOFNE3FisOutPUR_eDQ/edit?usp=drive_link
Participants
@Adam Stankiewicz
Goals
Discussion topics
Time | Item | Presenter | Notes |
---|---|---|---|
| Color tokens, accents | @Adam Stankiewicz | The 2U/edX.org Paragon Elm Theme ( This is a change from the current Paragon theme in that
Discussion
|
| Updates to | @Adam Stankiewicz | [inform] One of the changes in the following PR includes updating the https://github.com/openedx/paragon/pull/3203 Without this change, the CSS variables output from a brand package will not contain references to relevant CSS variables, which limits support for runtime theming of those tokens. Before Brand packages did not include CSS variables in its output, instead having hard coded values (i.e., HEX codes). After When relevant, the output CSS variables will reference its underlying CSS variable, instead of always hardcoding the raw value. Discussion
|
| Composite tokens in | @Adam Stankiewicz | Why? Simpler tokens schema in JSON for theme authors, by combining style properties under a composite token vs. implementing separate tokens.
Impacted token types:
Docs:
Examples: {
"shadow-token": {
"$type": "shadow",
"$value": {
"color": "#00000080",
"offsetX": "0.5rem",
"offsetY": "0.5rem",
"blur": "1.5rem",
"spread": "0rem"
}
}
} Design Tokens Format Module (“Typography”) {
"type styles": {
"heading-level-1": {
"$type": "typography",
"$value": {
"fontFamily": "Roboto",
"fontSize": "42px",
"fontWeight": 700,
"letterSpacing": "0.1px",
"lineHeight": 1.2
}
}
}
} Discussion
|