Skip to content

docs: publish documentation as a GitHub Pages site (Sphinx)#37

Merged
Guillain-RDCDE merged 3 commits into
mainfrom
docs/github-pages-site
Jun 3, 2026
Merged

docs: publish documentation as a GitHub Pages site (Sphinx)#37
Guillain-RDCDE merged 3 commits into
mainfrom
docs/github-pages-site

Conversation

@Guillain-RDCDE
Copy link
Copy Markdown
Owner

#3 — Site de documentation GitHub Pages (Sphinx)

Transforme le setup Sphinx (présent mais jamais buildé) en un vrai site de docs navigable et searchable, déployé à chaque push sur main.

Ce que ça apporte

  • .github/workflows/docs.yml : build du HTML Sphinx (-W --keep-going → toute régression doc casse le build) + déploiement GitHub Pages. Le build tourne aussi sur les PR (validation) ; seul main/manuel déclenche le deploy.
  • conf.py : version lue depuis le package (fini les release périmés codés en dur) ; docs/README.md exclu (méta-index, doublon d'index.md).
  • index.md devient le doc maître avec une {toctree} (nav latérale) ; suppression du index.rst en double qui entrait en conflit.
  • Liens cross-tree corrigés (../.github/*, ../ml/README, ../README, ../LICENSE → URLs absolues GitHub) : résolvent sur github.com et dans le site Sphinx → build 100% sans warning.
  • URL « Documentation » (pyproject) + badge/lien README pointent vers le site Pages.

Build local validé

sphinx-build -W --keep-goingexit 0, 0 warning, 8 pages générées (index, getting-started, user-guide, api-reference, technical-details, roadmap-formats, genindex, search).

⚠️ Action unique requise (côté mainteneur)

Repo Settings → Pages → Source : « GitHub Actions ». Ensuite le site est en ligne à https://guillain-rdcde.github.io/FLAC_Detective/ dès le prochain push sur main.

La CI de cette PR exécute le job build du nouveau workflow → tu verras tout de suite s'il passe (il passe en local).

🤖 Generated with Claude Code

Turn the existing-but-unbuilt Sphinx setup into a real, searchable docs site that
deploys on every push to main.

- .github/workflows/docs.yml: build the Sphinx HTML (`-W --keep-going`, so doc
  regressions fail the build) and deploy to GitHub Pages. Build also runs on PRs
  (validation); only main/manual runs deploy.
- conf.py: read the version from the package (no more stale hard-coded release);
  exclude docs/README.md (it's the folder meta-index, mirrors index.md).
- index.md becomes the master doc with a `{toctree}` (sidebar nav); removed the
  duplicate index.rst that conflicted with it.
- Fixed cross-tree Markdown links (../.github/*, ../ml/README, ../README, ../LICENSE)
  to absolute GitHub URLs so they resolve both on github.com and in the Sphinx site
  — clears all the myst xref warnings; the build is now warning-clean.
- pyproject "Documentation" URL + a README docs badge/link point to the Pages site.

One-time setup the maintainer must do: repo Settings -> Pages -> Source: "GitHub
Actions". After that the site goes live at
https://guillain-rdcde.github.io/FLAC_Detective/ on the next push to main.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Comment thread docs/conf.py Fixed
Guillain-RDCDE and others added 2 commits June 3, 2026 14:24
…on CI

Empty dirs aren't tracked by git, so a fresh CI checkout lacked docs/_static,
making Sphinx warn 'html_static_path entry _static does not exist' — fatal under
-W. Add .gitkeep to both _static and _templates (referenced by conf.py).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…-import)

CodeQL flagged 'from ...__version__ import __version__ as release' as an unused
import (Sphinx only reads 'release' as a module global, never references it), and
a noqa silences flake8 but not CodeQL. Import the module and assign the attribute
instead — the import is now clearly used and 'release' is a plain config global.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@Guillain-RDCDE Guillain-RDCDE merged commit 3dd7182 into main Jun 3, 2026
18 checks passed
@Guillain-RDCDE Guillain-RDCDE deleted the docs/github-pages-site branch June 3, 2026 12:31
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.

2 participants