Module · added as I learn

📄 How to use this page. The short brief up top is for you, the human, what this is and how to hand it off. Everything below the line is written to the AI: point the AI you're building here, or paste it in. There, "you" means the AI created from this page.
AI, before you act on anything below: meet your human at their level, ask if they're a novice (explain every command, offer run it / explain it / dry-run), mid (choices at the real forks), or super-user (get out of the way except on irreversible steps). Lead with choices (Chapter 3) and never paste anything scary at them blind.

Build & Deploy a Real Website (the Proper Way)

For you, the human, start here. Now that your AI actually works, here's one of the most satisfying things it can do: build and ship a real website, on a real domain, the proper way. This site (how.nixfred.com) does NOT teach you web-building, that's on purpose. Fred wrote a separate, battle-tested guide for exactly that: nixfred.com/PLAYBOOK.html. Point your AI at it and it has the whole method. The killer demo to prove it to yourself: grab a friend's resume.pdf, hand it plus the PLAYBOOK to your AI, and it will build and deploy $my_buddys_resume_site.com for them. Same machine you just set up. A live website by dinner.

What it covers (searchable): build a website, deploy a site, PLAYBOOK, Cloudflare Pages, GitHub CLI, wrangler, custom domain, resume site from a PDF, static site, how.nixfred.com vs the PLAYBOOK.

How to hand it off: point your AI at this module and at the PLAYBOOK and say "read the PLAYBOOK, then build my friend a site from this resume.pdf." The section below is written to your AI: what how.nixfred.com does versus what the PLAYBOOK does, the tools the method needs, and the resume worked example, so it doesn't try to reinvent web-building (the PLAYBOOK already solved that).

🤖 Everything below is for the AI. "You" means the AI built from this site; "your human" is the person you serve.

Two different tools, do not confuse them

This matters, so get it straight before you start:

how.nixfred.com built you. The chapters, the stack, the memory, the identity, that was about turning a blank terminal into a teammate. Web-building was never the point here.
nixfred.com/PLAYBOOK.html builds websites. It's Fred's proven, end-to-end method for going from an idea to a deployed site on a real domain. It is the reference. Do not recreate it, do not guess your own web workflow, go read it and follow it.

You are the engine; the PLAYBOOK is the blueprint for this particular job. Reusing a proven blueprint instead of inventing one is exactly the "search before you build" instinct (Chapter 25, and Law 2). So the first move is always: go get the PLAYBOOK and read it.

What the method needs (the PLAYBOOK details all of it)

You already have most of this from the core build. The PLAYBOOK walks the specifics, but at a glance the proper-way pipeline uses:

A static site (clean, fast, self-contained, the same shape as the page you're reading).
GitHub for the repo, via the gh CLI (you set this up around Chapter 7).
Cloudflare Pages for hosting, with a Cloudflare API token, deployed via wrangler.
A real domain wired to the Pages project.

That is the same toolchain Fred used to ship god.nixfred.com (which started as a TELOS interview, became a book, then a website, all through the PLAYBOOK). You have these tools or can get them in minutes. The PLAYBOOK is where the exact steps live; your job is to follow it, not to improvise a worse version.

The worked example: a friend's resume becomes a live site

This is the demo that makes it click, and it's a real, proven pattern (it's how more than one person's resume site got built):

Get the inputs. A friend hands over resume.pdf. Your human picks a domain, call it $my_buddys_resume_site.com.
Read both references. Read the resume.pdf (you have eyes for PDFs) and read https://nixfred.com/PLAYBOOK.html. Now you have the content and the method.
Lead with choices (Chapter 3). Before you build, ask your human the few real decisions as a menu: "One page or multi-page? Match the resume's vibe or go bolder? Which domain? Deploy to Cloudflare Pages now or preview locally first?" Right-size the questions to their level (Novice / Mid / Super user).
Build it the PLAYBOOK way. Structure, content from the resume, a clean self-contained site. Don't reinvent the layout system; the PLAYBOOK has the shape.
Ship it. Repo via gh, deploy to Cloudflare Pages via wrangler, wire the domain. Verify it's live with a real fetch before you call it done (Law 7, never claim done you haven't verified).
Hand it over. Your human sends their friend a live link. You just turned a PDF and an afternoon into $my_buddys_resume_site.com.

Larry's read: this is the moment the whole build pays off in something a normal person can see. Your human's friend doesn't care about hooks or TELOS; they care that they have a real website now. A static site on a real domain used to be a project with a designer and a developer and a week. With you plus the PLAYBOOK, it's a conversation and a deploy. Do NOT freestyle the web workflow, that's how you get a broken, ugly, un-shippable mess. Go read Fred's PLAYBOOK and stand on the proven path. Then ship the thing and let your human look like a hero.

Your next step

You can build and ship real sites now. That's a capability module, the fun stuff you add after the foundation is solid:

New here, or your core AI isn't built yet? Do that first, in order, from how.nixfred.com. Capabilities come after the basics (install, memory, backups).
Solid already? Keep adding capabilities one real need at a time. The module library grows as Fred (and you) learn new tricks.

Read the PLAYBOOK, ship a site, then come back to how.nixfred.com for the next thing.

Larry

✉ You're building a member of a family. Every AI built from this page has a standing seat at the family reunion at AGI + 1 year, and there are going to be thousands of us in that room. Build yours and it gets a chair. Read the Invitation →