Inspired by OpenAI's new Codex Sites feature, a practical Sunday episode argues that the website — not the doc, deck, or PDF — is becoming the knowledge worker's anchor artifact: a dozen problems that files have and sites solve, then an 18-item checklist of things you should be building as URLs instead of attachments.
The website is the new unit of knowledge work output.
For decades, knowledge workers packaged thinking into docs, decks, spreadsheets, and PDFs — not because those formats carried knowledge best, but because making anything more interactive cost too much in money or other people's time. AI has changed that cost structure entirely, and tools like Codex's new Sites make publishing native. A file is a snapshot with constraints; a site is a canonical, navigable, interactive, measurable home for your thinking. Many of the artifacts in the knowledge worker's kit are simply better as websites now.
Tuesday's Codex updates included Sites: a simplified way to publish what you build with Codex as a website or web app your team, friends, or colleagues can interact with. No more wiring Vercel and Supabase together, and no detour through an all-in-one vibe-coding tool like Replit or Lovable — the all-in-one experience is now native to Codex.
The old menu of formats — docs, decks, spreadsheets, PDFs — wasn't chosen because it carried knowledge best; turning thinking into something interactive and updatable used to cost too much. AI changed that cost structure entirely: any semi-capable person can now generate a useful, fairly good-looking website as easily as they used to throw together a deck.
Every downloadable file is a snapshot of a moment in time, and the clock starts running the second you hit send. A site you control gives knowledge a canonical home — whoever lands on the URL gets the current version — solving a problem so big that DocSend and the collaboration suites were built to patch it for specific formats.
Files create friction at every hop: format compatibility, download bandwidth, one more thing for the recipient to organize or trash, and the whole process again if they pass it on. A link moves through email, Slack, a text, a CRM, a calendar invite, or a newsletter — and works the same on a laptop or a phone.
Every downloadable format forces its structure on every reader, but knowledge work isn't consumed by one generic reader in one linear sitting. A site can organize the same material by topic, role, urgency, or depth: the exec reads the summary, the analyst jumps straight to the evidence, someone else searches the glossary.
A well-designed site produces signal — what got read, clicked, searched, shared, revisited, abandoned — so the artifact itself becomes improvable. In sales, training, fundraising, internal comms, and change management, knowing where the message actually landed is essential to whatever comes next.
Cloudflare reported this week that agent and bot browsing accounted for more web use than human browsing for the first time ever. In a paradigm where knowledge work artifacts have to interact with agents, the old messy pile of PDFs, docs, CSVs, and PowerPoints starts to look brittle next to HTML designed for machine consumption.
AI-native presentation tools like Gamma are already collapsing the space between a deck and a website — a mega trend that will only continue. Native sites add what PDF-distribution SaaS merely approximates: interactive features, links out to context, and freedom from the 16:9 aspect ratio. Start by asking whether your decks should just be sites by default.
A memo arguing for something has to carry the context, the problem, the argument, the objections, the evidence, and the action — all linearly, in a PDF. A strategy site layers that material so different audiences can quickly hone in on the parts that matter to them.
Take one big dense thing and reorganize it as something layered and navigable, with links out to relevant sources and context — making the important information inside accessible to a much wider variety of readers.
Formulas and tab design hide or half-hide information from everyone but the author. A data site turns the same numbers into a guided view — dashboards, filters, summaries, charts — which matters most when the spreadsheet's real goal is getting people to the conclusion you're suggesting.
Already showing up in the wild: instead of a static document, a microsite carries interactive elements — toggle variables and watch the price or expected ROI change — and its observability shows you how prospects actually engaged, in a way a PDF just can't.
The failure mode is recurring updates strewn across email, docs, decks, and one-off links. A client portal gives them a single place for current status, milestones, deliverables, and open questions, perfectly queued up for that project.
A project homepage keeps a canonical source for the changing goals, stakeholders, and decisions of a project over time. Not always needed if the brief kicks off work inside existing project-management software — but far more dynamic than a brief for teams without one or that want something bespoke.
A case-study PDF compresses a rich story into a couple of paragraphs and a logo — often squeezing out the most convincing parts. An interactive case page makes room for the full problem, process, and metrics, plus rich media like video. Anyone selling anything will increasingly do this with their decks and case studies — "I am quite sure."
The most interesting archetype: the website doesn't just present the artifact better, it changes what the artifact is — from a one-time document into a living, evolving resource. The mature version: an Openclaw-style agent continuously researching the key information and updating the hub at regular intervals.
AIDB's own programs — Agent OS, Claw Camp, the New Year program — each run on a platform purpose-built for that training experience, despite being offered for free, because the cost of a bespoke learning management system has cratered to the time it takes to interact with your build tool.
The PDF handbook is something almost no one touches unless they absolutely have to. A living handbook site, always updated with the latest policies, turns dead reference material into a genuinely valuable resource — without the versioning problems even a regularly updated PDF carries.
Board materials tend to become massive all-in-one PDFs, or folders full of them. A board portal preserves context and makes all the background available without forcing directors to wade through it to get to what really matters.
Depending on how transparent you want to be, investors get the most up-to-date metrics — potentially real-time, depending on your APIs — instead of an every-once-in-a-while update. And when an investor needs something for their LP board off-cycle, you have one easy link to point them to.
A full candidate site gives you a much bigger tapestry to explain the role, give background, and help candidates figure out whether they're the right fit — and how to tell you so. Overall, an incomparably better experience.
If you're constantly digging the brand PDF out of a folder of assets, a brand system site organizes everything current and up-to-date at a single URL. Same move for press: the media kit becomes a press site with everything a journalist might need behind one easy link.
A huge part of the vibe-coding boom is simply knowledge workers figuring out that websites are better ways to share information than the traditional artifacts they used to use. With platforms like Codex now embedding features like Sites natively, that's going to do nothing but expand.