Learning Paths
Two learning paths

Pick where you are starting from

Two paths, four modules each, four one-hour sessions per module. Both end with something you can hand to someone else — not with a certificate.

32 sessions · 32 hours

0 of 32 hours done

Nothing is locked. Start anywhere, in any order.

Every session

Go straight to any hour. The map below shows how they fit together.

BeginnerClient-ready: promo material and a company profile

16 sessions · 16 hours

A1Understand the business first

0/4 · 4 hours

  1. 1Interviewing the ownerFilled-in interview notes
  2. 2One message for everythingOne positioning sentence that survives the test
  3. 3Gathering real materialA folder of verified material
  4. 4The one-page brand briefA brief pasted into a Project and used from here on

A2Visual promo material

0/4 · 4 hours

  1. 1The visual briefA brief for each piece
  2. 2Generating promo images, and the limitsThree candidate visuals
  3. 3Text on the imageThe final version, checked at phone size
  4. 4Assembling a week of contentA week's content package, ready to post

A3A company profile people can decide from

0/4 · 4 hours

  1. 1Which pages a small business actually needsA page map with the question each page answers
  2. 2Copy that does not read as AIFinal text for every page
  3. 3Building the site without codeThe site, built but not yet published
  4. 4Publishing, then four checksA live URL you can send

A4Turning it into work

0/4 · 4 hours

  1. 1Packages and pricingA price list you could send today
  2. 2From brief to handoverA project checklist
  3. 3Revisions without losing timeA written revision policy
  4. 4Image rights, and what you must not promiseA one-page scope and limits sheet

BuilderFrom pages to a working application

16 sessions · 16 hours

B1Specify before you build

0/4 · 4 hours

  1. 1A PRD that can be built fromA one-page PRD a model has already argued against
  2. 2Vibecoding and its one safety ruleYour own working rules, written down
  3. 3Reading a diff without knowing codeOne change accepted knowingly, one rejected
  4. 4Just enough GitHubA repository holding your project, with several commits

B2From a page to an application

0/4 · 4 hours

  1. 1Static or dynamic: when you really need a serverAn architecture decision you can justify
  2. 2Data: storing it, reading it, not losing itA form whose submissions actually survive
  3. 3Accounts and login without building themSigning in as two different users
  4. 4Deploying an application, not just a siteThe app live at a URL, used from a phone

B3Making it work without you

0/4 · 4 hours

  1. 1Agent, chatbot, workflow: the differenceThe right choice for your case, with a reason
  2. 2Connecting AI to your own dataAn answer you can trace back to a row
  3. 3End to end: webhooks, APIs, JSONOne flow that runs untouched
  4. 4Guardrails, approval, and testing before releasePasses five deliberately hostile inputs

B4Keeping it alive

0/4 · 4 hours

  1. 1The failures that only appear in productionLogs you can actually read when it breaks
  2. 2Cost: what is expensive, and whenA monthly estimate that holds up
  3. 3The security basics you cannot skipNo secret in the repository, access scoped
  4. 4Handing it over: documentation and ownershipSomeone else can run it from your notes

The shape of it

The same 32 sessions, seen whole. Click any one to open it.

The map needs a wider screen. The table above has everything it holds.

Progress is saved in this browser only.