Skip to content

Serve the website without Jekyll - #68

Merged
Paururo merged 1 commit into
mainfrom
pages-nojekyll
Oct 20, 2026
Merged

Paururo merged 1 commit into
mainfrom
pages-nojekyll

Conversation

@Paururo

@Paururo Paururo commented Oct 20, 2026

Copy link
Copy Markdown
Member

The repository is public now, so GitHub Pages can serve the website from main, folder /docs, as .github/workflows/docs.yml says. Deploying from a branch, Pages runs Jekyll over the folder first. The markdown sources sit next to the pages built from them, and they keep their front matter from the MkDocs days (docs/user-guide/report.md starts with ---), so Jekyll would make a page of each at the address of the page tools/build_docs.py builds from it.

  • docs/.nojekyll, empty, turns Jekyll off, so Pages serves every file as it is.
  • tools/check_site.py fails when it is missing (checked by taking it away).
  • The comment in docs.yml and the contributing page say why it is there.

tools/build_docs.py --check and tools/check_site.py pass.

GitHub Pages serves docs/ from main and by default runs Jekyll over it first, which would make a page of each markdown file with front matter at the address of the page build_docs.py builds from it. An empty docs/.nojekyll turns Jekyll off, and check_site.py fails without it.
@Paururo Paururo added the documentation Improvements or additions to documentation label Oct 20, 2026
@Paururo
Paururo merged commit 6351c0c into main Oct 20, 2026
3 checks passed
@Paururo
Paururo deleted the pages-nojekyll branch October 24, 2026 09:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant