chore(slides): align Aspire theme tokens with official brand spec#37
Merged
chore(slides): align Aspire theme tokens with official brand spec#37
Conversation
Aligns slide CSS variables with https://microsoft.github.io/aspire-brand/. The previous values had drifted to a 'lavender' palette: --aspire-magenta and --aspire-flamingo were lavender-purples (#9d72f8 / #b793fa) rather than the brand's true magenta (#b30f87) and coral flamingo (#f65163). The 135deg purple→magenta gradient on .gradient slides therefore rendered as purple→lavender instead of the brand's striking purple→pink. Token corrections (both light + dark themes): - --aspire-purple #864df5 → #512bd4 - --aspire-magenta #9d72f8 → #b30f87 - --aspire-flamingo #b793fa → #f65163 - --aspire-cyan #28c2d1 → #0b7e84 - --aspire-secondary #b9aaed → #b9aaee - --aspire-muted #dbd3f4 → #dcd5f6 - --aspire-grey #dcdfe6 → #dce0e8 - --aspire-black #1f1e31 → #1f1e33 - --aspire-white #fefffe → #ffffff - --aspire-yellow (added) #9b8308 Plus the four official supporting gradients as CSS variables for re-use in future slides: - --aspire-gradient-purple-magenta - --aspire-gradient-blue-purple - --aspire-gradient-flamingo-purple - --aspire-gradient-purple-cyan --aspire-primary (#7455dd) and --aspire-blue (#0078d7) were already correct and left untouched. ## Validation Built with marpteam/marp-cli docker (latest), template=bare, then walked all 32 slides with Playwright at 1280×720 logical canvas. Per-slide overflow audit passed: no element exceeds the 1280×720 viewport. The .gradient title/wrap-up slides now render the on-brand purple→true-magenta diagonal — confirmed via vision review of the exported PNGs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Aligns
slides/themes/custom-aspire-{light,dark}.csswith https://microsoft.github.io/aspire-brand/.Problem
--aspire-magentaand--aspire-flamingohad drifted to lavender-purples (#9d72f8 / #b793fa) instead of the brand's true magenta (#b30f87) and coral flamingo (#f65163). The 135°purple→magentagradient on.gradientslides therefore rendered as purple→lavender instead of the brand's striking purple→deep-pink.Token corrections (both light + dark)
--aspire-purple--aspire-magenta--aspire-flamingo--aspire-cyan--aspire-secondary--aspire-muted--aspire-grey--aspire-black--aspire-white--aspire-yellow--aspire-primary(#7455dd) and--aspire-blue(#0078d7) were already correct.Added
The four official supporting gradients as CSS variables:
--aspire-gradient-purple-magenta(#7455dd → #b30f87)--aspire-gradient-blue-purple(#0078d7 → #7455dd)--aspire-gradient-flamingo-purple(#f65163 → #7455dd)--aspire-gradient-purple-cyan(#7455dd → #0b7e84)Validation
Built with
marpteam/marp-clidocker (latest), templatebare, then walked all 32 slides with Playwright at the 1280×720 logical canvas:section.purple(slide 18 "Demos") still uses--aspire-primary, unchangedNo content / Slides.md changes; CSS-only.