Contributing
Propose changes through a branch and pull request. Keep changes focused, explain the GeoEpi use case, and update linked templates or resources when a page changes their meaning.
For substantive guidance, include the source or experience behind the recommendation and distinguish a useful group convention from an actual institutional, contractual, security, or scientific requirement. Reviewers should check clarity, accessibility, scientific accuracy, links, and whether the proposed guidance fits the practical GeoEpi operating model.
Render the full site locally with quarto render before opening a pull request. The validation script checks active-page metadata, internal links, templates, and generated output. Do not commit _site/, credentials, tokens, or local IDE state.