Keep a public open-data site checkable and easy to join - sources, freshness, method, limits, privacy, licence and how to contribute visible on each page. Use when you add or review a page, a section or a panel that shows data to the public.
# citizen-science
People trust an open-data site only when they can see where each number comes from and how old
it is. People join only when the way in is clear. This skill says what must be on the page. Use
it with `web-ui`, which says how the page looks.
## What each page carries
| Item | Rule |
|---|---|
| Data sources | Each number on the screen names its provider, with a link |
| Freshness | Show when the data was computed and when a sample was taken. Flag old data in words |
| Method | One click from the data to how the score is made |
| Limits | Say what is missing or estimated. Never fill a gap silently |
| Privacy | Say that there are no cookies and no tracking of your own. Name each third party that gets a request. A location never leaves the browser |
| Open code | The repository and the docs are one click from each page |
| Money | Costs and donations are public |
| Contribute | A visitor finds the issue tracker and the docs from the page they are on |
## Rules
- **No claim without a source.** A new panel that shows a number names its provider and date.
- **Official verdicts word for word.** Show the agency's own words, with the sample point and
the date.
- **Safety first, plainly.** Unsafe conditions are red with the reason. A safety note is never
hidden behind a hover.
- **No dark patterns.** No cookie banner tricks, no sign-up walls.
- **"Soon" is honest.** A section that does not exist is muted text, not a dead link.
## Review
Before a visible change is done, a first-time visitor can answer these from the page alone:
1. Where does this number come from?
2. How old is it?
3. What does it not know?
4. Does anyone track me?
5. How do I help, or check the code?
If one answer needs a guess, change the page.
h0ffmann/skills