Skip to content

docs: phase 1 — properdocs site scaffolding + GitHub Pages deploy#5

Merged
chad-loder merged 1 commit into
mainfrom
docs/phase-1-properdocs-infra
May 12, 2026
Merged

docs: phase 1 — properdocs site scaffolding + GitHub Pages deploy#5
chad-loder merged 1 commit into
mainfrom
docs/phase-1-properdocs-infra

Conversation

@chad-loder
Copy link
Copy Markdown
Owner

Summary

Re-add the pyhaul-style documentation infrastructure stripped during the initial spin-up cleanup. Infra-only — content reshape lands in phases 3-6.

Adds Why
properdocs.yml mkdocs-material theme; pymdownx admonitions/tabs/superfences; mkdocstrings for the eventual API reference; mkdocs-code-validator runs python -c "ast.parse(...)" on every Python block so drift = CI failure, not silent rot
[dependency-groups] docs properdocs / mkdocs-material / mkdocstrings[python] / mkdocs-code-validator — versions match pyhaul
.github/workflows/docs.yml build + deploy on push to main (paths-filtered); properdocs build --strict so broken anchors / missing nav entries fail closed
docs/stylesheets/extra.css nav section-header polish copied from pyhaul
docs/index.md minimal landing page; README is still the source of truth until phase 4
just docs / just docs-serve local build + live-reload
renovate.json restore the "docs tools" group + add the four docs deps to the automerge list
[tool.rumdl.per-file-flavor] docs/**/*.md = "mkdocs" so the markdown linter accepts admonitions / tabbed code blocks

Nav already includes WPT Conformance pointing at the existing auto-generated docs/wpt-compliance.md, so the site has one real page from day one.

Site target: https://chad-loder.github.io/yarlpattern (Pages source + github-pages environment configured GH-side after merge).

Test plan

  • uv sync --group docs resolves; just docs builds clean
  • just check passes (16 lint tools + 580 tests, both lint stacks)
  • actionlint clean on docs.yml
  • zizmor clean on the new workflow
  • CI on this PR passes
  • After merge: enable Pages with build_type=workflow; create github-pages env with branch policy main

Re-add the pyhaul-style documentation infrastructure stripped during the
initial spin-up cleanup. This is infra-only — content reshape lands in
phases 3-6.

Adds:

* ``properdocs.yml`` — site config (mkdocs-material theme; pymdownx
  admonitions / tabs / superfences; mkdocstrings for the eventual API
  reference; mkdocs-code-validator runs ``python -c "ast.parse(...)"``
  on every Python block at build time so doc-snippets that drift become
  build-time failures, not silent rot).
* ``[dependency-groups] docs`` — properdocs, mkdocs-material,
  mkdocstrings[python], mkdocs-code-validator (versions matching pyhaul).
* ``.github/workflows/docs.yml`` — build + deploy to GitHub Pages on
  every push to main (paths-filtered to docs/, properdocs.yml, .md,
  src/). ``properdocs build --strict`` so broken anchors or missing
  nav entries fail CI.
* ``docs/stylesheets/extra.css`` — nav section-header polish (copied
  from pyhaul).
* ``docs/index.md`` — minimal landing page; the README is still the
  source of truth until phase 4.
* ``just docs`` / ``just docs-serve`` — local build + live-reload.
* ``renovate.json`` — restore the "docs tools" group + add the four
  docs deps to the automerge list.
* ``[tool.rumdl.per-file-flavor]`` — ``docs/**/*.md = mkdocs`` so the
  markdown linter accepts admonitions / tabbed code blocks.

Nav already includes ``WPT Conformance`` pointing at the existing
auto-generated ``docs/wpt-compliance.md``, so the site has one real
page from day one.

Site target: https://chad-loder.github.io/yarlpattern (Pages source +
``github-pages`` environment configured GH-side in the merge follow-up).
@github-actions github-actions Bot added the documentation Improvements or additions to documentation label May 12, 2026
@chad-loder chad-loder merged commit acaa508 into main May 12, 2026
19 checks passed
@chad-loder chad-loder deleted the docs/phase-1-properdocs-infra branch May 12, 2026 22:50
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