People with different backgrounds turn work, writing, and projects into a personal website with Codex.
The first step is not understanding the tools. It is saying what you want people to see, inside one clean folder.

Copy This First

If you can open Codex inside an empty folder, start with this:

I want to build my first personal website, but I am not a programmer.

Please break the process into small steps I can follow.
Do not make me understand GitHub, Cloudflare, DNS, or build commands first.

For now, inspect the current folder and tell me whether it is safe to start here.
If it is safe, give me the smallest first plan.
If it is not safe, tell me which empty folder I should use instead.

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

Please keep warning me about anything that should not be public.

This prompt does not require web vocabulary. It makes Codex the guide before the tools become the problem.

You Do Not Need The Full Map First

A normal person can see Cloudflare, GitHub, terminal, deployment, and DNS and feel that they need a whole course before touching anything.

They do not.

This series assumes:

  • Codex checks the project, creates files, explains the next step, and runs necessary checks;
  • you confirm the goal, choose accounts, sign in, authorize, and read the page yourself;
  • technical terms appear only when a real page makes them useful;
  • you do not have to guess which website to open next.

You need basic computer skills, copy and paste, the ability to read a page, and the judgment to keep private material out.

Version One Only Answers Four Questions

Do not start by imagining a large company website.

The first version only needs to answer:

  1. Who am I?
  2. What am I focused on now?
  3. What public work, writing, or projects can people see?
  4. How can someone contact me?

If it answers those questions, it is already a real personal website. It can be plain. It can use placeholders at first. It should not be chaotic, and it should not contain private material.

Different People Can Start Differently

If you are a designer or artist, version one can be a small portfolio: a few works, your direction, and a contact path.

If you are a teacher or consultant, it can be a resource page: what you help with, what you have written, and how people can reach you.

If you are an engineer or technical person, it can be projects and notes: what you built, what you learned, and tutorials worth keeping.

If you are a parent, it can be a reviewed family learning record: only public-safe material, no school names, home address, schedules, or children’s faces unless you are certain.

If you simply want a long-term homepage, keep it even smaller: a short intro, a few articles, and public links.

None of these starts with choosing a stack. You describe who it is for, then let Codex make the first version.

How To Walk Through The Series

The “Complete Route” block on the side shows every step in this series. On a phone, it usually moves below the article.

Do not read everything in one sitting. Finish one visible result at a time:

  • first stage: start Codex in an empty folder and open a local preview;
  • second stage: publish a free URL before buying a domain;
  • third stage: decide whether a custom domain helps, then learn small updates;
  • final check: review privacy, images, links, and mobile readability before publishing.

If you get stuck, do not guess. Paste the page, error, or message back to Codex and ask for the next sentence to copy.

Codex Guides; You Decide

Codex can handle repetitive work:

  • creating files;
  • writing pages;
  • keeping styles consistent;
  • opening local previews;
  • naming the next page you need to confirm;
  • checking links, builds, and privacy risks.

But only you can decide:

  • which experiences should be public;
  • which photos are safe to publish;
  • which contact path you want to keep using;
  • whether the site sounds like you.

The website represents you, not Codex. This series is not about handing everything over. It is about turning unfamiliar tools into small confirmations.

Done With This Introduction

You do not need to memorize any technical word.

This introduction has done its job if:

  • you know the first move is starting Codex inside one clean folder;
  • you can copy the first prompt above;
  • you know version one only needs a home page, about page, list page, and contact page.

Start here: Step 1: Start Codex in an empty folder.

References