docs: publish the glossed paper pages via GitHub Pages - #32
Open
ksdisch wants to merge 1 commit into
Open
Conversation
The interactive click-to-reveal glossed page renders as raw HTML source on github.com, which is the only place it was reachable — a page built to be read in a browser, shipped in the one place a browser won't run it. Serving docs/ via Pages makes it live. .nojekyll because the site is static files, not a Jekyll build: the docs/ tree is full of markdown containing braces that Liquid would try to interpret, and a failed Jekyll build means no site at all. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015uobnj3QL2D9Acd4hDiGSm
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The interactive click-to-reveal glossed page renders as raw HTML source on github.com — a page built to be read in a browser, shipped in the one place a browser won't run it.
Serving
docs/via Pages makes it live..nojekyllbecause this is static files, not a Jekyll build: thedocs/tree is full of markdown containing braces Liquid would try to interpret, and a failed Jekyll build means no site at all.Pages source (
main/docs) is set on the repo alongside this PR.🤖 Generated with Claude Code
https://claude.ai/code/session_015uobnj3QL2D9Acd4hDiGSm