Setting up {{brand}} for the first time: a 15-minute walkthrough.

import { TLDR, InTheApp, RelatedReading } from '@/components/kb-blocks'

<TLDR items={[ "Fifteen minutes from sign-up to first logged activity. That is the whole first session.", "Sign up, add one child, log one activity, close the app. Nothing else is required on day one.", "If you are stuck, email {{supportEmail}}. A real person reads it.", ]} />

Short answer

Sign up, add one child, log one activity, close the app. About fifteen minutes. Do not try to set up the schedule, the curriculum heatmap or the council report today.

Walk-through

1. Sign up at {{appUrl}} with an email address and a password. You will get a magic-link confirmation email to click.
2. Add your first child. One child. You can add siblings later. Enter their name, date of birth and (if you know it) their Montessori plane. If the word "plane" is unfamiliar, leave the field blank; the dedicated help article on adding a child explains it.
3. Log one activity. Anything. The first tray your child used, the book you read at bedtime, the walk you went on. Open the activity log, pick a category, type a sentence about what happened.
4. Close the app for the rest of the day. Resist the urge to explore every menu. The app will still be there tomorrow.

If that did not work

• If the magic-link email did not arrive, check the spam folder. If it is not there, email {{supportEmail}} and we will send it manually.
• If the plane field confused you, leave it blank. You can add it later from the child's profile.
• If the activity log would not save, check your internet connection and try once more.

If you are still stuck, email {{supportEmail}}. A real person reads it.

{/*

Review log

2026-04-19 kb-new-homeschool-mum (Sarah): PASS

Read as a mum who just signed up at 10pm on a Tuesday.

• "Fifteen minutes from sign-up to first logged activity. That is the whole first session." Exactly the permission to stop I needed.
• Four numbered steps, each a sentence. No feature tour. No "explore the schedule". "Close the app for the rest of the day." Love this.
• "If the word 'plane' is unfamiliar, leave the field blank." Removes the single most stressful first-setup moment.
• Plain-English "if the magic-link email did not arrive" troubleshooting list. No jargon.
• Real-person promise at the end, with the support email.

Nothing blocking. Ready for SEO.

2026-04-19 kb-seo: PASS

• seo_title 46 chars with {{brand}} template variable (resolves at build time).
• seo_description 141 chars; direct, promise-shaped.
• H1 mirrors the title.
• seo_schema_type is [Article] (help articles do not need FAQPage; the walk-through is numbered steps, not Q&As).
• Internal links to next two help articles in this wave (add a child, logging) plus the record-keeping-cadence article for context.
• UK spelling clean.

Nothing blocking. Ready for brand-guardian.

2026-04-19 kb-brand-guardian: PASS, no edits required

• Zero em-dash or en-dash characters.
• Zero exclamation marks.
• British English.
• All brand references use {{brand}}, {{appUrl}}, {{supportEmail}} template variables throughout; zero hardcoded brand names.
• No banned words; no forced cheer.
• Tone: calm, anti-feature-tour, permission-to-stop.

Status set to ready-to-import. */}

<RelatedReading internal={[ {slug: "adding-a-child-developmental-plane", title: "Adding a child: what's a 'developmental plane' and why is the app asking?"}, {slug: "logging-first-activity-home-ed", title: "Logging your first activity: what the fields actually mean"}, {slug: "home-ed-record-keeping-cadence", title: "A home-ed record-keeping cadence that does not burn you out"}, ]} external={[]} />