The most detailed free FDE + DevOps library: 140+ lessons, 70+ labs and 80 long-form articles, in English and Turkish. Start learning →

TürkçeSearch

Build with AI: From Zero to Your First App · Module 8: Finish, publish and present · Lab

One-Page Capstone Plan

40 min hands-on · Core

Browser only. No account anywhere; the plan is one page in your notes, fit-checked before building.

Three ways to do this lab. A: the browser steps below, the main path, free with no account. B: try the same task with your own AI tool if you have one (its terms and quotas apply). C: work from the provided material and the worked solution below, which teaches the same skill. No path claims you used a live AI tool when you did not.

Objectives

  • Choose theme, user and three browser-only features
  • Write scope, steps with checks, risk at position two, dates
  • Run the backend, quota and calendar fit checks

  1. Step 1

    Choose and scope

    Pick one capstone theme and one user. Choose three features that pass the three backend tests as browser-only. Write in/out lists with payment, accounts and tracking out unless your tests prove otherwise.

    plan-template.mdmarkdown
    PLAN TEMPLATE (one page)
---
Problem: ____
Theme: ____ User: ____
Features (max 3): ____
In: ____ Out: ____
Steps with checks: ____
Risk at position 2: ____
Milestones with dates: ____

  2. Step 2

    Steps and risk

    Write four to seven ordered steps with minute-checks each. Place the biggest unknown (quota behavior, layout risk, validation wording) at position two with its test.

  3. Step 3

    Fit-check

    Run three backend tests, count quota generations for the build, check the calendar. Shrink until it fits; write the verdict plus the README one-liner.

How to confirm it worked

  • Theme plus user plus max three features chosen
  • In/out lists with backend-heavy items out by test verdict
  • Steps ordered with checks, risk at position two
  • Backend, quota and calendar fit confirmed in writing

Workspace

0/2 checks passing · Coverage only, not a quality score.

Draft kept in this browser.

Hints, in three stages

Stage 1: a nudge

Three features means three. The fourth beloved idea goes on the later list with a name, not into the plan.

Stage 2: a direction

Risk at position two is load-bearing. Unknowns discovered late rework everything above them.

Stage 3: almost the answer

If the calendar needs nine weekends, the plan is unscoped, not ambitious. Shrink the scope, not the sleep.

Worked solution (open after an honest attempt)

Worked solution. Example: theme neighborhood ordering, user office lunch crowd plus owner, features menu/prices, order form with echo, persistent list with delete. Out: payment, accounts, tracking, second language. Six ordered steps with checks, quota-behavior risk at position two, five dated evenings plus test evening. Backend tests three noes, quota counted inside free tier, README line 'No accounts, no server; orders persist in this browser on this device.' Plan fits; build approved.