Roles
7 roles described. A role is a kind of user, with the screens it uses and the processes it takes part in.
| Role | Actors | First line | Links |
|---|---|---|---|
| Author | The person who writes notes in a knowledge repository: a screen, a rule, a term, a decision, in standard markdown with the frontmatter that qualifies it and the links that assert its relations. An author never edits the model or the site; the lint of the merge request tells them what the build will say, and the to-do page what is missing. | 81 | |
| Glossary owner | The person who owns the vocabulary: writes the term notes, settles the homonyms with distinct titles or a ## Not to be confused with section, turns the keyword pages of the to-do page into definitions, and decides which candidate expressions the lock file rejects. | 35 | |
| Integrator | The person who installs the tool and connects it to a forge: creates the configuration repository, declares the sources and their typing rules, sets the pipeline that builds and publishes the site and the lint of every knowledge repository, and does the human steps a forge asks for, the Pages source and the credentials. The onboarding of a repository is their path. | 61 | |
| Maintainer | The person who keeps the tool: reviews and merges the pull requests, cuts the releases, holds the licence inventory and the security contact, and decides on a design change after the discussion it starts with. A maintainer's own small change may be merged by its author once the pipeline is green; a story is always reviewed by someone else. | 27 | |
| Quality owner | The person who reads the findings: sets the severities under checks: and the fail-on policy of the build, reads the build log and the reports of the lint in the merge requests, and holds the corpus to the rules the checks describe. | 30 | |
| Reader | The person who opens the generated site: searches, browses the index, reads a page, follows the mentions and the neighbourhood, downloads a document, pins the pages to keep at hand. A reader needs no account, no server and no JavaScript to read every page in full. | 120 | |
| Theme author | The person who gives the site the identity of the organisation: writes theme.yaml, ships the fonts and the icons, adds the project stylesheet, or overrides a slot with a component of a plugin theme, and checks the result in the gallery against the budget, the contrast and the accessibility rules. | 20 |
7 roles of 7 — pagination by twenty. The Links column counts the related pages, which brings the most central roles of the journey to the top.