Skip to content

docs: migrate site to Zensical#77

Open
alejandroGM0 wants to merge 5 commits intohiero-ledger:mainfrom
alejandroGM0:docs/zensical-migration
Open

docs: migrate site to Zensical#77
alejandroGM0 wants to merge 5 commits intohiero-ledger:mainfrom
alejandroGM0:docs/zensical-migration

Conversation

@alejandroGM0
Copy link
Copy Markdown
Contributor

@alejandroGM0 alejandroGM0 commented Apr 23, 2026

Summary

  • replace the MkDocs docs toolchain with pinned Zensical builds in CI
  • keep the current Material look, Hiero favicon, and gh-pages PR preview flow
  • update contributor docs for the new local docs commands

Closes #70.

Test plan

  • Run zensical build --clean
  • Review the local docs preview

Signed-off-by: Alejandro <26930485+alejandroGM0@users.noreply.github.com>
@alejandroGM0 alejandroGM0 force-pushed the docs/zensical-migration branch from 1d83a6c to 25ccc1d Compare April 23, 2026 17:10
Comment thread requirements-docs.txt Outdated
Install Zensical directly in the docs workflow and contributor docs instead of keeping a separate requirements file. Keep the version explicit while Zensical is still in 0.0.x to avoid unexpected breaking changes.

Signed-off-by: Alejandro <26930485+alejandroGM0@users.noreply.github.com>
GITHUB_TOKEN from pull_request workflows cannot write to the base repo when the PR head is a fork, so gh-pages push fails with 403. Still run the docs build; deploy and comment only for same-repo PRs.

Signed-off-by: Alejandro <26930485+alejandroGM0@users.noreply.github.com>
Split the Docs workflow in two. The Docs workflow now only builds the site and uploads a docs-preview artifact, which is safe for fork PRs. A new Docs Preview Deploy workflow runs on workflow_run, downloads the artifact, and publishes the preview to gh-pages/pr/<n>/ and comments the URL on the PR, so fork PRs get previews too.

Signed-off-by: Alejandro <26930485+alejandroGM0@users.noreply.github.com>
Treat the PR number from the artifact as untrusted: strictly validate it as a positive integer, and pass it to actions/github-script via env instead of an inline expression so no attacker-controlled text can be expanded into the script body.

Signed-off-by: Alejandro <26930485+alejandroGM0@users.noreply.github.com>
@alejandroGM0
Copy link
Copy Markdown
Contributor Author

I also fixed an issue where fork PR doc previews failed with a 403 because the read‑only GITHUB_TOKEN couldn't deploy; I split the flow so the PR job only builds and uploads an artifact, and a separate workflow_run deploys to /pr// and comments, restoring fork previews.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: migrate from MkDocs to Zensical

2 participants