This document describes how you can contribute documentation to Promitor.
The documentation for Promitor is stored in /docs.
Documentation is written in Markdown and uses MkDocs for Material to generate a static website that is served with GitHub Pages from the live-docs branch.
In addition, Mike is being used to leverage versioned documentation.
For every new Promitor version, a new Git tag is created which automatically builds and pushes a new doc version. Next to that, every push on main branch will update the unreleased version of the documentation that is automatically published through GitHub Actions.
Documenting a new scraper is fairly simple and only requires a few steps in the docs\ folder:
- Create a new document in
scraping\providersbased onscraping\scraper.md.template. - Add the new scraper to the navigation in
mkdocs.yml.- Ensure that the scraper is listed alphabetically in the
Scrapingsection of the navigation.
- Ensure that the scraper is listed alphabetically in the
- Add the new scraper to the supported scrapers list for resource discovery in
mkdocs.yml, when applicable.- The
Supported Providerssection ofResource Discoveryin the navigation - Ensure that the scraper is listed alphabetically.
- The
- If the scraper provides scraper-specific labels, they should be documented in
scraping/labels.mdunder "Scraper-specific labels".
Every PR will automatically build and deploy a preview version of the documentation for you with Netlify. This allows you to easily contribute changes without having to fully configure your local environment.
- Install Python:
⚡ tkerkhove@tomkerkhove C:\promitor
❯ choco install python- Install dependencies
⚡ tkerkhove@tomkerkhove C:\promitor
pip install -r requirements.txt- Serve the documentation:
⚡ tkerkhove@tomkerkhove C:\promitor
mkdocs serve