This repository contains the user-facing documentation for the MAD4HATTER amplicon sequencing pipeline. The documentation is built with MkDocs and automatically deployed to GitHub Pages.
The documentation provides comprehensive guides for using the MAD4HATTER pipeline, including installation instructions, execution parameters, pipeline outputs, and configuration options for custom amplicon pools. The live documentation is available at https://eppicenter.github.io/wonderland-docs/.
This documentation site is built with MkDocs and the Material theme, and is automatically deployed to GitHub Pages via GitHub Actions.
- Python 3.x
- pip
-
Install dependencies:
pip install -r requirements.txt
-
Preview the site locally:
mkdocs serve
The site will be available at
http://127.0.0.1:8000/ -
Build the site (without serving):
mkdocs build
The built site will be in the
site/directory (which is gitignored).
- Documentation source files: Located in the
docs/directory- Main pages:
docs/*.md - Assets (images, CSS):
docs/assets/
- Main pages:
- Configuration:
mkdocs.ymlin the repository root - Custom styling:
docs/assets/css/custom.css
-
Add a new page:
- Create a new Markdown file in
docs/or an appropriate subdirectory - Add it to the
navsection inmkdocs.yml
- Create a new Markdown file in
-
Edit an existing page:
- Edit the corresponding
.mdfile indocs/ - Use
mkdocs serveto preview changes in real-time
- Edit the corresponding
-
Update navigation:
- Edit the
navsection inmkdocs.yml - Follow the existing structure and indentation
- Edit the
-
Add images:
- Place images in
docs/assets/images/ - Reference them using relative paths:

- Place images in
- Use clear, concise language
- Include code examples where helpful
- Use MkDocs Material features:
- Admonitions (notes, warnings, tips) using
!!! note,!!! warning, etc. - Code blocks with syntax highlighting
- Tables for structured information
- Links to other documentation pages
- Admonitions (notes, warnings, tips) using
The documentation is automatically deployed to GitHub Pages when changes are pushed to the main or master branches.
The deployment is handled by the GitHub Actions workflow in .github/workflows/docs.yml.
- Go to repository Settings → Pages
- Under "Source", select "GitHub Actions" (not "Deploy from a branch")
- The workflow will automatically deploy on every push to the configured branches
Before committing documentation changes:
- Run
mkdocs serveand review all changes in the browser - Check that all links work correctly
- Verify images display properly
- Ensure the navigation structure makes sense
- Test on different screen sizes if possible
Documentation dependencies are listed in requirements.txt:
mkdocs>=1.5.0mkdocs-material>=9.0.0mkdocs-git-revision-date-localized-plugin>=1.2.0pymdown-extensions>=10.0mkdocs-minify-plugin>=0.7.0mike>=1.1.0
When contributing to the documentation:
- Make changes in a feature branch
- Test locally with
mkdocs serve - Submit a pull request
- Documentation will be automatically deployed once merged to the main branch