edit-cratis-docs

Editing a Cratis documentation page

Scope this skill to source files under Documentation/** in the product or contributing repo. Site-level pages in Documentation/web are owned by the Documentation repo.

Cratis docs content lives in each product's own repo under that repo's Documentation/ folder; the published site (in the Documentation repo at Documentation/web/) aggregates them. Editing the wrong copy wastes the work — the per-product folders under web/src/content/docs/ are generated and overwritten.

1. Find the source of truth

Map the page URL to its owning repo:

URL	Source file
/chronicle/**	Chronicle/Documentation/**
/arc/**	Arc/Documentation/** (the ApplicationModel repo, cloned as Arc)
/components/**	Components/Documentation/**
/cli/**, /fundamentals/**, /contributing/**	the matching repo's Documentation/
/, /why-cratis, /cratis-stack, /glossary, /comparisons/**, /adopting-cratis, …	Site-level pages: use the Documentation repo; source lives in Documentation/web/src/content/docs/*.{md,mdx}.

Example: /chronicle/concepts/event-source/ → Chronicle/Documentation/concepts/event-source.md. If unsure, grep -rl "<a distinctive sentence>" */Documentation Documentation/web/src/content/docs/*.md*.

Never edit Documentation/web/src/content/docs/{chronicle,arc,components,cli,fundamentals,contributing}/ — generated and git-ignored.

2. Edit the source

• Match the page's Diátaxis type (tutorial / how-to / explanation / reference) and the tour voice (teach, don't dump) — see the writing-cratis-docs rule (the tour-voice checklist + Starlight authoring tools). Don't mix types.
• Verify every framework API in a code example against real source before writing it — readers paste them verbatim. (See the writing-correct-examples rule; grep Studio *.cs/*.tsx and the product Source/ trees.)
• Link rules: product .md may use ./foo.md; links to a .mdx page must be extension-less (./foo); site-level .mdx uses clean root-relative URLs (/arc/...).