The First Step Should Be Light

A beginner should not start by designing a folder system.

The realistic first step is:

Create one empty folder.
Start Codex inside that folder.
Describe the website you want.
Let Codex do the first setup.

That is the path I recommend. You do not need to create folders like materials, public-candidates, or private-do-not-publish before Codex starts. Those are useful for long-term project maintenance, but they should not become the entry fee for a beginner.

Prepare One Empty Folder

Create a folder on your Desktop, in Documents, or anywhere you can find easily.

A simple name is:

my-personal-site

Then open that folder and start Codex CLI:

codex

If you use the Codex app or IDE extension, the idea is the same: choose this empty folder as the project directory.

The key is not the command itself. The key is giving Codex a clean working area. Do not start by pointing it at your Downloads folder, full Desktop, family photo library, contracts, bills, or other private materials.

Do Not Move All Your Materials First

For the first attempt, do not drag in a large set of photos, drafts, documents, screenshots, or chat records.

First let Codex create a website with placeholder content. After the structure exists, replace the placeholders with real material one by one.

If you already have material that is clearly public, keep it small:

  • a public bio draft;
  • one or two images you are certain can be public;
  • up to three work, article, or project titles;
  • one contact method you are willing to publish.

If you are unsure whether something can be public, do not put it in the project folder yet. On day one, a clean boundary matters more than having a lot of content.

Use This As The First Prompt

Inside Codex, type:

Please build a minimal personal website in this empty folder.

I am not a programmer, so do not ask me to design the folder structure first, and do not start with too many technical terms.
You choose the first directory structure, technical approach, and page files, but explain each step in ordinary language.

Version one only needs:
- home page
- about page
- work or writing list
- contact page

The site should help a first-time visitor understand:
- who I am
- what I am focused on now
- a few public works, articles, or projects
- how to contact me

Constraints:
- do not read files outside the current directory
- do not include identity documents, addresses, children's schools, client files, contracts, backend screenshots, or private information
- if real content is missing, use clear placeholder text
- do not add login, comments, membership, payments, or complex animation

First explain your plan in 3 to 5 sentences, then create the first version.
When done, run the necessary checks and tell me how to open the local preview.

The point is that you do not need to tell Codex which framework to use, which folders to create, or what every file should be named. That is work Codex can take on first.

You only need to define the goal, audience, page scope, and privacy boundary.

If Codex Asks About Technology

Sometimes Codex may ask:

Do you want Astro, Next.js, Vite, or plain HTML?

You do not need to choose by yourself. Reply:

Please choose what fits a first personal website for a beginner.
Use these standards: simple, static, easy to preview, and easy to publish later on a free hosting platform.
If you must use a technical word, explain it in one sentence first.

For a first website, the priority is not picking the perfect stack. The priority is seeing a page that opens, reads clearly, and can be improved.

Done Means This

This step is complete when:

  • an empty folder has become a website project;
  • Codex created the necessary files;
  • Codex told you how to preview it locally;
  • you roughly know where the home, about, list, and contact pages are;
  • the project does not contain private material you did not mean to publish.

If Codex gives you too much technical language, say:

Please rewrite that explanation for a non-programmer.
Do not explain the history of the tools. Only tell me where to look, what to click, and what to do next.

The next step is opening the local preview: Step 2: Ask Codex for a first version you can open.