prodockit 0.1.0__tar.gz

prodockit-0.1.0/.github/CODEOWNERS

@@ -0,0 +1,8 @@
+# Copyright (c) 2026 Mark Buckwell and contributors
+# SPDX-License-Identifier: MIT
+
+# Every pull request needs a review from one of the owners listed below,
+# regardless of which files it touches. Combine with a branch protection
+# rule on main ("Require a pull request before merging" + "Require review
+# from Code Owners") for this to actually block merging without approval.
+* @buckwem

prodockit-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,33 @@
+# Copyright (c) 2026 Mark Buckwell and contributors
+# SPDX-License-Identifier: MIT
+
+name: CI
+on:
+  push:
+    branches: [main]
+  pull_request:
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v5
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: pip install -e ".[dev]"
+      - run: ruff check .
+      - run: mypy src
+      - run: pytest --cov=prodockit
+
+  docs:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v5
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.x"
+      - run: pip install -e .
+      - run: zensical build --clean --strict

prodockit-0.1.0/.github/workflows/docs.yml

@@ -0,0 +1,32 @@
+# Copyright (c) 2026 Mark Buckwell and contributors
+# SPDX-License-Identifier: MIT
+
+name: Documentation
+on:
+  push:
+    branches:
+      - main
+  workflow_dispatch:
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+jobs:
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/configure-pages@v5
+      - uses: actions/checkout@v5
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.x"
+      - run: pip install -e .
+      - run: zensical build --clean --strict
+      - uses: actions/upload-pages-artifact@v4
+        with:
+          path: site
+      - uses: actions/deploy-pages@v4
+        id: deployment

prodockit-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,33 @@
+# Copyright (c) 2026 Mark Buckwell and contributors
+# SPDX-License-Identifier: MIT
+
+name: Publish to PyPI
+on:
+  release:
+    types: [published]
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v5
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.x"
+      - run: pip install build
+      - run: python -m build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write # required for PyPI trusted publishing
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

prodockit-0.1.0/.gitignore

@@ -0,0 +1,17 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+build/
+dist/
+.venv/
+venv/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+.DS_Store
+site/
+docs/site_documentation.pdf
+docs/.prodockit-pdf-mermaid/

prodockit-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Mark Buckwell and contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

prodockit-0.1.0/PKG-INFO

@@ -0,0 +1,148 @@
+Metadata-Version: 2.4
+Name: prodockit
+Version: 0.1.0
+Summary: A family of extensions for Zensical needed for professional and academic documentation: section cross-references, bibliography/citation handling, a glossary, a Pandoc/WeasyPrint PDF pipeline, and Jinja macros for word counts and reference-style spacing
+Project-URL: Homepage, https://github.com/buckwem/prodockit-extensions
+Project-URL: Documentation, https://buckwem.github.io/prodockit-extensions/
+Project-URL: Issues, https://github.com/buckwem/prodockit-extensions/issues
+Author: Mark Buckwell
+License-Expression: MIT
+License-File: LICENSE
+Keywords: extension,markdown,pandoc,pdf,python-markdown,zensical
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Text Processing :: Markup :: Markdown
+Requires-Python: >=3.10
+Requires-Dist: beautifulsoup4>=4.12
+Requires-Dist: click>=8.0
+Requires-Dist: markdown>=3.4
+Requires-Dist: zensical
+Provides-Extra: dev
+Requires-Dist: mypy; extra == 'dev'
+Requires-Dist: pytest; extra == 'dev'
+Requires-Dist: pytest-cov; extra == 'dev'
+Requires-Dist: ruff; extra == 'dev'
+Requires-Dist: types-beautifulsoup4; extra == 'dev'
+Requires-Dist: types-markdown; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# prodockit
+
+A family of extensions for [Zensical](https://zensical.org/) needed for
+professional and academic documentation: section cross-references,
+bibliography/citation handling, a glossary, and a Pandoc/WeasyPrint PDF
+pipeline for the downloadable, submittable document these usually need
+alongside the website itself. Each piece is independent, so you only pay
+for what you use.
+
+Most of prodockit is [Python-Markdown](https://python-markdown.github.io/)
+extensions, in the spirit of [pymdown-extensions](https://facelessuser.github.io/pymdown-extensions/) -
+configure one the same way as any other Zensical/`pymdownx` Markdown
+extension, via `zensical.toml`. `prodockit.pdf` is a command-line tool
+instead (`prodockit pdf`), since a PDF build pipeline isn't a Markdown syntax
+extension - it reads the same `zensical.toml` too.
+
+> **Status:** early, but functional - `prodockit.headings`, `prodockit.refs`,
+> `prodockit.citations`, `prodockit.glossary`, `prodockit.pdf`, and
+> `prodockit.zensical_macros` are implemented and tested.
+
+**[Full documentation](https://buckwem.github.io/prodockit-extensions/)**
+
+## Installation
+
+```bash
+pip install prodockit
+```
+
+## Extensions
+
+| Extension | Description |
+|---|---|
+| [`prodockit.headings`](https://buckwem.github.io/prodockit-extensions/extensions/headings/) | Gives every heading an id and a hierarchical section number ("1", "1.1", "1.2", "2", ...). |
+| [`prodockit.refs`](https://buckwem.github.io/prodockit-extensions/extensions/refs/) | `\ref{id}` section cross-references, resolving to the target's current number - similar in spirit to LaTeX's `\ref`. |
+| [`prodockit.citations`](https://buckwem.github.io/prodockit-extensions/extensions/citations/) | Define a source once, cite it by key anywhere with `\cite{id}` - auto-generates the bracketed, linked citation text. |
+| [`prodockit.glossary`](https://buckwem.github.io/prodockit-extensions/extensions/glossary/) | Define a term once (an acronym expansion, a glossary entry), insert it by id anywhere with `\gls{id}` - similar in spirit to LaTeX's `glossaries` package. |
+
+```python
+import markdown
+
+html = markdown.markdown(
+    text,
+    extensions=[
+        "attr_list", "prodockit.headings", "prodockit.refs", "prodockit.citations", "prodockit.glossary"
+    ],
+)
+```
+
+```md
+# Introduction {: #intro }
+
+See \ref{intro} for background.\cite{skou2023} This uses \gls{css}.
+
+Skoulikari, A. (2023) *Learning Git*.
+{: #skou2023 data-cite-text="Skoulikari, 2023" }
+
+**CSS** - Cascading Style Sheets.
+{: #css data-term="CSS" }
+```
+
+`\ref{intro}` resolves to a link reading `1` - the heading's current
+section number; `\cite{skou2023}` resolves to `[Skoulikari, 2023]`, linked
+to that source; `\gls{css}` resolves to `CSS`, linked to its own
+definition. All three stay correct if content is reordered, since
+resolution happens fresh on every conversion. See the
+[docs](https://buckwem.github.io/prodockit-extensions/) for options, multi-page
+registry sharing, and full syntax details.
+
+## PDF generation
+
+[`prodockit.pdf`](https://buckwem.github.io/prodockit-extensions/pdf/) builds a
+standalone PDF from your site, via Pandoc and WeasyPrint (both need to be
+installed separately - see the docs). No Python required - it reads the
+same `zensical.toml` your site already has:
+
+```bash
+prodockit pdf
+```
+
+That's it - run it from your project root and it builds a complete PDF,
+table of contents included, from every page in your `nav`. See the
+[docs](https://buckwem.github.io/prodockit-extensions/pdf/) for the
+`zensical.toml` settings it reads, and for the Python API
+(`build_pdf()`, `prodockit.pdf.html`/`.lua`/`.css`/`.icons`/`.mermaid`) if
+you're scripting your own build pipeline instead.
+
+## Website macros
+
+[`prodockit.zensical_macros`](https://buckwem.github.io/prodockit-extensions/macros/)
+provides a site-wide word count, the git-detected repository URL, chapter/
+appendix numbering that continues across pages, and reference/acronym/
+glossary spacing that matches `prodockit.pdf`'s own PDF output - as Jinja
+variables/macros for Zensical's own macros plugin:
+
+```toml
+[project.markdown_extensions.zensical.extensions.macros]
+modules = ["prodockit.zensical_macros"]
+```
+
+See the [docs](https://buckwem.github.io/prodockit-extensions/macros/) for the
+full variable/macro list.
+
+## Development
+
+```bash
+python -m venv .venv
+source .venv/bin/activate
+pip install -e ".[dev]"
+pytest
+```
+
+`zensical` is a core dependency, so `zensical serve` is available as soon as
+`prodockit` is installed - no extra step needed to build the documentation
+locally.
+
+## License
+
+MIT - see [LICENSE](LICENSE).

prodockit-0.1.0/PLAN-16.md

@@ -0,0 +1,143 @@
+# Plan: rename `zendoc` → `prodockit` (zendoc-extensions#16)
+
+Not yet implemented - for review/agreement first, per the same
+plan-then-implement pattern used for #11 (the earlier GitHub repo rename).
+
+## What #16 actually asks for
+
+> I want to remove the "zen" from the name of the extension. Change
+> extension name to prodockit in prodockit-extensions repo.
+
+Two renames, not one:
+1. The **Python package/import name**: `zendoc` → `prodockit` (this repo's
+   own `src/zendoc/*` code, PyPI project name, CLI command, entry points).
+2. The **GitHub repo name**: `zendoc-extensions` → `prodockit-extensions`
+   (this repo already went through one rename this month - `zendoc-extension`
+   → `zendoc-extensions`, #11/#15 - so this is a second hop; see risks below).
+
+This repo is not the only thing affected - `zendoc-template`
+(github.com/buckwem/zendoc-template) depends on the `zendoc` PyPI package
+directly (imports, `requirements.txt`, `zensical.toml` extension config)
+and has **132 references to "zendoc"** across 20 files that would need
+updating in lockstep. `zendoc-dev-dashboard` does **not** depend on the
+`zendoc` package at all (checked - its dependencies are `zensical`,
+`weasyprint`, etc., unrelated) - it just happens to share the naming
+prefix, so it's out of scope here unless you want full branding
+consistency later.
+
+## Decisions (resolved)
+
+1. **Existing `zendoc` PyPI releases**: remove the `zendoc` project from
+   PyPI entirely. Note this is a manual step only you can do (full project
+   deletion is a pypi.org web UI action, not available via API/CLI to an
+   agent) - and PyPI's policy is that a deleted project's exact name
+   generally can't be re-registered by anyone afterwards, so this is a
+   one-way door. Sequencing: do this *after* `prodockit` is published and
+   `zendoc-template` is cut over (Phase 4), so there's no gap where neither
+   package installs.
+2. **Version numbering for `prodockit`**: reset to `0.1.0`.
+3. **`zendoc-template` renaming**: out of scope for now (bigger plans
+   pending) - Phase 4 below only updates its *dependency* on the package,
+   not the template repo's own name/branding.
+
+## PyPI name check
+
+`prodockit` is **available** on PyPI (confirmed - no existing project by
+that name), so no squatting conflict to work around.
+
+## Sequencing (each phase is a PR, tested before moving to the next)
+
+### Phase 1 - `zendoc-extensions`: the package rename itself
+- `src/zendoc/` → `src/prodockit/` (directory rename), all internal
+  imports (`headings.py`, `refs.py`, `citations.py`, `glossary.py`,
+  `settings.py`, `util.py`, `wordcount.py`, `zensical_macros.py`,
+  `_zensical.py`, `pdf/__init__.py`, `pdf/build.py`, `pdf/cli.py`,
+  `pdf/config.py`, `pdf/css.py`, `pdf/html.py`, `pdf/icons.py`,
+  `pdf/lua.py`, `pdf/mermaid.py`) updated from `zendoc.X` to `prodockit.X`.
+- `pyproject.toml`: `name = "zendoc"` → `"prodockit"`; entry points
+  (`"zendoc.headings"` etc. → `"prodockit.headings"` etc.); `[project.scripts]
+  zendoc = "zendoc.pdf.cli:main"` → `prodockit = "prodockit.pdf.cli:main"`
+  (this is a CLI-breaking rename too - anyone running `zendoc` from a
+  shell gets `prodockit` instead, worth a changelog line); `packages =
+  ["src/zendoc"]` → `["src/prodockit"]`; ruff per-file-ignores paths;
+  `[project.urls]` updated to the new repo name/Pages URL (see Phase 3 -
+  these can be updated now even before the repo rename actually happens,
+  same as #11 did).
+- `tests/*.py` - update every `from zendoc...`/`import zendoc` to
+  `prodockit`.
+- `docs/*.md`, `README.md`, this repo's own `zensical.toml` (which
+  showcases the extension on its own docs site) - every `zendoc.headings`/
+  `zendoc.citations`/`pip install zendoc`/repo-URL reference updated.
+- Verify: full test suite (`pytest`), `zensical build`, docs site builds
+  clean.
+
+### Phase 2 - cut a `prodockit` PyPI release
+- `pyproject.toml` version reset to `0.1.0` (per decision #2).
+- One-time manual step **you'll need to do yourself**: register
+  `prodockit` as a pending trusted publisher on pypi.org for this repo's
+  `publish.yml` workflow (trusted publishing is configured per-project-name
+  on PyPI's side and requires your own PyPI login - I can't do this part).
+- Then a normal GitHub Release triggers `publish.yml` as it already does.
+
+### Phase 3 - rename the GitHub repo
+- `zendoc-extensions` → `prodockit-extensions` (Settings → repo name, same
+  process as #11's `zendoc-extension` → `zendoc-extensions` rename).
+- **Risk worth flagging**: GitHub redirects old→new repo URLs, but this
+  repo already has one redirect hop in place (`zendoc-extension` →
+  `zendoc-extensions`); adding a second hop (→ `prodockit-extensions`)
+  means anyone following the *original* pre-#11 URL now needs GitHub to
+  chain two redirects. GitHub does support this, but it's worth a quick
+  manual check afterwards that the original `zendoc-extension` URL still
+  lands somewhere sane.
+- GitHub Pages URL moves the same way: `buckwem.github.io/zendoc-extensions/`
+  → `buckwem.github.io/prodockit-extensions/` (same pattern as #11 -
+  confirmed old URL 404s, new one resolves).
+- Rename the local clone directory to match
+  (`~/GitHub/zendoc-extensions` → `~/GitHub/prodockit-extensions`).
+
+### Phase 4 - `zendoc-template`: update the dependent repo
+132 references across 20 files, roughly:
+- `requirements.txt` - `zendoc>=0.10.0` → `prodockit>=<new version>`.
+- `macros.py` - `from zendoc.zensical_macros import define_env` →
+  `from prodockit.zensical_macros import define_env`; update the
+  workaround comment (currently references `zendoc.zensical_macros` and
+  `zensical/zensical#823`, the issue number stays the same, just the
+  module name in the prose changes).
+- `zensical.toml` - `[project.markdown_extensions."zendoc.headings"]` and
+  siblings (`refs`, `citations`, `glossary`) → `"prodockit.headings"` etc.
+- `build_pdf.py` - any `zendoc.pdf`/`zendoc.settings`/`zendoc.wordcount`
+  references.
+- `docs/starthere/customise.md`, `installtooling.md`, `startediting.md`,
+  `testing.md` - prose references, install instructions, doc links
+  (`buckwem.github.io/zendoc-extensions/...` → `.../prodockit-extensions/...`).
+- `test/conftest.py`, `test_customisation.py`, `test_captions.py`,
+  `test_fences.py`, `test_links.py`, `test_pdf_structure.py`,
+  `test_word_count.py`, `test_zensical_basics.py`, `test/run_tests.py` -
+  import statements and docstring/comment references.
+- `README.md`, `CONTRIBUTING.md` - prose references.
+- `spike/render-pipeline-92/fix_tabs.py` - this is old spike/scratch code
+  from a past migration; worth checking whether it's still referenced by
+  anything live or safe to leave/delete rather than update in place.
+- Verify: `pip install -r requirements.txt`, `python build_pdf.py`,
+  `zensical build --clean`, full `pytest` suite (157 tests currently) -
+  all need to pass against `prodockit` before merging.
+
+### Phase 5 - close out
+- Close #16 (this repo) referencing the merged PRs.
+- Remove the `zendoc` project from PyPI (decision #1 - manual, pypi.org,
+  after `prodockit` is live and `zendoc-template` is cut over).
+- Update memory/notes if anything here should persist beyond this
+  conversation (e.g. the new repo name, PyPI package name).
+
+## Effort/risk summary
+
+This is bigger than #11 (that was a pure find-replace on self-referential
+URLs/prose, ~15 lines across 5 files). This one is a real package rename:
+directory move, import rewrites, entry-point/CLI renames, a PyPI release,
+a second repo rename hop, and a 132-reference cleanup in the dependent
+template repo - each phase independently testable, but the whole thing
+only "works" end to end once `zendoc-template` is pointed at a published
+`prodockit` release, so there's a window where the two repos are
+intentionally out of sync (Phase 1-2 done, Phase 4 not yet) - not a
+problem as long as `zendoc-template`'s `main` isn't touched until Phase 4
+actually lands.

prodockit-0.1.0/README.md

@@ -0,0 +1,118 @@
+# prodockit
+
+A family of extensions for [Zensical](https://zensical.org/) needed for
+professional and academic documentation: section cross-references,
+bibliography/citation handling, a glossary, and a Pandoc/WeasyPrint PDF
+pipeline for the downloadable, submittable document these usually need
+alongside the website itself. Each piece is independent, so you only pay
+for what you use.
+
+Most of prodockit is [Python-Markdown](https://python-markdown.github.io/)
+extensions, in the spirit of [pymdown-extensions](https://facelessuser.github.io/pymdown-extensions/) -
+configure one the same way as any other Zensical/`pymdownx` Markdown
+extension, via `zensical.toml`. `prodockit.pdf` is a command-line tool
+instead (`prodockit pdf`), since a PDF build pipeline isn't a Markdown syntax
+extension - it reads the same `zensical.toml` too.
+
+> **Status:** early, but functional - `prodockit.headings`, `prodockit.refs`,
+> `prodockit.citations`, `prodockit.glossary`, `prodockit.pdf`, and
+> `prodockit.zensical_macros` are implemented and tested.
+
+**[Full documentation](https://buckwem.github.io/prodockit-extensions/)**
+
+## Installation
+
+```bash
+pip install prodockit
+```
+
+## Extensions
+
+| Extension | Description |
+|---|---|
+| [`prodockit.headings`](https://buckwem.github.io/prodockit-extensions/extensions/headings/) | Gives every heading an id and a hierarchical section number ("1", "1.1", "1.2", "2", ...). |
+| [`prodockit.refs`](https://buckwem.github.io/prodockit-extensions/extensions/refs/) | `\ref{id}` section cross-references, resolving to the target's current number - similar in spirit to LaTeX's `\ref`. |
+| [`prodockit.citations`](https://buckwem.github.io/prodockit-extensions/extensions/citations/) | Define a source once, cite it by key anywhere with `\cite{id}` - auto-generates the bracketed, linked citation text. |
+| [`prodockit.glossary`](https://buckwem.github.io/prodockit-extensions/extensions/glossary/) | Define a term once (an acronym expansion, a glossary entry), insert it by id anywhere with `\gls{id}` - similar in spirit to LaTeX's `glossaries` package. |
+
+```python
+import markdown
+
+html = markdown.markdown(
+    text,
+    extensions=[
+        "attr_list", "prodockit.headings", "prodockit.refs", "prodockit.citations", "prodockit.glossary"
+    ],
+)
+```
+
+```md
+# Introduction {: #intro }
+
+See \ref{intro} for background.\cite{skou2023} This uses \gls{css}.
+
+Skoulikari, A. (2023) *Learning Git*.
+{: #skou2023 data-cite-text="Skoulikari, 2023" }
+
+**CSS** - Cascading Style Sheets.
+{: #css data-term="CSS" }
+```
+
+`\ref{intro}` resolves to a link reading `1` - the heading's current
+section number; `\cite{skou2023}` resolves to `[Skoulikari, 2023]`, linked
+to that source; `\gls{css}` resolves to `CSS`, linked to its own
+definition. All three stay correct if content is reordered, since
+resolution happens fresh on every conversion. See the
+[docs](https://buckwem.github.io/prodockit-extensions/) for options, multi-page
+registry sharing, and full syntax details.
+
+## PDF generation
+
+[`prodockit.pdf`](https://buckwem.github.io/prodockit-extensions/pdf/) builds a
+standalone PDF from your site, via Pandoc and WeasyPrint (both need to be
+installed separately - see the docs). No Python required - it reads the
+same `zensical.toml` your site already has:
+
+```bash
+prodockit pdf
+```
+
+That's it - run it from your project root and it builds a complete PDF,
+table of contents included, from every page in your `nav`. See the
+[docs](https://buckwem.github.io/prodockit-extensions/pdf/) for the
+`zensical.toml` settings it reads, and for the Python API
+(`build_pdf()`, `prodockit.pdf.html`/`.lua`/`.css`/`.icons`/`.mermaid`) if
+you're scripting your own build pipeline instead.
+
+## Website macros
+
+[`prodockit.zensical_macros`](https://buckwem.github.io/prodockit-extensions/macros/)
+provides a site-wide word count, the git-detected repository URL, chapter/
+appendix numbering that continues across pages, and reference/acronym/
+glossary spacing that matches `prodockit.pdf`'s own PDF output - as Jinja
+variables/macros for Zensical's own macros plugin:
+
+```toml
+[project.markdown_extensions.zensical.extensions.macros]
+modules = ["prodockit.zensical_macros"]
+```
+
+See the [docs](https://buckwem.github.io/prodockit-extensions/macros/) for the
+full variable/macro list.
+
+## Development
+
+```bash
+python -m venv .venv
+source .venv/bin/activate
+pip install -e ".[dev]"
+pytest
+```
+
+`zensical` is a core dependency, so `zensical serve` is available as soon as
+`prodockit` is installed - no extra step needed to build the documentation
+locally.
+
+## License
+
+MIT - see [LICENSE](LICENSE).