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

Watch, then try

23|檢查隔離的 worktree(CLI 版・25 秒)

真實 CLI 輸出檢視器與本機網站錄影,非 Codex 原生介面;繁中字幕、無旁白,等待區段已剪接。檢查兩個事先建立、來自第一版基準的 worktree,依序操作,非平行 agent。

zero2codex
MP4

Step-by-step

  1. 沿用前一課的 my-brand-site,或從下方練習檔取用本課 before 起點。
  2. 在專案目錄執行本片 CLI 指令;本課權限為 read-only。
  3. 核對實際輸出與結束碼,不把文字回報當成瀏覽器操作證據。
  4. 列出兩個真實 worktree;此片依序查看,不宣稱平行 agent。
跟著本片操作:CLI 指令與練習檔(繁體中文)

這是本課的 CLI 替代實作路徑;下方概念課程仍保留其他介面的說明。先安裝並登入 Codex CLI,在 my-brand-site 資料夾內執行下列 macOS/Linux 指令。影片將真實 CLI JSON 事件排版成易讀畫面,下列指令使用一般 CLI 輸出;不是 Codex 原生介面,等待區段已剪接。

codex exec --ephemeral --ignore-user-config --sandbox read-only '執行 git worktree list,並唯讀檢查 .worktrees/copy/index.html 與 .worktrees/a11y/index.html,分別確認文案與連結目標。不要建立分支、不改檔。這是兩個已準備好的隔離 checkout,不代表有兩個 agent 同時執行。限 160 字。'

下載逐課練習檔與實際結果(ZIP)

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.

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