Every page, designed then built
A signed-off vocabulary, templates that build themselves from tags, and a Voice Kit, so every draft already sounds like you.
An add-on I developed after hearing the same need from client after client: a connected content system that links every service, project, answer and video to the ideas behind it, so people, Google and AI assistants can follow what you know. Built natively for the Webflow CMS, portable to any platform, with a Voice Kit that drafts in your voice and publishes nothing you haven't approved.
The same questions kept coming up on client calls. Why don't we show up when people ask ChatGPT? Why does our blog go nowhere? Who has time to write it, and won't AI make us sound like everyone else? The Knowledge System is my answer: it turns a site that lists what you do into one that explains how it all connects, so every new article makes the rest of the site stronger, in your voice.
A shared vocabulary as a Topics collection, multi-reference tags on every content type, templates that assemble their own related sections, JSON-LD generated from the same fields, video fields with parsed chapters, and an AI drafting pipeline with a human approval gate. Native Webflow CMS first; the same model maps to any CMS.
Open a system to see what it does, why it matters and, in Engineer mode, how it works.
30 to 60 words in six categories name what you do: who you help, your services, how it works, what you watch for, the ideas behind the work, and what you're known for. Every page points to the same words.
One Topics collection with a Category option and a self-referencing Related Topics field. Every other collection gets a Related Topics [[multi-reference]], so the vocabulary is the spine everything hangs on.
Switch Crew level to Engineer for the technical breakdown.
Tag an article, project or service with a few terms and its related sections, topic pages and hub fill themselves. Nothing is linked by hand.
Template Collection Lists filtered by "Related Topics contains the current item" build the reverse links natively in the [[CMS]]: no script and no plugin to maintain.
Switch Crew level to Engineer for the technical breakdown.
The blog becomes a library of answers, organized by theme instead of date, and every article opens with the short answer.
An Insights collection with a Primary Theme option, filtered on the page by [[Finsweet]] CMS Filter (deep-linkable with ?theme=). Cards carry no dates; the publish date lives only in the schema.
Switch Crew level to Engineer for the technical breakdown.
A 10 to 15 minute kit captures how you write and talk. AI works as a partner, drafting from it, and you edit and approve every piece before it goes live.
The kit bundles a writing sample, a voice memo and a few preferences into one file that stays on the client's computer until they send it. It becomes a voice profile every draft is checked against. Drafts land in the CMS as drafts; only the client's approval publishes.
Switch Crew level to Engineer for the technical breakdown.
Paste a video link and a few chapter lines. The page leads with the film, adds chapter jumps and keeps the written version right below it.
Video URL, Duration and Chapters fields (one "0:00 | Title" per line). A small init-guarded script turns the lines into chips that seek the player; conditional visibility hides the player when the URL is empty.
Switch Crew level to Engineer for the technical breakdown.
The same fields that fill each page also write the structured data search engines and AI assistants read.
Per-template [[JSON-LD]]: Article on insights, DefinedTerm on topic pages, FAQPage on answers, and one Organization with sameAs site-wide. [[AEO]] is the same discipline as SEO, aimed at answer engines.
Switch Crew level to Engineer for the technical breakdown.
It's built natively in the Webflow CMS, but the idea is just topics, entries and the links between them, so it moves to any platform.
Collections and references in Webflow; a custom post type plus a taxonomy in WordPress; reference arrays in Sanity; a topics list in Markdown front matter. Same three shapes everywhere.
Switch Crew level to Engineer for the technical breakdown.
What the site does for the people who run it and the people who visit it.
An entity-style vocabulary, internal links built from tags, and [[JSON-LD]] on every template.
Dateless cards, [[Finsweet]] CMS Filter with ?theme= deep links, and related rows from shared tags.
A voice profile distilled from the kit; drafts saved as CMS drafts; publish only after approval.
Native Collection Lists and bindings only, so there is no code for editors to touch.
Chapters parsed from a plain-text field; the written twin carries the Article schema.
Everything this mission delivered, planned and mocked up first, then built from the ground up.
A signed-off vocabulary, templates that build themselves from tags, and a Voice Kit, so every draft already sounds like you.
Platform · Year
Self-initiated identity
hours a month clients save by editing the CMS themselves
minutes, at most, to fill the Voice Kit once
schema types written from every entry for search + AI
drafts published without your approval
Every tool this mission ran on. Pull one out of orbit and let go; it finds its way back.
Tools in orbit