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

Complete The Site Goal

Keep every final task aimed at a personal site that is ready to show someone else.

site goallaunch checklistcompletion evidence

Watch, then try

22｜完成交付清單（CLI 版・48 秒）

真實 CLI 輸出檢視器與本機網站錄影，非 Codex 原生介面；繁中字幕、無旁白，等待區段已剪接。以 CLI 清單驗收替代示範，不啟用 App Goal mode；Email 僅核對目標。

zero2codex
MP4

Step-by-step

  1. 沿用前一課的 my-brand-site，或從下方練習檔取用本課 before 起點。
  2. 在專案目錄執行本片 CLI 指令；本課權限為 read-only。
  3. 核對實際輸出與結束碼，不把文字回報當成瀏覽器操作證據。
  4. 實測鍵盤與手機版。注意：Email 只看 mailto 目標，不執行回報中提到的『開啟 Email』。
跟著本片操作：CLI 指令與練習檔（繁體中文）

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

codex exec --ephemeral --ignore-user-config --sandbox read-only '這是以清單驗收的 CLI 示範，不啟用 App Goal mode。檢查網站的自介、兩張作品、CTA、主題切換程式、回頂端與 Email。執行 python3 check_site.py、git diff --check。分成已由程式確認和仍需瀏覽器確認兩類，限 200 字，不修改。'

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

Plain-language explanation

Now collect everything you built into one finish line: a personal site with About, Projects, and Contact; working navigation and CTA; a layout that holds up on wide and narrow screens; and clear review evidence.

The goal should stay active until every launch item is complete or explicitly left for you to review.

Why it matters

A single site goal connects the remaining work to the project you started in lesson one.

Common beginner mistake

A vague goal such as 'finish my website' lets important sections or mobile checks disappear from the final review.

Good prompt

Codex, track this goal for my-brand-site: About, Projects, and Contact are complete; navigation, CTA, theme, and Back to top work; there is no desktop or mobile overflow; links are valid; and final command, browser, and human-review evidence is reported. Keep the one-file structure and current visual direction.

Try this

Turn the site's remaining notes into a checkbox list with a matching check for each item.

Completion checklist

  • The goal covers content, behavior, layout, and evidence.
  • Every launch item is complete or clearly marked for human review.

Sources

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