Skip to main content
SoftsasiAI for Engineers
Sign in

§ masterplan.md

Refugee Family Cookbook

A storytelling recipe site where each dish carries a family story, photos and an audio narration in the cook's voice.

All ideas
Storytelling

01

App overview and objectives

A cookbook where every recipe carries the story of the person who brought it: family history, the country it came from, the substitutions exile forced, and a video of it being cooked.

02

The problem worth solving

Food is the least threatening doorway into a hard subject. A reader who cooks someone's grandmother's dish has met them in a way no news report achieves.

03

Target audience

  • Primary — Home cooks curious about unfamiliar cuisines.
  • Secondary — Diaspora communities preserving family recipes, and resettlement organisations.

04

Roles and permissions

  • Visitor — read-only public pages, can sign up.
  • Member — owns their own records, cannot see other users' data.

05

Core features

  • Recipe pages with the cook's story woven through the method
  • Video of the dish being cooked by its owner
  • Ingredient notes with substitutions available in the destination country
  • Cook profiles with origin, journey summary and consent-respecting detail
  • Origin map linking dishes to places
  • Support section directing revenue and attention to contributing cooks

Deliberately later

  • Print cookbook
  • Supper club event listings
  • Contributor payment platform

06

Technical stack

Static-rendered content site with structured recipe data, video hosted externally, a small CMS for contributors.

Why: Recipes benefit hugely from structured data and search indexing, and static delivery keeps a media-heavy site fast.

Alternatives: A recipe platform (built-in audience, strips the storytelling) or a video channel (great reach, terrible as a reference while cooking).

07

Conceptual data model

Recipe — cook, title, origin, ingredients, steps, time, difficulty, video

Cook — name or pseudonym, origin, current city, story, consent scope

Ingredient — name, local substitute, where to buy note

Story — cook, narrative sections, media

SupportLink — cook or organisation, type, url, verified

08

Integrations

  • Video hosting
  • Structured recipe markup for search
  • Map for origins
  • Payment link for contributor support

09

UI design principles

  • Scroll is the narrative device: each section reveals one beat of the story.
  • Full-bleed imagery alternating with quiet text-only moments to let the reader breathe.
  • Always offer a skip-to-summary path for readers who want the facts fast.

10

Security considerations

  • Cooks control how identifiable they are, including pseudonyms and no-face video options.
  • Consent recorded per recipe and per media item, revocable.
  • No sale of contributor data; any revenue share documented publicly.

11

Development phases

Phase 1 — Prove the core

  • — Recipe pages with the cook's story woven through the method
  • — Video of the dish being cooked by its owner
  • — Ingredient notes with substitutions available in the destination country
  • — Static content and design system in place
  • — Basic analytics

Phase 2 — Make it real

  • — Cook profiles with origin, journey summary and consent-respecting detail
  • — Origin map linking dishes to places
  • — Support section directing revenue and attention to contributing cooks
  • — Accounts, sign-in and password reset
  • — Empty, loading and error states everywhere

Phase 3 — Polish and launch

  • — Performance, accessibility and SEO pass
  • — Legal pages, contact route and 404 handling
  • — Wire up: Video hosting
  • — Wire up: Structured recipe markup for search

Phase 4 — Grow

  • — Print cookbook
  • — Supper club event listings
  • — Contributor payment platform

12

Challenges and solutions

Risk — The project extracts stories without returning value

Solution — Contributor payment or revenue share agreed in writing before publication.

Risk — Ingredients unavailable to readers

Solution — Every recipe ships with tested substitutions for at least one destination country.

Risk — Video production cost

Solution — Phone-shot vertical video with good audio beats an expensive shoot; supply a clip-on microphone.

13

Future expansion

  • Restaurant incubator partnerships
  • Language editions
  • Community kitchen events

14

Page list (13 pages)

  1. 01 PUBLIC Recipes — Browse dishes by cuisine and time.
  2. 02 PUBLIC Cooks — The people behind the food.
  3. 03 PUBLIC Stories — Longer-form journeys.
  4. 04 PUBLIC Origins — Map of where dishes come from.
  5. 05 PUBLIC Support — How to pay the cooks back.
  6. 06 AUTH Sign up — Create an account with email or a social provider.
  7. 07 AUTH Log in — Return to the account, with error and lockout states.
  8. 08 AUTH Reset password — Request a reset link and set a new password.
  9. 09 APP (signed in) Account settings — Profile, email, password, language and delete account.
  10. 10 PUBLIC Contact — Contact form plus real address, phone and email.
  11. 11 LEGAL & SYSTEM Privacy policy — What data is collected, why, and how to remove it.
  12. 12 LEGAL & SYSTEM Terms of service — Rules of use, liability and account termination.
  13. 13 LEGAL & SYSTEM 404 not found — Friendly dead end with search and links back.

15

Page map

PUBLIC      AUTH               APP (signed in)      LEGAL & SYSTEM
──────────  ─────────────────  ───────────────────  ───────────────────
├─ Recipes  ├─ Sign up         └─ Account settings  ├─ Privacy policy
├─ Cooks    ├─ Log in                               ├─ Terms of service
├─ Stories  └─ Reset password                       └─ 404 not found
├─ Origins
├─ Support
└─ Contact

key flows:
  Recipes ──▶ Cooks
  Cooks ──▶ Stories
  Origins ──▶ Recipes
  Stories ──▶ Support