[amjjbonvin]

What does this PR do and why?

Adds a documentation site, https://www.bonvinlab.org/disvis, built with MkDocs Material and deployed to GitHub Pages, as for PowerFit and WHISCY.

• Pages: home, installation, manual, example, performance, contributing, CLI reference, and "Try it in your browser". They include sections of README.md, INSTALLATION.md, CONTRIBUTING.md and test-cases/README.md (between <!-- --8<-- [start:x] --> markers, invisible on GitHub and PyPI), so nothing is duplicated.
• New text: a recommended workflow and the web service (form and scanning modes, taken from the portal's help page and submit form).
• The CLI reference is generated from the disvis arguments (mkdocs-rich-argparse); the example page links the reports of the CPU reference results (Write an HTML report with a Mol* view (--no-report to turn it off) #49).
• A JupyterLite notebook runs the PRE5-PUP2 test case in the browser (quick scan, ~30 s) and shows the report with the Mol* view. The WebAssembly wheel is built from the source with cibuildwheel, as in pypi-publish.yml, since the 3.0.0 wheel on PyPI has no report.
• docs extra, docs/Makefile (make -C docs, make -C docs serve) and .github/workflows/pages.yml (builds on PRs, deploys from main).
• README: link to the site; the links to aidecl.yaml and CHANGELOG.md are now absolute (they were broken on PyPI). CONTRIBUTING.md explains how to build the site.

How was this tested?

• make -C docs from a clean state: wheel, mkdocs build --strict, JupyterLite.
• Pages and an example report checked in headless Chrome over HTTP.
• WebAssembly wheel: the unit tests pass in Pyodide, and a 9.72° run gives output byte-identical to cpu/coarse.
• Notebook: all cells run in headless Chrome, and checked by hand in a browser.
• Manually checked a local version of the manual in a web browser

Not tested: the Pages workflow on GitHub (this PR runs its build job), and the deployment.

AI assistance

Written with Claude Code; checked as above.

Checklist

• Tests cover the new and/or changed code
• Documentation updated if needed (README.md, INSTALLATION.md)
• Reference results in test-cases/*/example-results/ updated if the output changes (output unchanged)

Related issues

Closes #50

Notes for reviewers

• GitHub Pages must be enabled for the repository (Settings → Pages → Source: GitHub Actions) before the first deployment.
• jupyterlite-pyodide-kernel==0.8.7 and cibuildwheel==4.3.5 are pinned together: the Pyodide ABI of the wheel (2026_0) must match that of the JupyterLite kernel. PowerFit pins only the build side.
• docs/test-cases is a symlink to test-cases/ (as WHISCY links example/), so the site can serve the example reports.

🤖 Generated with Claude Code