Most complex websites don’t have a content problem. They have an arrival problem. I built TobyGod...Most complex websites don’t have a content problem. They have an arrival problem. I built TobyGod...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Most complex websites don’t have a content problem. They have an arrival problem.
I built TobyGodden.com/help because my work is spread across browser instruments, film, live video, music, writing and AI systems. A project grid left the visitor to make sense of all that alone.
The guide begins somewhere else: why are you here?
Commissioning, researching, listening, reading, collaborating—or simply curious. It works from a small, approved corpus, asks one useful question, then points to one place rather than ten.
There’s no vector database and no chatbot pretending to know everything. It’s plain JavaScript, PHP, Claude, a 25KB curated corpus and deterministic fallback routing when the model fails.
The interesting part isn’t really the AI. It’s deciding what the system is allowed to know, what it must never claim, and what counts as a useful next step.
I think more portfolios, archives and cultural websites need a conversational front door—not more navigation.
Nucleus Institute is the platform that takes your AI idea and ships it. We scope the product, generate the architecture, build the intelligence layer, and hand you the production system plus the content engine that grows it, with a trained team that can keep building. One workspace. One shipped product.
https://nucleusinstitute.com/introduction
We rebuilt TechFoundry's website in a week. The brief that mattered most wasn't "make it look good". It was "make ChatGPT and Gemini able to find us".
Buyers ask an AI before they search now. So all 110 pages (26 pages, 80 Aerless™ hardware parts, 4 articles) are server-rendered with real content and structured data a model can cite: Product schema with SKU and MPN on every part, BlogPosting on articles, CreativeWork on case studies, and a robots.txt that lets AI crawlers in.
Three other decisions I'd make again.
1) One hand-coded WordPress theme, three "surfaces": corporate hub, /ai, /aerless. Each gets its own nav, palette and CTAs; the same codebase decides which company you're looking at. No page builder, no front-end framework. Homepage Lighthouse: 98 / 100 / 100 / 100.
2) Leads go where the team already is. Every form posts straight into a Microsoft Teams channel and creates a record in a lightweight CRM I built inside WordPress. Nothing lives only in an inbox.
3) Claude Code and ChatGPT alongside hand-written PHP and JS. That's how one person ships 110 pages in seven days.
What I'd fix on day one next time: reserve space for the animated heroes so mobile doesn't shift layout, and ship an llms.txt next to the sitemap.
If you're rebuilding a site this year: are you designing for AI search yet, or still just Google?