Step 6 of 6
Validate and Submit
Run the authoring checks, inspect the complete Guide at desktop and mobile sizes, and prepare a focused pull request.
Run the focused authoring checks before opening a pull request:
pnpm format:write
pnpm content:validate
pnpm typecheck
pnpm lintThe content validator rejects invalid metadata, duplicate slugs, missing Guide steps, mismatched step order, broken internal references, unapproved MDX components, imports, exports, and executable JavaScript.
Preview the complete experience
pnpm devOpen the Guide overview and every step. Check both a desktop viewport and a narrow mobile viewport.
- The overview promises a specific, observable outcome
- Every manifest entry has one matching step document
- Previous and next navigation follows the intended order
- Code can be copied and run as written
- Every step ends with a result the reader can verify
- Callouts and structured components are used intentionally
- The Guide remains readable at a 390px viewport
- All automated checks pass
Prepare the pull request
Keep the pull request focused on one Guide. Explain its intended reader, promised outcome, verification environment, and any parts that need especially close technical review.
When review is complete, add publishedAt, update lastVerified, change the status to published, and rerun the checks.
Step 6
Ready to continue?
Mark this step complete when you have finished the checks above.
Checking saved progress…