Skip to content

feat(tokens): add brand gradient ramp for per-product marketing surfaces#3

Merged
ajianaz merged 1 commit into
mainfrom
feat/brand-gradient-ramp
Jul 19, 2026
Merged

feat(tokens): add brand gradient ramp for per-product marketing surfaces#3
ajianaz merged 1 commit into
mainfrom
feat/brand-gradient-ramp

Conversation

@ajianaz

@ajianaz ajianaz commented Jul 19, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds a 3-stop brand gradient ramp to the shared design tokens so per-product marketing surfaces (landing pages, hero sections, CTA strips) no longer hardcode their own palette.

Changes

  • --cc-brand-1 defaults to --cc-mauve (primary brand)
  • --cc-brand-2 defaults to --cc-pink (secondary brand)
  • --cc-brand-3 defaults to --cc-peach (tertiary brand)
  • --cc-brand-gradient auto-composed linear-gradient(120deg, brand-1, brand-2 48%, brand-3)

Products override only the stops they need; the gradient derives automatically.

Why

cora-api PR #34 hardcodes --brand-1: #8b5cf6; --brand-2: #ec4899; --brand-3: #f59e0b for its landing page — colors that don't exist in the Catppuccin palette and create a second source of truth. This token slot centralises that concept.

Backward compatible

No existing tokens changed. Only additions.

Adoption (follow-up PR)

  • cora-api PR #34: replace hardcoded --brand-* with --cc-brand-* override
  • web-landing: optionally wire CTA gradients to --cc-brand-*

- Add --cc-brand-1/2/3 (3-stop gradient ramp) defaulting to mauve/pink/peach
- Add --cc-brand-gradient (auto-composed from the 3 stops)
- Products override only the stops they need; gradient derives automatically
- Adopted by cora-api landing (PR #34) to replace hardcoded brand colors

Backward compatible: no existing tokens changed.
@ajianaz
ajianaz merged commit 6913b83 into main Jul 19, 2026
@ajianaz
ajianaz deleted the feat/brand-gradient-ramp branch July 19, 2026 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant