Markdown files
Markdown files are the working files behind the sitemap.
In the sitemap view, each markdown file becomes a page card. In Page Writer, the same file becomes editable page content. In GitHub sync, those files can be written to the connected repository under `/clea-sitemap-expansion`.
This keeps the page workflow simple. The sitemap is not only a board. It points to files CLEA can use.
Why markdown matters
Markdown is plain enough for humans and structured enough for CLEA.
You can write notes, headings, tables, draft copy, page status, source notes, and internal link ideas inside one file. CLEA can read that file in chat or Page Writer and help improve it.
Add frontmatter
Give the file title, description, and URL data.
Add page notes
Write the goal, status, source notes, and link ideas.
Edit with CLEA
Use Page Writer or chat when the file needs work.
Review before sync
Check the saved markdown before GitHub sync.
Start with a useful file
A good sitemap markdown file does not need to be long on day one.
It should have enough data to prevent guessing. Add a title, URL, description, page goal, status, and any evidence that should guide the page.
--- title: "AI visibility dashboard" description: "How the dashboard helps teams see prompts, mentions, and next actions." url: "/ai-visibility-dashboard" --- ## Goal Explain the dashboard in simple words. ## Status Planned.
Keep files reviewable
Do not let markdown files become messy storage.
If a note is important for the page, keep it in the file. If it belongs to a different page, move it to that page. This makes review easier before GitHub sync.