Files

T

Bendik Aagaard LynghaugandClaude Fable 5.1 268d545843 A releases manifest renders as a download card, the device's file first

A kind: url resource whose JSON is a releases manifest - latest,
versions newest first with per-platform assets, channels such as a
package repo or TestFlight - is one card: the newest version, the file
for the visitor's own platform (read from the browser on hydration;
the server renders every file), the Linux package repo lines beside a
Linux file, TestFlight for iPhones and Macs, and the rest folded under
"All downloads". Decided by shape, as every resource is; written for
redoal's public releases at dl.redoal.com.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

2026-10-05 12:48:31 +02:00

design

Docs: routing bullet + design doc marked implemented

2026-08-24 22:33:37 +02:00

access.md

Memberships: groups kept by portal itself, a person by phone number first

2026-09-30 13:28:28 +02:00

architecture.md

Sessions outlive the deploy that interrupted them

2026-09-28 16:38:05 +02:00

content-reference.md

A releases manifest renders as a download card, the device's file first

2026-10-05 12:48:31 +02:00

getting-started.md

Docs: the examples in English

2026-09-30 15:31:59 +02:00

lint-changelog.md

One binary: the lint and the trainer are commands of portal

2026-09-30 15:29:30 +02:00

lint.md

iris check --findings: every finding as JSON with a stable id

2026-10-03 10:48:09 +02:00

mail.md

One set of mail variables for every mail, and {link} in state mails

2026-10-02 11:25:49 +02:00

memberships.md

Docs: the examples in English

2026-09-30 15:31:59 +02:00

operations.md

Rate limit: a hundred at once, ten a second, and the page's own files are not counted

2026-09-30 19:51:48 +02:00

README.md

One binary: the lint and the trainer are commands of portal

2026-09-30 15:29:30 +02:00

state-machines.md

One set of mail variables for every mail, and {link} in state mails

2026-10-02 11:25:49 +02:00

storylines.md

Docs: the examples in English

2026-09-30 15:31:59 +02:00

SUMMARY.md

One set of mail variables for every mail, and {link} in state mails

2026-10-02 11:25:49 +02:00

training.md

generate follows its findings through, and stops when it stalls

2026-10-03 10:48:09 +02:00

README.md

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	Bringing your people in: from an empty Kanidm to everyone at their own desk, from what the content says.
Architecture	What the engine is made of and where each piece lives in the source.
Content reference	Every key a content repo may write, and what it does.
State machines	`aggregates.yaml`: stages, who moves a case, mail, deadlines, memberships.
Access	How the Cedar policy is compiled from content, and who may ask it what.
Storylines	The same site told several ways: lists of texts, one storyline per visitor, counted per storyline.
Memberships	Groups kept by portal itself: a membership as a case, a person as a phone number first, and the provider only saying who.
Operations	Releasing, deploying, adding a site, environment variables.
Training a site	`portal plan` and `portal build`: a business in plain words becomes a content repo, held to the lint.
The lint	`portal lint`: what a content repo's CI runs before anything reaches a site.
Filesystem routes	Why the `questions/` tree is the router.

One repo in the same family carries its own docs:

uhhm/gdo — the mailer. Delivers what content asked to be sent, and carries replies back.

The lint (once uhhm/iris) and the trainer (once uhhm/portal-trainer) are commands of the portal binary since 0.6; their chapters are above, and the trainer's runs stay in the old repo.