zero2codex
OpenAI Codex workflow course

Course goal: ship your personal brand site

Build a personal brand site with Codex

Keep improving one project from an empty folder to a responsive one-page site with an introduction, projects, and contact details. Every lesson adds a visible result or a check toward that finish line.

Curriculum

Personal brand site build path

01

Start With Codex

Set up Codex and build the hero section of your personal brand site.

0/4
00｜Install And Open CodexInstall the desktop app, sign in, open the site project folder, and send a safe first message.What Codex Is ForBuild the first version of your site with a name, introduction, projects, contact details, and one working button.Choose A Codex SurfaceEdit the site's Projects button locally, then verify its text and behavior in a browser.Your First Useful PromptTurn “add an About section” into a concrete request with content, constraints, and browser checks.
08

Finish And Deliver The Site

Polish independent tasks in parallel, then complete one final acceptance review.

0/3
Complete The Site GoalTurn the finished personal site into one measurable goal with content, layout, interaction, and evidence checks.Polish Copy And Accessibility In ParallelUse isolated worktrees only when copy polish and accessibility review can avoid editing the same lines.
10 minReady

Polish Copy And Accessibility In Parallel

Speed up final polish without mixing changes or creating a hard merge in the one-file site.

isolated reviewfile overlapclean merge

Plain-language explanation

Final copy review and accessibility review can happen in parallel, but your site lives mostly in one file. If both tasks edit index.html, parallel work may create more merging than it saves.

A safer pattern is to let each worktree report findings first, then apply overlapping fixes once in the main task.

Why it matters

You get independent reviews without blindly merging two versions of the same page.

Common beginner mistake

Beginners sometimes assume parallel always means faster, even when both tasks need to rewrite the same lines.

Step-by-step

  1. Give one worktree a copy-only review.
  2. Give another worktree an accessibility-only review.
  3. Keep both findings-only when their edits would overlap.
  4. Apply and verify the accepted fixes in one place.

Good prompt

Codex, use one worktree to suggest copy improvements and another to report accessibility issues in my-brand-site/index.html. Record each branch, path, and evidence. If both would edit the same lines, keep them findings-only and let the main task apply accepted fixes once.

Try this

Mark whether copy and accessibility work would touch the same line before choosing parallel edits.

Completion checklist

  • Each worktree has one review scope and a clear evidence report.
  • Overlapping index.html changes are applied and verified once.

Sources

Run The Final Three ReviewsRun separate content, link, and accessibility reviews, then compare all evidence against the same launch checklist.

Practice lab

Copyable Codex prompts

Plan before coding

Codex, inspect the relevant files first, then propose a plan. Do not edit until the plan names tests and verification steps.

Verification checklist

  • Relevant files are named before edits begin.
  • The plan includes tests and verification commands.

Verify a UI change

Codex, start the dev server, open the route in the browser, check desktop and mobile layouts, then report the exact evidence.

Verification checklist

  • Desktop and mobile states are checked in the browser.
  • The final note includes exact evidence.

Review focused risk

Codex, review the uncommitted diff. Focus on behavioral regressions, missing tests, and accessibility issues. Do not modify files.

Verification checklist

  • Findings lead with severity and file references.
  • Unchanged files are left untouched.
Every good Codex request says what to change, what to preserve, and how to prove it worked.

Reference

Codex concepts to keep nearby