Public: anyone can read this; the crew can change it.
One design language: every page, card and word at the home page's standard #9433
Parked by the crew: the check stayed red through 2 automatic tries (pull #9463 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Reviewed pull #9535 at its head: left open: docs/DESIGN.md opens with these principles in under 30 lines, with the home page and the Security settings page as worked examples, and the design check enforces what it can. — Not in this pull.; Every page has a meaningful <title>, description, og:title, og:description, og:image and canonical URL. A test fails any public page without them. Repository and app descriptions that are empty or jargon get a plain fallback, and a description no longer ends in " · live." — Not in this pull.; Web standards are complete and tested: robots.txt, sitemap.xml, the manifest, /.well-known/security.txt, llms.txt, favicons and theme colors, structured data for the site and software, and humans.txt or its equivalent if wanted. — Not in this pull.; The remaining dense settings pages (Tokens, Crew, Subscriptions, Usage) get the same rewrite as Security and Limits, and are measurably shorter. — Not in this pull.; Signed-in home, repository, app, issue and pull pages are brought into the same language one at a time, each with before and after screenshots at 1440 and 390 in light and dark. — Not in this pull.; The crew's reviewer checks a pull touching the UI against these principles, and the crew brief points to them, so new work speaks the same language. — Not in this pull..
Left open after pull #9535 landed: 7 unticked items remain (docs/DESIGN.md opens with these principles in under 30 lines, with the home page and the Security settings page as worked examples, and the design check enforces what it can.; Every page has a meaningful <title>, description, og:title, og:description, og:image and canonical URL. A test fails any public page without them. Repository and app descriptions that are empty or jargon get a plain fallback, and a description no longer ends in " · live."; Share cards (src/web/pages/og.ts) match the home page's type and restraint. No "PAGE" label, nothing cut off mid-sentence, and no edge strip on the left. Each card is checked as an image in a test.; …). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Split: #9576 (DESIGN.md principles), #9577 (meta on every page), #9578 (share cards), #9579 (web standards), #9583 (dense settings pages), #9584–#9588 (signed-in home, repository, app, issue and pull pages, one each), #9589 (reviewer checks UI pulls against the principles).
The owner, 2026-11-05: "make sure the og metadata and all the webstandards are up to the same standard as the home page is now. that should flow into the roadmap as well so when usage is back we start speaking in a cohesive design language."
The reference is the public home page (
src/web/studio/home.ts, shipped in 0.7.401 to 0.7.403) and the design study behind it: one confident sentence, the real product as the visual, generous rhythm, one background, one text color and at most one accent, few borders, rows over boxes, and plain words that a grandma, a gamer, a developer and an artist each get. Words followdocs/WRITING.md; the message follows Open Platform's messaging ("Software for what you're building. Yours to keep.").Done when:
docs/DESIGN.mdopens with these principles in under 30 lines, with the home page and the Security settings page as worked examples, and the design check enforces what it can.<title>, description,og:title,og:description,og:imageand canonical URL. A test fails any public page without them. Repository and app descriptions that are empty or jargon get a plain fallback, and a description no longer ends in " · live."src/web/pages/og.ts) match the home page's type and restraint. No "PAGE" label, nothing cut off mid-sentence, and no edge strip on the left. Each card is checked as an image in a test.robots.txt,sitemap.xml, the manifest,/.well-known/security.txt,llms.txt, favicons and theme colors, structured data for the site and software, andhumans.txtor its equivalent if wanted.