Xu Bian

Posted on May 3 • Originally published at marlinbian-site.pages.dev

Build your own independent site with Codex

#webdev #tutorial #beginners #productivity

The Short Version

You do not need to become a programmer before you can have your own place on the web. You need to make three decisions first:

What should last: artwork, essays, projects, learning notes, tutorials, or a family archive.
How often you will update it: weekly, monthly, or only when a real project is ready.
How much maintenance you can accept: no-code, light file editing, or a long-term code project.

Codex sits between light file editing and a long-term code project. It is not a magic website button. It is a local collaborator that can inspect a project, edit files, run checks, and explain the changes. The official OpenAI Codex CLI documentation describes it as a coding agent you can run locally from the terminal, working inside the selected directory.

That makes it useful for the repetitive parts: setting up folders, creating pages, adjusting styles, turning Markdown into pages, running builds, and checking that private material has not entered the public site.

A Website Is Not Just Another Feed

Social platforms are useful. They are where distribution, feedback, and discovery happen. But they are not good archives. Rules change, timelines bury work, and links can become fragile.

An independent site solves a different problem: it gives your public work a stable address.

A healthier publishing order looks like this:

Publish the complete version on your site first.
Then adapt it for Xiaohongshu, WeChat, YouTube, Bluesky, DEV.to, or other platforms.

This keeps the source version in your hands. You can still benefit from social platforms without letting them become the only copy of your work.

Choose By Person, Not By Tool

Designers And Artists

Start with a portfolio. Do not start with a complex blog system.

Your strongest assets are images, project process, taste, and judgment. A first version can be very small:

Home: one clear sentence about who you are, plus selected work.
Work pages: one page per project, with images, context, process, and outcome.
About: what you do, what kind of collaboration fits, and how to contact you.

For a designer, Codex should not decide which work is good. Its job is to make the structure steady: create pages, keep image sizing consistent, add alt text, update navigation, and run checks.

Engineers And STEM Builders

Start with project records and reusable notes.

It is easy to over-engineer your own site. The better first version is practical:

Project pages: what you built, why it exists, what stack you used, and what happened.
Tutorials: reusable explanations for things you keep teaching.
Playgrounds: small demos or tools people can try without an account.

If you are comfortable with Git, Markdown, Astro, and static hosting, Codex can be very effective. It can work inside the repository and run the build. Your job is to review the changes and keep the important decisions explicit.

Children And Family Projects

Start with safety, simplicity, and adult review.

A child's site should not begin with public attention. A better goal is a safe record:

A small wall of work: drawings, crafts, Scratch projects, or reading notes.
A learning log: one or two sentences each week.
A review flow: drafts stay local until an adult checks them.

Privacy matters more than polish. Do not publish school names, home locations, routine schedules, identity documents, or anything that makes the child easy to identify. Codex can help scan text, but an adult must make the final decision.

Writers, Teachers, And Small Service Businesses

Start with articles and useful resources.

Writers need durable long-form links. Teachers need organized materials. Small service businesses need a clear public introduction. A first version can be:

Home: what value you provide.
Writing or resources: public material grouped by topic.
Contact: one low-friction way to reach you.

You do not need a complex system at the beginning. Let the work have stable URLs first. Add newsletters, courses, payments, membership, or automation only when the content proves the need.

The Steady Route

If you do not know what to choose, I would start here:

Write content in Markdown or MDX.
Build the site with Astro.
Keep history in Git.
Deploy to Cloudflare Pages, GitHub Pages, Netlify, or Vercel.
Treat social platforms as distribution, not the archive.

This route is not the only good route. Its advantage is durability. Your content remains ordinary files. If you change themes, hosting providers, or domains, the articles and images are still yours.

No-code tools are also valid. Framer, Webflow, Carrd, Notion-style sites, and similar tools can be faster for a single polished homepage. The deciding question is simple: if you need one beautiful page, no-code may be faster. If you want years of essays, tutorials, projects, and interactive demos, a file-based site is usually steadier.

A Better First Prompt For Codex

This prompt is too vague:

Build me a personal website.

A better starting prompt is:

Please help me build a personal independent site in the current directory.
The audience is not programmers only. People should understand me through work and writing.
The first version needs a home page, about page, writing list, project list, and contact page.
Store content in Markdown or MDX. Public content should not depend on a database.
Inspect the project structure first, give me a short plan, and wait before editing files.

If you already have materials, add a privacy boundary:

The materials/inbox folder contains images and drafts.
First list what is suitable for public use and what may be private.
Do not move anything from private into public or src/content.

A good prompt does not lock every technical detail. It states the goal, audience, boundaries, and acceptance checks.

Keep Version One Small

The first version only needs five areas:

Home: one clear positioning sentence and recent work.
About: who you are and what you are focused on now.
Writing: articles and durable opinions.
Projects: work, experiments, and tools.
Contact: email, social links, and collaboration paths.

Avoid login, comments, CMS complexity, memberships, heavy animation, and multilingual admin systems at the beginning. Add them only after you have a real publishing rhythm.

Launch Checklist

Check at least these items before publishing:

Every page is readable on a phone.
The home page explains who you are within ten seconds.
Each article has a title, description, date, and tags.
Images have reasonable dimensions and alt text.
Secrets, private drafts, backend screenshots, and child-sensitive details are not in public folders.
The build command passes.
Important links open correctly.

This is where Codex helps: run the build, inspect diffs, and list risks. Still, read the public pages yourself before shipping.