BUG-035
ID:BUG-035Status:fixed

Five create-refrakt starters link a nav item to a page that does not exist

Found by WORK-634 (#695), which scaffolds a project in its tests.

The starters ship content/docs/getting-started.md, but five of the six _layout.md files list the nav item as getting-started instead of docs/getting-started:

Severity:majorMilestone:v0.41.3Source:SPEC-109
changeset-release/main View source
Branches 5
History 5
  1. 65f872e
    Created (fixed)by github-actions[bot]
  2. 6f35356
    Content editedby Claude
    plan: link v0.41.3 bugs to #712
  3. 4503745
    Content editedby Claude
    v0.41.3: a fresh scaffold works, plan history stops scaling with git
  4. abc833f
    Content editedby Claude
    plan: v0.41.3, v0.42.0 and v0.43.0 milestones
  5. c14f915
    Content editedby Claude
    plan: file BUG-035..037 from WORK-634's findings

Steps to Reproduce

  1. npx create-refrakt my-site with the default (SvelteKit) template.
  2. Start the dev server and open any page.

Expected

The nav resolves, and a fresh scaffold builds with no errors or warnings.

Actual

getting-started resolves to no page, and every page reports it.

Fix

Change the nav item to docs/getting-started in the five templates. Also add a scaffold test that builds each template and asserts zero errors, so a template-only drift like this one is caught.

Resolution

Completed: 2026-10-24

Branch: claude/milestone-v0-41-3-1mzttp

What was done

  • packages/create-refrakt/template{,-astro,-eleventy,-next,-nuxt}/content/_layout.md: nav item getting-started → docs/getting-started.
  • packages/create-refrakt/test/scaffold-builds.test.ts (new): scaffolds each of the six targets, loads it with createRefraktLoader, and asserts both pages exist, no error-severity diagnostics, and the nav links /docs/getting-started. Fails on main for the SvelteKit starter.
  • scaffold-project-runes.test.ts: dropped the comment excusing the nav error.

Notes

  • Changeset: .changeset/scaffold-nav-and-html-plugins.md.