Clarify user personas in documentation

[rudokemper]

As we expand Guardian Connector documentation, it’s becoming clear that different pages serve very different audiences. For example:

• A community organization’s technical data manager that wants to set up a Windmill script
• A system administrator / developer deploying GC
• A casual reader curious about GC principles

Right now, these audiences are not always explicitly signaled. This can create friction if someone stumbles onto a page not meant for them.

Proposal

1. Define user personas in one central page (e.g. "Who this documentation is for") and refer back to it throughout the docs.
2. Mark each page with its intended audience at the top (e.g. “This page is written for: System administrators”).
3. Audit existing docs and tag them with personas.

Related discussions

• Add "Common workflows" section with two pages (download all data, use data in QGIS) #54
• 'pip install stack-deploy-tool' instead of making users check-out git repo gc-deploy#44
  • If we implement the work in this issue, we should follow up on deciding where deployment instructions go, as discussed in the linked thread.

[rudokemper]

@nicopace would you want to work on this at some point?