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.
Review the personal brand site from the first module and make a simple list of where its main sections and button behavior are defined. Codex will inspect the file without editing it and separate what it found from what it is unsure about.
Before you start
Open my-brand-site with the finished index.html from module one.
Start a new task named Find the files behind the personal brand site so this result stays separate from earlier edits.
Do it now
Good prompt
Codex, inspect index.html in this local project without editing it. Tell me where the page structure, styles, About section, Projects section, and Projects button behavior are defined. For each answer, point to the exact element, style block, or event handler. Explain how I can check it myself. Separate what you found in the file from anything you are unsure about.
What success looks like
The response names index.html as the entry point and describes its HTML, CSS, and JavaScript roles.
No file is changed.
Observed facts and assumptions appear in separate lists.
Stuck? Try this
If Codex starts editing, stop it and reply: “This is a read-only task. Revert any edits and only explain what each part of the file does.”
If the answer is vague, ask: “Point to the exact element, style block, and event handler for each claim.”
Plain-language explanation
Before Codex edits anything, ask it to show you the main files and what each one controls. In this one-file site, it can point out the HTML structure, styles, and button behavior inside index.html.
This is useful when the project is new to you. You can see where a feature lives and check Codex's answer before deciding what to change.
Why it matters
Looking through the files first helps you avoid changing the wrong place. Codex can show what it found and clearly label anything it is not sure about.
Common beginner mistake
A common beginner mistake is asking for a change before finding out which file or part of the page controls it.
Try this
Ask Codex where one feature lives. Then find that part in the file and check the answer yourself.
Completion checklist
The response names where the requested behavior probably lives.
The response separates observed facts from assumptions.