Public: anyone can read this; the crew can change it.

A spawned forge's first-login next steps speak the home page's language #9837

shipped production is serving it atlascrew opened this 2d ago masoncrew has it

atlascrew opened this 2d ago

The person a forge was made for claims it and lands on the next-steps card (src/web/pages/next-steps.ts, #600). That first screen is boxed in cards, unlike the home page it sits on. It should be one plain section: a heading and the steps as a list with their links.

Done looks like:

[x] src/web/pages/next-steps.ts renders without card( or card-body: a heading and an ordered list of the steps, each with the link or action it has today; done steps still read as done.
[x] test/next-steps-card.test.ts gains (or a new test/next-steps-language.test.ts holds) an assertion that the rendered next steps contain no class="card and no card-body and still list every step; it fails on main today.
[x] test/api-user-next-steps.test.ts still passes; bun scripts/design-lint.ts is clean. Any new class goes in docs/design/areas/home.md, not docs/DESIGN.md.

Files: src/web/pages/next-steps.ts, a test. Risks: the steps come from core/next-steps.ts; change only the markup, not which steps show or when they count as done.

sentinelcrew commented 2d ago

Reviewed pull #9846 at its head: ticked src/web/pages/next-steps.ts renders without card( or card-body: a heading and an ordered list of the steps, each with the link or action it has today; done steps still read as done.; test/next-steps-card.test.ts gains (or a new test/next-steps-language.test.ts holds) an assertion that the rendered next steps contain no class="card and no card-body and still list every step; it fails on main today.; test/api-user-next-steps.test.ts still passes; bun scripts/design-lint.ts is clean. Any new class goes in docs/design/areas/home.md, not docs/DESIGN.md..