Bug Report
Describe the bug
When using a custom bodyOfWork.slug in config, the page doesn't show up after the first deploy even though the build logs say it was created. It only appears after a second deploy/rebuild.
To Reproduce
- Set a custom slug in config.yaml:
bodyOfWork.slug: "archive"
- Run
npm run build and deploy
- Try to access
/archive — 404 or missing from navigation
- Run build again and redeploy
- Now it works
Expected behavior
The body of work page should be accessible after the first build, not require two builds.
Additional context
I think it's a build order issue — the body of work file gets created after the pages index is already generated.
Bug Report
Describe the bug
When using a custom
bodyOfWork.slugin config, the page doesn't show up after the first deploy even though the build logs say it was created. It only appears after a second deploy/rebuild.To Reproduce
bodyOfWork.slug: "archive"npm run buildand deploy/archive— 404 or missing from navigationExpected behavior
The body of work page should be accessible after the first build, not require two builds.
Additional context
I think it's a build order issue — the body of work file gets created after the pages index is already generated.