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.
06

Finish The Site Details

Use the app, CLI, or cloud where each remaining site task fits best.

0/3
Polish The Site In The AppUse the Codex app to polish one Projects card, review the diff, and check the result at two widths.Run Site Checks In The CLIUse the terminal to catch duplicate IDs, missing section links, and whitespace errors in the single-file site.Delegate An Isolated Site TaskHand off a bounded content or accessibility audit without opening the door to a full redesign.
11 minReady

Delegate An Isolated Site Task

Write a site handoff that another Codex task can finish and you can review later.

isolated auditfile scopereview evidence

Plain-language explanation

You can delegate one narrow site review without handing off the whole design. A read-only accessibility audit is a good fit because the file, questions, and expected report are clear.

The task should return exact findings. It should not quietly redesign the page or add packages.

Why it matters

A bounded handoff gives you a second look at the site while keeping the final decision in your hands.

Common beginner mistake

A vague request such as “make my site accessible” can expand into a large, hard-to-review rewrite.

Step-by-step

  1. Name my-brand-site/index.html as the only file to inspect.
  2. Make the audit read-only on its first pass.
  3. Forbid redesigns, new packages, and unrelated edits.
  4. Require exact elements, impact, and suggested fixes in the report.

Good prompt

Codex, run a read-only accessibility audit of my-brand-site/index.html. Do not redesign, edit files, or add packages. Report each issue with the exact element, why it matters, and a focused fix I can review later.

Try this

Write a handoff for either a content audit or an accessibility audit, but not both at once.

Completion checklist

  • The handoff names one file, one audit goal, and clear limits.
  • The report can be checked from exact findings instead of trust.

Sources

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.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