Sitemap view

The sitemap view turns workspace files into a visual page map.

It reads the locked `Sitemap` folder in the workspace. Folders become groups. Markdown files become page cards. Each page card is shown like a search result, with a title, URL path, and description when the file contains that data.

Existing markdown files show the pages CLEA can inspect or edit.

These files can be opened in Page Writer. CLEA can read the page, improve the draft, add JSON-LD, and run an on-page check when a live URL exists.

Planned pages can start as simple markdown files.

The sitemap view has a `Create page` action for a group. It creates a new `page N.md` file with starter frontmatter, a title, a URL, and basic sections.

Groups help keep page ideas organized.

For example, a group can hold pages for one topic, one product area, one competitor gap, or one content plan.

The sitemap view has zoom and movement controls because larger sites can become wide.

You can fit the view, zoom in or out, and focus a group. This makes the sitemap useful for both small page sets and larger page plans.

Markdown frontmatter helps CLEA understand the page.

Useful fields include `title`, `description`, `url`, and JSON-LD data when available.

Folders are sections. Markdown files are pages.

This keeps the sitemap close to how the content will later sync into GitHub.

CLEA can treat pages differently based on their state.

A page may be a draft, an improvement target, or a page ready for review.

GitHub sync writes sitemap markdown files to `/clea-sitemap-expansion` in the connected repository.

The sync keeps folder paths. A page inside a sitemap folder becomes a markdown file under the same path in the GitHub expansion folder.

Clicking a page card can open Page Writer.

Page Writer shows the markdown, preview data, JSON-LD area, chat, and on-page check. This is where a planned page becomes a reviewed file.

Use the sitemap for bulk work only when the plan is clear.

Bulk maintain means keeping existing pages healthy. Bulk improve means upgrading weak pages. Bulk produce means creating planned pages from a known gap. Each one needs review before publishing.