How to Publish a Page Without Breaking the Site.

Write the page in the submit-here directory so drafts stay separate from published history and generated site data. The draft should call approved blocks and fill their inputs rather than invent new presentation in markdown.

One draft file should lead to one clear publishing decision.

Use npm run content -- check content/submit-here/your-file.md to validate the draft. The checker catches bad frontmatter, invalid block usage, and route collisions before the change becomes trusted.

That validation step is what keeps fast editing from turning into silent production mistakes.

Use npm run content -- submit content/submit-here/your-file.md for a new page. Use npm run content -- edit content/submit-here/your-file.md when you are revising an existing page.

Published source is mirrored into the archive and the live site data is rebuilt from there. That means the agent can help write the draft, but the trusted source only changes when the reviewed command runs.

If someone writes to the wrong place or mangles generated files, the system quarantines that work into recovered drafts instead of letting it disappear or leak live.

That is a practical requirement when people and AI tools are both touching the same repository.