Handbook: Zensical skeleton, ADR and publishing to git-pages #138
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
MassiveDynamic/kataba#138
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #137
What
Set up the handbook site: a Zensical project in
handbook/with the skeleton of both handbooks, published to git-pages as part of the release.Decisions (from the #137 grilling)
handbook/in the kataba repo (docs/is taken by ADRs and agent docs), so doc changes land in the same MR as the feature. Python stays out of the Node project: pin Zensical inhandbook/requirements.txt, install viauv/pipx.https://pages.mike-ochmann.de/kataba/(the server is already running there; sites live under paths, no wildcard subdomains). Setsite_urlaccordingly.~/.claude/skills/release, outside the repo), no Forgejo Action/runner:zensical build --strict(fails the release on broken links) → push the built site to thepagesbranch →PUTthe repo URL to the site URL on git-pages. Find out how this git-pages instance authorizes a publish and document it in the skill.package.jsonhomepagestays the repo.Acceptance criteria
handbook/builds withzensical build --strictfrom a clean checkout, following a short README section on how to preview it locally (zensical serve)handbook/, hosted on git-pages, published by the release skill, screenshots generated by Playwright and committed (see sibling ticket) — including why (Material end of support, no built-in Forgejo Pages, no runner)https://pages.mike-ochmann.de/kataba/Done in #143 (merged as
249de57): Zensical handbook skeleton in handbook/ with both handbooks as placeholder pages, kataba logo and accent in light and dark mode, README section on previewing it, ADR-0024, and a handbook step in the release skill (build --strict, pages branch, PUT to git-pages, authorized by the DNS challenge _git-pages-challenge.pages.mike-ochmann.de; token in ~/.config/kataba/pages-token). First publish is live at https://pages.mike-ochmann.de/kataba/ and the repo's Website field points there.