Repository navigation
Conversation
doc/ pages now carry a schema-validated frontmatter block, so a plain markdown file dropped in fails the Astro content collection and never reaches the Worker. Documents the exact frontmatter contract, slug/parent/ sort/visibility rules, what a body may contain (no raw HTML), the add/rename/delete recipes, the gates, and the split between the live Worker deploy and the still-running GitHub Pages pipeline. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FgJHpbomqG9v26obEFEonp
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a dedicated, AI-agent-focused guide for safely editing doc/*.md handbook pages under the Astro content-collection constraints, and links it from CLAUDE.md so it’s discoverable before any doc/ edits.
Changes:
- Add
CONTENT-GUIDE.mddocumenting required frontmatter schema, slug/parent/sort/visibility rules, supported Markdown features, and content workflows. - Document required local gates (
pnpm check/test/guard/build) and explain how content ships via the Cloudflare Worker vs the legacy VitePress Pages pipeline. - Update
CLAUDE.mdto point contributors/agents toCONTENT-GUIDE.mdbefore editingdoc/*.md.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| CONTENT-GUIDE.md | New guide describing the content schema contract, authoring rules, and release pipeline for doc/*.md pages. |
| CLAUDE.md | Adds an upfront pointer to the new content editing guide for doc/*.md changes. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| | `parent` | no | Slug of the parent page, **in the same section**. A parent in another section (or a missing one) silently makes the page top-level. Nesting is capped at 4 levels. | | ||
| | `nav_label` | no | Quoted string; sidebar label when it should differ from `title`. Empty string = fall back to `title`. | | ||
| | `sort` | no (defaults 0) | Number. Orders pages within a section **and** orders the sections themselves (a section sits where its lowest-`sort` page falls). | | ||
| | `visibility` | no (defaults `internal`) | `public` (anyone) or `internal` (signed-in only). **Fails closed** — a typo means internal. | |
| - Allowed: GitHub-flavoured markdown (tables, task lists, strikethrough), | ||
| fenced code, `:::info` / `:::tip` / `:::warning` / `:::danger` / `:::note` / | ||
| `:::caution` / `:::important` / `:::details` callouts (with or without a | ||
| label), ` ```mermaid ` diagrams, and `[[TOC]]` on its own line for an |
This was referenced Aug 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Superseded by #105, which carries the identical two-file change on a branch opened from issue #104. Closing this one.
🤖 Closed by Claude Code