19 Publishing On GitHub Pages¶
This repository can be published as a proper documentation site instead of relying on raw file browsing.
What is configured¶
mkdocs.ymlbuilds a navigation-driven documentation site from the repository's canonical markdown filessite-docs/is a thin build root made of symlinks back to the canonical markdown files, so GitHub Pages gets a proper docs directory without duplicating content.github/workflows/pages.ymlbuilds and deploys that site on pushes tomainCNAMEdeclares the intended public Pages hostname:wllm.riera.co.uk- the site home page is the canonical repository
README.md, so there is still one canonical introduction
Why this setup is better¶
- GitHub repository browsing is good for contributors
- GitHub Pages is better for reading guides in order
- the left-hand navigation makes the numbered guides, knowledge layer, prompt assets, and evaluation docs easier to follow
- Mermaid diagrams and report graphs render directly in the published site
First-time setup on GitHub¶
- push the repository to GitHub
- open
Settings -> Pages - under
Build and deployment, selectGitHub Actions - push to
mainor run thepagesworkflow manually
After that, GitHub will publish the generated site/ artifact automatically.
Local preview¶
Install the docs dependencies:
Run the local preview server:
Build a production-style local site:
Writing guidelines for Pages-friendly docs¶
- link to markdown pages or landing pages, not bare folders
- keep command paths as repository-relative paths inside code blocks
- prefer human-readable landing pages like
evaluation/cases/README.mdwhen a folder contains machine-readable files - keep diagrams in Mermaid blocks so both GitHub and GitHub Pages can render them
What to avoid¶
- absolute local filesystem links
- references that only make sense inside your terminal session
- sending readers to a folder path that has no landing page
Related files¶
mkdocs.yml.github/workflows/pages.yml- repository_map.md