Bendik Aagaard LynghaugandClaude Opus 5.5
641c5f1bd3
Test / test (pull_request) Successful in 51s
From an empty Kanidm to everyone at their own desk: what in the content decides who needs an account, the four things Kanidm needs for portal, the first person, what happens at start, how everyone after comes in from the desks, what the people who ask the questions can do, and what each failure looks like. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GT37Z1Xtfd9pUuQtMTg6Yt
24 lines
1.3 KiB
Markdown
24 lines
1.3 KiB
Markdown
# portal documentation
|
|
|
|
Portal turns a Git repo of YAML into a running site. Almost everything
|
|
here is about that YAML: what a content repo may say, and what the
|
|
engine does with it.
|
|
|
|
| | |
|
|
|---|---|
|
|
| [Getting started](getting-started.md) | Bringing your people in: from an empty Kanidm to everyone at their own desk, from what the content says. |
|
|
| [Architecture](architecture.md) | What the engine is made of and where each piece lives in the source. |
|
|
| [Content reference](content-reference.md) | Every key a content repo may write, and what it does. |
|
|
| [State machines](state-machines.md) | `aggregates.yaml`: stages, who moves a case, mail, deadlines, memberships. |
|
|
| [Access](access.md) | How the Cedar policy is compiled from content, and who may ask it what. |
|
|
| [Operations](operations.md) | Releasing, deploying, adding a site, environment variables. |
|
|
| [Filesystem routes](design/filesystem-routes.md) | Why the `questions/` tree is the router. |
|
|
|
|
Two repos in the same family carry their own docs:
|
|
|
|
- [uhhm/iris](https://project.uhhm.no/uhhm/iris) — the lint. Versioned
|
|
as portal and released by portal's publish job; it is the thing a
|
|
content repo's CI runs before anything reaches a site.
|
|
- [uhhm/gdo](https://project.uhhm.no/uhhm/gdo) — the mailer. Delivers
|
|
what content asked to be sent, and carries replies back.
|