Translations · CC BY 4.0

Translate a guide, keep the credit

All 91 guides are published under CC BY 4.0, which means translation is explicitly allowed — you do not need to ask. What you do need is the attribution line, which is why the workflow below is short and the glossary is long.

Honest status: there are zero community translations today. The Spanish landing page at /es is ours, written to test the localisation route — it is not a community contribution and is not counted as one below.

The workspace

Translation is a form of remixing, and remixing is a form of review: the best translation note is the one that tells us where the original was unclear. Translate the file faithfully, then list the sentences you had to invent a term for.

Pick a guide, and say which locale you are taking — a comment is enough, one translator per locale per guide avoids collisions.
Translate the prose, the headings and the alt-equivalents. Do not translate slugs, component names, model names or the audit numbers.
Keep the attribution block and the CC BY 4.0 note in the translated file, plus a line saying it is a translation of the English original.
Include the glossary decisions you made, so the next translator of that locale does not re-litigate them.
Send it through the submit flow with the guide slug in the “based on” field.

Status by guide · all locales

Status by guide · all locales — data table
Guide	Minutes	Status
Build a hero that breathes — in 20 minutes	20	needs a translator
Easing is a language — a field guide to curves	12	needs a translator
Write AI prompts that reproduce — not ones that 'inspire'	15	needs a translator
Before you copy that component: the a11y checklist	8	needs a translator
Glass is a material — not a trend	10	needs a translator
3D that costs nothing: CSS depth in five moves	4	needs a translator
Scroll choreography that respects the reader	5	needs a translator
Gradients that don't look cheap	9	needs a translator
The 60fps handshake: what devtools is really telling you	10	needs a translator
Design the empty state first	9	needs a translator
Easing cheatsheet, deep dive	11	needs a translator
Springs are not easings	12	needs a translator
The choreography question: story or decoration?	8	needs a translator
Micro-interactions that pay rent	9	needs a translator
Will-change is a promise — keep it or break it	10	needs a translator
Why 60fps feels like 24fps	11	needs a translator
Animating on the GPU without asking	12	needs a translator
Scroll speed is a type choice	9	needs a translator
The 200ms click window	8	needs a translator
Reduced motion beyond the switch	11	needs a translator
Glass, part two: when glass belongs	10	needs a translator
Shadow discipline	9	needs a translator
Grid systems that don't shout	8	needs a translator
Fluid type without magic numbers	9	needs a translator
CSS nesting, now	8	needs a translator
Container queries cookbook	10	needs a translator
:has() is finally useful	9	needs a translator
scroll-timeline, honestly	10	needs a translator
In defence of the button	8	needs a translator
Colour contrast you can compute	10	needs a translator
Writing a brief the model can't ignore	10	needs a translator
The retry loop: from fidelity 84 to 92	9	needs a translator
One palette, three moods	8	needs a translator
When to say 'no gradients' in a prompt	8	needs a translator
Model personality drift	9	needs a translator
Design tokens inside prompts	10	needs a translator
Prompting for reduced motion	8	needs a translator
From prompt to component	11	needs a translator
The 5-line prompt myth	9	needs a translator
Fidelity is a claim	10	needs a translator
The keyboard walk	9	needs a translator
Screen-reader poetry	8	needs a translator
Focus order is layout	8	needs a translator
Contrast on brand colours	9	needs a translator
Touch targets beyond 44px	8	needs a translator
Autoplay is a decision	9	needs a translator
Designing for cognitive load	10	needs a translator
Forms that fail kindly	9	needs a translator
The invisible header	8	needs a translator
Testing with one hand	9	needs a translator
Building a personal UI library	11	needs a translator
Copy-paste guilt is a feature	8	needs a translator
Designing in the open	9	needs a translator
The first 90 days of a content site	10	needs a translator
Performance budgets for solo builders	9	needs a translator
Portfolio pieces that get you hired	10	needs a translator
Freemium that isn't a lie	9	needs a translator
Animated storytelling for non-profits	9	needs a translator
Dark mode is a design system	11	needs a translator
Naming is design	9	needs a translator
Reading a diff as a reviewer	9	needs a translator
Why your hero LCP is a font problem	7	needs a translator
The three questions a changelog must answer	6	needs a translator
Colour tokens are an API	8	needs a translator
Empty states are onboarding	6	needs a translator
A form is a conversation	8	needs a translator
Tables that survive 10,000 rows	9	needs a translator
When animation is documentation	7	needs a translator
The cost of one dependency	8	needs a translator
Version numbers people trust	7	needs a translator
Writing error messages that name the fix	6	needs a translator
A11y is a spec, not a vibe	10	needs a translator
Lighthouse is a smoke test	7	needs a translator
The layout shift that wasn't	6	needs a translator
Design review for engineers	6	needs a translator
Search is a product	8	needs a translator
Dark mode is a theme, not an inversion	7	needs a translator
Progressive disclosure on long pages	7	needs a translator
The economics of a copy button	5	needs a translator
Feature flags are communication	8	needs a translator
Charts without a chart library	6	needs a translator
Naming a component	6	needs a translator
The retriable request	7	needs a translator
Licensing for frontend snippets	6	needs a translator
Ship the boring version first	7	needs a translator
Anatomy of a false claim	8	needs a translator
What a build cannot see	7	needs a translator
The rule that had to be first	6	needs a translator
Recorded numbers need labels	6	needs a translator
Auditing the crawl surface	7	needs a translator
Five passes over a finished site	8	needs a translator

The zero column is the honest one. We would rather show 91 rows reading zero than seed the table with shadow translations to look international.

Do-not-translate glossary

Motif UI

Never translated — it is the name.

Translated brands read as a different product.

audit score / a11y score

Keep the English term in Latin scripts; gloss it once on first use.

It is a link target and a label on every card.

fidelity

Translate, but keep the English in brackets on first use.

Every prompt page is scored with this exact word.

component slugs (combo-box, halo-button…)

Never translated or re-cased.

They are URLs.

reduced motion

Use the platform term of your locale, not a literal translation.

It is an OS setting name users already see.

bundle budget

Translate the phrase, keep the KB numbers exactly as published.

The numbers are the claim.

Translation credits work exactly like remix credits: the English original keeps its author, the translation adds a translator name, and both stay on the page.

Attribution policy Send a translation →