This project uses MkDocs with Material theme for documentation, automatically deployed to both GitHub Pages and GitLab Pages.
- GitHub Pages: https://bvandewe.github.io/events-player/
- GitLab Pages: Check your GitLab project Settings > Pages for the URL
Documentation is automatically built and deployed when:
- Push to
mainbranch - Create a new tag (e.g.,
v0.2.0) - Manual workflow dispatch (Actions tab)
- Push to the default branch (
main) - Create a new tag
All dependencies are listed in docs-requirements.txt:
pip install -r docs-requirements.txtOr install individually:
pip install mkdocs mkdocs-material pymdown-extensions
pip install mkdocs-awesome-pages-plugin
pip install mkdocs-git-revision-date-localized-plugin
pip install mikemkdocs serveAccess at: http://127.0.0.1:8884
mkdocs build --clean --verboseOutput in site/ directory
- Go to Settings > Pages in your GitHub repository
- Under Source, select "GitHub Actions" (NOT "Deploy from a branch")
- Push to
mainbranch or trigger workflow manually - Check Actions tab for deployment status
Current Issue: If set to "Deploy from a branch", the documentation won't build.
See GITHUB_PAGES_FIX.md for detailed instructions.
GitLab Pages deploys automatically via the pages job in .gitlab-ci.yml:
- Check CI/CD > Pipelines for job status
- Go to Settings > Pages to view your docs URL
- Configure access level (public/private) if needed
- mkdocs.yml - MkDocs configuration
- docs-requirements.txt - Python dependencies
- .github/workflows/deploy-docs.yml - GitHub Actions workflow
- .gitlab-ci.yml - GitLab CI/CD (includes
pagesjob)
- Content: Edit Markdown files in
docs/ - Theme: Modify settings in
mkdocs.yml - Styling: Custom CSS in
docs/assets/css/custom.css - Scripts: Custom JS in
docs/assets/js/
- Check the Actions tab for error logs
- Verify all dependencies in
docs-requirements.txtare compatible - Ensure GitHub Pages is set to "GitHub Actions" as source
- Check workflow has proper permissions (pages: write, id-token: write)
- Check CI/CD > Pipelines for the
pagesjob status - Verify the job creates a
public/directory - Check that
docs-requirements.txtis present - Review job logs for build errors
- Update dependencies:
pip install -r docs-requirements.txt --upgrade - Clear cache:
rm -rf site/ - Rebuild:
mkdocs build --clean --verbose - Check for broken links or missing pages
If you see errors about missing plugins, ensure all dependencies are installed:
pip install -r docs-requirements.txt