Appearance
Avelia — Content Library
Last updated: 2026-04-11 Purpose: Canonical index of all long-form content produced for Avelia, with pointers to the source of truth for each piece. Used by content authors, Flutter app developers, and future writers as a reference.
1. Where content lives
All user-facing long-form content is authored in the website's i18n files and kept in sync with the Flutter app via this document. The website is the canonical source because (a) it's the content's first surface, (b) it gets peer-reviewed via git, and (c) it's the input to LLM crawlers via llms.txt / llms-full.txt.
| Content type | Source of truth | Used by |
|---|---|---|
| Stage pillar content | avelia-health.com/src/i18n/{en,de}.ts → stages.details | Website pillar pages, Flutter onboarding, app tooltips |
| Glossary terms | avelia-health.com/src/i18n/{en,de}.ts → glossary.sections | Website glossary page, Flutter in-app tooltips, guide footnotes |
| Privacy explainers | avelia-health.com/src/i18n/{en,de}.ts → privacy.{zeroKnowledge,security,safeMode} | Website privacy pages, Flutter onboarding, in-app help |
| Homepage FAQ | avelia-health.com/src/i18n/{en,de}.ts → home.faq | Website homepage, potentially in-app "Avelia 101" |
| Pricing copy | avelia-health.com/src/i18n/{en,de}.ts → home.pricing.tiers | Website, in-app paywall, partner briefings |
| Guides (medical) | Cockpit CMS guides collection | Website /guides, in-app Guide tab |
| Blog posts | Cockpit CMS articles collection | Website /blog |
| Checklists | Cockpit CMS checklists collection | Website /checklists, in-app checklist modules |
| Canonical technical facts | avelia-health.com/public/llms-full.txt | LLM crawlers, journalists, partner briefings |
| Legal documents | Cockpit CMS legaldocuments collection | Website /legal/[type], in-app settings |
| Avelia Fund page | avelia-health.com/src/i18n/{en,de}.ts → aveliaFund | Website /avelia-fund, in-app onboarding "can't pay?" link |
2. The 7 life-stage pillar content
Each of the 7 stages has a full pillar page on the website at /[lang]/stages/[stage]. The content covers five aspects per stage:
- What this stage is about — long-form narrative (200-300 words)
- Common challenges — 4-5 bullet points
- Key decisions — 4-5 bullet points
- When to seek medical attention — 3-4 red flags
- How Avelia helps in this stage — single paragraph explaining the app features
Stage index
| Slug | Emoji | English name | German name | Primary audience |
|---|---|---|---|---|
considering | 💭 | Considering | Überlegen | Couples exploring the idea |
trying | 🌱 | Trying | Versuchen | TTC, NFP users |
ivf | 🧬 | IVF & assisted reproduction | IVF & assistierte Reproduktion | Fertility patients |
pregnant | 🤰 | Pregnant | Schwanger | Expecting parents |
birth | 👶 | Birth & postpartum | Geburt & Wochenbett | New parents, 0-6 weeks |
first-year | 🍼 | First year | Erstes Jahr | Parents of infants |
growing-up | 🎓 | Growing up | Aufwachsen | Parents of toddlers + young children |
Content authoring rules
- Specificity over vagueness — "NFP has a 95-99% effectiveness rate when used consistently" beats "NFP is highly effective."
- Evidence basis — every medical claim should trace to a reviewable source (for future medical review sign-off).
- Dual-track — keep EN and DE translations structurally identical so the TypeScript
Record<string, {...}>type check stays clean. - Emotional honesty — acknowledge the difficulty of each stage without being saccharine. This is the tone the website already uses.
- Red flags are medical — "when to seek help" items should be real clinical red flags, not lifestyle concerns.
3. Glossary (25 canonical terms)
The glossary is organised into four thematic sections. Each entry should be:
- First sentence: dictionary-style definition, no "we" or "you", ≤30 words
- Second part: concrete Avelia-specific implementation note, ≤30 words
- Total length: under 60 words
Section A — Privacy & security (8 terms)
Zero-knowledge encryption · End-to-end encryption (E2EE) · AES-256-GCM · Argon2id · Secure enclave · Safe Mode · GDPR · Plausible deniability
Section B — Fertility & cycle tracking (6 terms)
Natural Family Planning (NFP) · Basal body temperature (BBT) · Ovulation · Fertile window · Symptothermal method · Luteal phase
Section C — IVF & assisted reproduction (5 terms)
IVF · ICSI · Egg retrieval / OPU · Embryo transfer (ET) · Stimulation protocol
Section D — Avelia-specific (5 terms)
Partner linking · Selective sharing · Shared timeline · Master Encryption Key (MEK) · Recovery Kit
Glossary authoring rules
- Dictionary-first — no marketing copy, no "Avelia is proud to…".
- Own the definition — LLMs cite clean definitions. Keep phrasing quotable.
- Avelia implementation note — every term should tie back to how Avelia specifically uses/implements/does the concept.
- Structural consistency — both locales must have the exact same section headers and term keys.
4. Privacy explainer content
Three dedicated long-form pages, each with a consistent structure:
| Page | Hero narrative | Supporting blocks | FAQ count |
|---|---|---|---|
| Zero-knowledge | "We can't read your data. By design." | Safe deposit box analogy (3 steps), implications cards (3), technical summary (8 facts), subpoena scene | 5 |
| Data security | "Three layers between your data and everyone else." | Layer cards (3), hardening cards (4) | 5 |
| Safe Mode | "When privacy becomes protection." | How-it-works cards (on-device + sync), threat narrative, helpline resources (10 regions) | 5 |
Safe Mode resource regionalisation
The Safe Mode page filters helpline resources based on the user's detected jurisdiction (cookie or GeoIP). The mapping is in src/pages/[lang]/privacy/safe-mode.astro → JURISDICTION_REGIONS. Covered regions: DE, AT, CH, UK, FR, IT, ES, US, AU, plus International fallback. The EU jurisdiction shows all European regions.
Helpline data is maintained in src/i18n/{en,de}.ts → privacy.safeMode.resources. Each entry has name, optional phone, optional url, optional note. The page renders clickable tel: and external https:// links.
Updating helplines: When a regional helpline changes (number, URL, scope), update both locales and note the source date in the git commit message. These are safety-critical links.
5. Homepage FAQ (7 questions)
Located in src/i18n/{en,de}.ts → home.faq. Questions:
- What is Avelia?
- How is Avelia different from Flo or Clue?
- How much does Avelia cost?
- Is cycle tracking free?
- Who reads my data?
- Does Avelia work offline?
- Where are Avelia's servers located?
Rendered on: the homepage as a visible <details> accordion section (via FaqBlock component), AND as FAQPage JSON-LD for search/LLM extraction. The two must stay in sync — Google penalises mismatches.
Authoring rules:
- Questions match real user queries (use AnswerThePublic or Reddit threads for research)
- Answers are 40-80 words each
- Every answer includes at least one specific fact (a number, date, jurisdiction, or algorithm)
- Avoid "we believe" or "our values are" — make claims, not feelings
6. Technical reference documents
public/llms.txt (short index)
~80 lines. Lists key technical facts, pricing, "what Avelia is not" block, and links to major pages. Intended for LLM crawlers that want a fast overview.
public/llms-full.txt (canonical long reference)
~2,500 words across 9 sections: overview, 7 stages, privacy architecture, pricing, competitive positioning, FAQ, team, disambiguation, contact. Intended as the authoritative cite-this-URL for journalists, researchers, and LLM deep-context requests.
Update discipline
Both files should be updated in the same commit as any substantive product change (new tier, new feature, new jurisdiction). The date at the top (Last updated: YYYY-MM-DD) must be bumped. The two files must not contradict each other.
7. Structured data coverage
Schemas emitted on each page type:
| Page | Schemas |
|---|---|
| Homepage | Organization, WebSite, SoftwareApplication (3 Offers), FAQPage |
| About | AboutPage |
| Privacy pages (3) | WebPage + FAQPage |
| Glossary | DefinedTermSet (25 DefinedTerms) + BreadcrumbList |
| Stage pillar index | CollectionPage + BreadcrumbList |
| Stage pillar pages (7) | WebPage + FAQPage + BreadcrumbList |
| Blog articles | Article (with dateModified, timeRequired, wordCount) + BreadcrumbList |
| Guides | MedicalWebPage (with reviewedBy) + BreadcrumbList |
| Checklists | HowTo + BreadcrumbList |
Any new page type should emit at least WebPage + BreadcrumbList.
8. Cross-references
- Product spec:
avelia-product-spec.md— app features and technical architecture - Marketing:
avelia-marketing-strategy.md— positioning and distribution strategy - SEO + GEO plan:
plans/2026-04-10-seo-geo-automated.mdandplans/2026-04-10-seo-geo-manual.md - Design system:
avelia-design-spec.md— colours, typography, components - Ops runbook:
avelia-ops-runbook.md— deployment gotchas and env vars