Document colour roles in the brand baseline, and resolve the gradient and alpha restrictions it contradicts
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 72/100
- Tipo di issue
- Documentazione
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- css, markdown, typescript
- Ambito
- design, documentation
Direzione di ricerca
Leggi .agents/skills/brand-baseline/SKILL.md e confronta le indicazioni sulla palette con i commenti sui ruoli e i token del tema in website/src/css/custom.css. Documenta i ruoli dei colori e segui le tonalità, quindi chiarisci le restrizioni indicate per gradienti e valori alpha e registra la regola del selettore del tema scuro. Il lavoro è completato quando la guida corrisponde agli stili distribuiti e indica chiaramente il ruolo di ogni colore e l’uso consentito.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Page or section
.agents/skills/brand-baseline/SKILL.md (the file that serves as the design system guide) and website/src/css/custom.css.
Issue description
The palette is documented, the way it is used is not, and two of the guide's own restrictions no longer match what the site ships.
The guide lists swatches by name and hex: Genie Blue #2353FF, Midnight #1D1D1B, Moon #F5F3EB, Vanilla Sunset #FEC104, Blazing Amber #FF4B11, Raspberry Blush #F8908F, Caramel Delight #FCE4C6, Rich Black, plus Shadow, Twilight, Winter Steel and Pure White.
What it does not say is what each colour is for. That knowledge currently exists only as comments in custom.css, and nowhere a person or an agent could find it before touching the stylesheet:
| Role | Colour | Light | Dark |
|---|---|---|---|
| Action, links, primary button | Genie Blue | #2353FF |
#4D91FF |
| Text and item rules | Midnight | #1D1D1B |
#F5F3EB |
| Scheduled, as a filled chip with midnight label | Vanilla Sunset | #FEC104 |
#FEC104 |
| Careful (warning callouts), contributor hover ring | Blazing Amber | #C13A0B text, #FF4B11 mark |
#FF8F6B / #F0764F |
| Band surfaces | White and Moon | #FFFFFF / #F5F3EB |
#1D1D1B / #2C2B2B |
| Navbar and footer surfaces | Genie Blue | #2353FF |
#2353FF |
On top of that, five track hues were added during the landing page work and are in no deck at all. Three are the languages' own colours, two are ours:
| Track | Hue | Light | Dark | Contrast on the tab it sits on |
|---|---|---|---|---|
| dApp and smart contracts | Genie Blue | #2353FF |
#4D91FF |
5.6 / 5.47 |
| Infrastructure and DevOps | Raspberry, darkened | #C2185B |
#F8908F |
5.87 / 7.54 |
| Core protocol, Haskell | Haskell purple | #5D4E8C |
#A794DE |
7.16 / 6.38 |
| Core protocol, Rust | Rust orange | #CE422B |
#F0764F |
4.73 / 5.96 |
| Core protocol, Go | Go cyan, darkened | #0B87AD |
#45C4E6 |
4.13 / 8.27 |
Three points where the guide and the build disagree:
"No gradients."Resolved in3abd1f3: the footer is solid Shadow#2C2B2B, and the dead.herogradient rule is deleted.custom.cssnow contains nolinear-gradientat all.- "No transparency or blend modes. Solid fills only." This one is open.
custom.cssnow contains 29rgba()declarations, after the footer rebuild in8a5e4b8removed thergba(255, 255, 255, 0.8)copyright rule along with the old footer, and Infima's alert components ship anrgbahighlight. The warning alert has been given a solid replacement, the other admonitions have not. The track tints usecolor-mix, which resolves to an opaque colour, so those are compliant in effect. - Semantics are missing entirely. Nothing states that blue means "you can act on this", that midnight is structure, that vanilla is reserved for "scheduled", or that blazing now means "careful" and the footer. Without that, a future change can reuse vanilla for decoration and the chip stops meaning anything.
Not urgent and nothing is broken for a reader. The cost is drift: every colour decision of the last week exists in one stylesheet's comments, and the guide that governs them documents swatches without saying what any of them is for.
Proposed change
- Add a
## Colour rolessection to.agents/skills/brand-baseline/SKILL.md: one row per job, with the light and dark value and the contrast each clears, plus the rule that a colour carries at most three meanings before it becomes decoration. - Add the five track hues to the palette section, marked as language-derived except the two that are ours, with the note that they are marks and washes only, never text.
- Decide the gradient question once: either drop the restriction and document the footer gradient as the sanctioned exception, or flatten the footer to a solid
#1A202Cand delete the dead.herogradient rule. - Same for alpha: allow it for text at 80% on the dark footer, or convert those to solid values.
- Note in the guide that dark-theme tokens must be declared on
html[data-theme='dark'], because Infima declares its own dark tokens on that selector and a bare[data-theme='dark']block loses every contested token silently. That bug was live until it was found: the warning callouts stayed Infima mustard while the brand values sat unused.
This is a concrete sub-item of #300, which proposes the token baseline and the brand assets page. The palette exists today; the roles and the conflict resolution are what is missing.
Checks
- I searched existing issues and discussions
- This is about documentation (not a feature request or bug)
- Lingua principale
- TypeScript
- Stelle
- 13
- Fork
- 24
- Merge medio
- 1g 15h
- PR unite (30g)
- 20
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di IntersectMBO/developer-experience
-
documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 90/100
IntersectMBO/developer-experience#363 ·
I maintainer di solito rispondono entro 1 giorno
-
documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
IntersectMBO/developer-experience#362 ·
I maintainer di solito rispondono entro 1 giorno
-
documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 90/100
IntersectMBO/developer-experience#360 ·
I maintainer di solito rispondono entro 1 giorno
-
Verify session: UI and Smart Contract Interaction (Q2 2026, 16-ui-smart-contract-interaction)Apertadocumentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 92/100
IntersectMBO/developer-experience#359 ·
I maintainer di solito rispondono entro 1 giorno
-
Verify session: dApp Architecture from Wallet to Backend (Q2 2026, 15-dapp-architecture-demo)Apertadocumentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
IntersectMBO/developer-experience#358 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di IntersectMBO/developer-experience
Issue simili
-
area:cards enhancement ready-for-agent
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
fil-donadoni/tolaria#8883 ·
I maintainer di solito rispondono entro 1 giorno
-
xsd:integer cast from a string rejects negative numbers, a leading + and surrounding whitespaceApertabug 🐛
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
comunica/comunica#1960 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Waiting for: Product Owner
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
getsentry/sentry-javascript#26203 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
bytedance/flowgram.ai#1235 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
devswha/herdr-web-ui#3325 ·