Official documentation of InGrid
InGrid is a modular software programme that can be used in a variety of ways: The core components are a web portal, a search engine, a metadata catalogue with profiles for recording INSPIRE-compliant metadata, open data and EIA projects, a visualisation component for OGC Web Map Services, a client for visualising time series and various access and query interfaces that are responsible for researching the connected components, but also for forwarding the results to external systems.
Website: https://www.ingrid-oss.eu
The documentation is organized in versions. Each version has its branch.
- Branches starting with
version/contain version specific documentation. - The default branch
draftcontains unreleased changes and is long lived. - See .docs-version to check which version the branch represents.
- Deployment is automated with GitHub workflows.
Once you found the correct branch, you can start to edit the documentation.
Tip: If you wish to add new markdown files you need to include them in mkdocs.yml at field
nav.
- Sign in and go to folder docs. Open the markdown you want to edit.
- Click ✏️ Edit (top-right of the file view).
- Make your changes in the editor.
- Press
Commit changes. - Add a commit message and press
Commit changesin the bottom-right on the dialog box.
Tip: If you don’t see the edit button, you likely don’t have write access — fork the repo and open a PR instead.
# 1) Clone repo
git clone https://github.com/informationgrid/ingrid-oss.eu.git
cd ingrid-oss.eu
# 2) Checkout the branch that contains the version you want to edit
git checkout your-branch-name
# 3) Edit docs files in folder "docs" with your editor, then:
git add .
git commit -m "Describe what you changed"
# 4) Push your commit
git pushIf you wish to add more complex changes (e.g. add new markdowns, edit navigation), you might want to preview your changes.
If you wish to edit the layout go to folder theme.
Here are 2 options how you can develop and preview this documentation locally:
- Open repo in VS Code
- Install VS Code extension
Dev Containers - Press
F1and run the commandDev Containers: Reopen in container - Open new terminal and run
mkdocs serve
Edit Theme: Run
mkdocs serve --watch-themeto edit files in theme folder.
Install python and pip. It is recommended to use a python environment. Recommended Python version is 3.13.
# Create a virtual env
python3 -m venv ./.venv
# Activate virtual env
source ./.venv/bin/activate
# Install requirements
pip install -r requirements.txt
# Start MkDocs
mkdocs serve
# If you wish to edit the theme run
mkdocs serve --watch-themeA new version is released based on the draft version/branch.
- Checkout branch
draft - Make sure everything is checked in and pushed.
- Get the version of the draft from file
.docs-version - Create new tag (e.g.
git tag v8.1.0) - Push tag (e.g.
git push origin v8.1.0) - Update file
.docs-versionwith the upcoming version - Commit and push the updated
.docs-versionfile!
This triggers the following workflows:
- Workflow
.github/workflows/docs-release.yml- This workflow creates a new branch e.g.
version/8.1.0 - Docs version
8.1.0is marked aslatest
- This workflow creates a new branch e.g.
- Workflow
.github/workflows/docs-version.yml- This workflow deploys MkDocs & updates files on branch
gh-pages
- This workflow deploys MkDocs & updates files on branch
If you wish to delete a version from branch gh-pages you can delete the version tag.
- Delete tag with command
git push --delete origin v8.0.0 - By removing the tag it triggers the workflow
.github/workflows/docs-delete.yml. - This removes the version from branch
gh-pages. - The branch
version/8.0.0will NOT be deleted.
git fetchmike alias 8.0.0 latest --push
git fetchmike alias 8.0.0 draft --push
git fetchmike delete --push 8.0.0
