Skip to content
Skip to this exploration
All explorations

Practical self-hosting · intermediate

13 · Design the first five minutes

Make a family service understandable without exposing extra access.

10 min 5 sectionsv1

What you can take away

  • Storyboard an invitation and test a reader's denied actions.
  • Storyboard invitation, first login, successful task, denied action, forgotten credentials, and return visit

Your trail through this idea

Checking saved progress…

Ian asked for family accounts and single sign-on through Authentik. That historical request is a human problem as much as a configuration problem: a person needs to know where to start, what they can do, and where to get help.

Prerequisite: complete the preceding lesson or bring its worksheet.

Mark sections complete when you choose. Reading alone does not mark them.

Understand the system

Authentik describes its identity and user-management role. The surrounding application experience still needs careful design. An invitation should explain the service’s purpose and expected access. A login error should not reveal whether a particular private account exists. A permission error should offer a useful next step without encouraging someone to request administrator access for routine use.

Treat onboarding as a sequence of observable tasks rather than a tour of settings. If the person wants to hear a radio station or read an approved family story, the test is whether they can do that safely on their own device.

Checking saved progress…

Work through the case

Original personas: Reader wants approved lessons; Editor maintains lesson drafts; Operator restores the service. These roles are fictional design aids, not named family members. Try the same page with each role. A hidden edit button is not enough: the server must deny unauthorized edit requests.

Checking saved progress…

Make something useful

Try this

Original exercise

Storyboard invitation, first login, successful task, denied action, forgotten credentials, and return visit. Use fictional names and a reserved example domain. Have another person act as Reader with the storyboard only. Record where they hesitate. For a real staging test, use synthetic accounts, remove them afterward, and preserve no private screenshots.

Checking saved progress…

Check your reasoning

A quick check · for your own learning

What is a useful reader-role test?

Choose one answer

A self-study prompt. You can retry; this is not an exam.

Checking saved progress…

Keep the result and follow the sources

Deliver a one-page welcome and a role test matrix. If the welcome needs to explain containers, GPU routing, or database migrations, those details probably belong in the operator handbook instead.

Sources and scope

  • Primary documentation or archival source, reviewed 14 November 2026. Additional direct links appear beside the claims they support.
  • Editorial basis: Ian's historical self-hosting questions and current repository inspection informed the case selection. Historical requests do not establish current deployment. Private chat records, credentials and host details are excluded.
  • Examples and exercises are original educational synthesis. External sources support the stated technical or historical context, not every hypothetical scenario.
Checking saved progress…

These checks are for reflection and practice. Your answers and reflection notes are not sent anywhere.

Back to all explorations