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

Polish The Site In The App

Complete one visible site refinement from edit through browser review in the same workspace.

project contextdiff reviewresponsive check

Watch, then try

16｜用 CLI 完成聚焦微調（CLI 版・25 秒）

真實 CLI 輸出檢視器與本機網站錄影，非 Codex 原生介面；繁中字幕、無旁白，等待區段已剪接。原 App 微調練習改以 CLI 完成，不示範 App 按鈕。

zero2codex
MP4

Step-by-step

  1. 沿用前一課的 my-brand-site，或從下方練習檔取用本課 before 起點。
  2. 在專案目錄執行本片 CLI 指令；本課權限為 workspace-write。
  3. 核對實際輸出與結束碼，不把文字回報當成瀏覽器操作證據。
  4. 刷新網站，對照第二張卡片；這次不示範 App 按鈕。
跟著本片操作：CLI 指令與練習檔（繁體中文）

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

codex exec --ephemeral --ignore-user-config --sandbox workspace-write '這是原 App 課程的 CLI 替代示範。只改 index.html 第二張作品卡的說明為『把資訊整理成清楚的介面，讓使用者更快完成任務。』。不要動第一張、主題或聯絡方式。執行 python3 check_site.py、git diff --check，簡短回報。'

下載逐課練習檔與實際結果（ZIP）

Plain-language explanation

Use the Codex app to finish one visible detail of the site from start to finish. A Projects card is a good example because you can edit its copy, inspect the diff, and immediately check the layout.

This lesson is not about learning every app feature. It is about completing one real site improvement without losing track of the evidence.

Why it matters

Keeping files, diff, terminal output, and browser checks together makes final polish easier to review.

Common beginner mistake

A common mistake is accepting a nicer-looking card without checking what else changed or how it wraps on a narrow screen.

Good prompt

Codex, in the app, improve the second Projects card in my-brand-site so its title and description clearly explain what I made. Keep the current visual style and one-file structure. Then show the focused diff and check the card at wide and narrow browser widths.

Try this

Rewrite one project description, inspect the diff, and resize the page before accepting it.

Completion checklist

  • Only the intended card and necessary styles changed.
  • The card remains readable at wide and narrow widths.

Sources

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