Private drafts, public artifacts
A note on separating raw material from publishable work when Codex is part of the workflow.
codex
11 public items tagged codex.
Codex workbench
A local-first workflow for turning project folders, notes, scripts, and code into durable outcomes.
Step 1: Start Codex in an empty folder
The first step should not be folder design. Create one empty folder, start Codex there, and let Codex choose the first project structure.
Step 2: Open the first version Codex made
After Codex creates the first personal website in an empty folder, focus on the local preview, clear pages, and privacy risks.
Step 3: Publish a free public URL first
After the local site works, let Codex guide the GitHub and Cloudflare Pages authorization flow with copy-paste prompts instead of manual upload.
Step 4: Add a custom domain only when it helps
After the free URL works, ask Codex whether a custom domain is worth buying. You confirm accounts, domain choices, and page states; you do not need to learn DNS first.
Step 5: Keep editing the site after it is online
After launch, change one thing at a time: ask Codex for a plan, preview locally, check, and publish with the workflow this project actually uses.
Step 6: Check privacy and common mistakes before publishing
Once your personal site can be published and updated, copy one fixed pre-publish prompt so Codex checks privacy, images, links, and phone readability before every release.
Your first personal website with Codex, without fearing the tools
A plain-language entry point for people who use phones and computers but do not yet know hosting, GitHub, or DNS: start from one clean folder and let Codex guide the route.
Build your own independent site with Codex
A beginner-friendly guide for creators, families, engineers, and non-programmers who want a durable home on the web.
How much does a personal independent site really cost?
A practical cost breakdown for Codex, domains, static hosting, storage, email, and the upgrades that may come later.