Skip to content

chore(docs): remove MkDocs site stack#156

Merged
BrettKinny merged 1 commit into
mainfrom
worktree-remove-mkdocs
Jun 6, 2026
Merged

chore(docs): remove MkDocs site stack#156
BrettKinny merged 1 commit into
mainfrom
worktree-remove-mkdocs

Conversation

@BrettKinny
Copy link
Copy Markdown
Owner

What

Strips out the MkDocs Material + mike versioned docs-site stack. The docs under docs/ stay exactly as they are — they already render fine as plain markdown on GitHub — we're just removing the unused build/publish apparatus around them.

Why

The site was maintenance overhead with no current payoff:

  • a nav: in mkdocs.yml that had to be hand-synced on every doc add/rename,
  • a GitHub Pages deploy workflow (mike on tag push),
  • a CI frontmatter-check job that could fail builds over a missing --- block.

In line with the broader "strip things back to reduce maintenance burden" effort.

Removed

  • mkdocs.yml
  • .github/workflows/docs-deploy.yml
  • docs/requirements.txt (mkdocs-material, mike, pymdown-extensions)
  • docs/versioning.md — entirely about the docs-site versioning model
  • docs/assets/dotty-hero.svg — MkDocs logo/favicon only; README's hero uses the separate bridge/assets/dotty-hero.svg
  • CI frontmatter-check job, and mkdocs.yml from the yaml-lint file list

Kept / fixed

  • Kept the YAML frontmatter in every doc (harmless; GitHub renders it).
  • Kept the root-file symlinks in docs/ (SETUP.md, ROADMAP.md, etc.) — real docs link to them relatively.
  • Fixed references that pointed at the now-dead published site in CONTRIBUTING.md, COMPATIBILITY.md, CHANGELOG.md, and docs/style.md.

Follow-up (manual, out of scope)

The gh-pages branch and the repo's Settings → Pages configuration are untouched. Delete the branch and disable Pages if the site is no longer wanted.

🤖 Generated with Claude Code

Copilot AI review requested due to automatic review settings June 6, 2026 11:36
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR removes the MkDocs Material + mike-based documentation site tooling (config, dependencies, and deploy workflow) while keeping the docs/ content as plain GitHub-rendered Markdown, and updates documentation references/CI accordingly.

Changes:

  • Remove MkDocs site configuration, docs-site dependencies, and the GitHub Pages deployment workflow.
  • Delete docs that only existed to support site versioning, plus the MkDocs-only asset.
  • Update documentation/CI references to stop pointing at the now-removed published site and drop the CI frontmatter gate.

Reviewed changes

Copilot reviewed 10 out of 11 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
mkdocs.yml Removed MkDocs site configuration (nav/theme/plugins).
docs/versioning.md Removed doc that described MkDocs/mike versioned-site behavior.
docs/style.md Updated docs authoring guidance to match “plain Markdown on GitHub” approach.
docs/requirements.txt Removed docs-site Python dependencies (mkdocs-material, mike, pymdown-extensions).
docs/assets/dotty-hero.svg Removed MkDocs-only logo/favicon asset.
CONTRIBUTING.md Removed docs-site versioning contributor guidance.
COMPATIBILITY.md Replaced published-site link with local-docs reference.
CHANGELOG.md Removed changelog entry about versioned docs-site deployment.
.pre-commit-config.yaml Updated check-yaml exclusions now that mkdocs.yml is gone.
.github/workflows/docs-deploy.yml Removed GitHub Pages docs deployment workflow.
.github/workflows/ci.yml Removed mkdocs/frontmatter-related CI checks and references.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread COMPATIBILITY.md
component exposes, what counts as a breaking change, and how to upgrade safely.

For protocol wire formats see [protocols.md](https://brettkinny.github.io/dotty-stackchan/latest/protocols/).
For protocol wire formats see `docs/protocols.md`.
Comment thread .pre-commit-config.yaml
Comment on lines 24 to 27
- id: check-yaml
exclude: '^(mkdocs\.yml|\.github/workflows/.*\.yml|firmware/)'
# mkdocs.yml uses python tags (!!python/name:...) that PyYAML
# safe_load can't resolve; GHA workflows use the same. yamllint
exclude: '^(\.github/workflows/.*\.yml|firmware/)'
# GHA workflows use tags PyYAML safe_load can't resolve; yamllint
# already lints them in CI.
Comment thread .github/workflows/ci.yml
Comment on lines 24 to +28
yamllint \
.config.yaml.template \
docker-compose.yml.template \
compose.all-in-one.yml \
compose.local.override.yml \
mkdocs.yml
compose.local.override.yml
The MkDocs Material + `mike` versioned docs-site setup was unused overhead:
a hand-synced nav, a GitHub Pages deploy workflow, and a CI job that failed
builds over missing doc frontmatter — all for a site that duplicated docs
that already render fine as plain markdown on GitHub.

Removed:
- mkdocs.yml, .github/workflows/docs-deploy.yml, docs/requirements.txt
- docs/versioning.md (entirely about the mike/MkDocs site)
- docs/assets/dotty-hero.svg (MkDocs logo/favicon only; README uses the
  bridge/assets copy)
- CI frontmatter-check job + mkdocs.yml from the yaml-lint list

Kept the docs/ frontmatter (harmless, GitHub renders it) and the root-file
symlinks in docs/ (they back intra-docs relative links). Fixed references in
CONTRIBUTING.md, COMPATIBILITY.md, CHANGELOG.md, and docs/style.md that pointed
at the now-dead published site.

Note: the gh-pages branch and the repo's GitHub Pages setting are untouched —
delete them manually if no longer wanted.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@BrettKinny BrettKinny force-pushed the worktree-remove-mkdocs branch from a7fbfe7 to ed7d003 Compare June 6, 2026 11:52
@BrettKinny BrettKinny merged commit 743dcd8 into main Jun 6, 2026
8 checks passed
@BrettKinny BrettKinny deleted the worktree-remove-mkdocs branch June 6, 2026 11:53
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