Knowledge Base

Coming soon on the longer handbook. What follows is the live surface, not a promised catalog.

The Knowledge Base is the shared truth of a site: how you sound, what is true about the company, what you sell, how the public site is organized, and the files that prove it. People and agents should read the same board. Content tools and Requests consume it. They are not its home.

What it holds

This is not a second blog and not a Request thread. It holds facts that must stay true when someone writes a post, answers a lead, or builds a change.

• Who you are, how you sound, and what you sell.
• How the public site is organized, and what already lives on it.
• How to answer a lead, and which claims you will not make.
• Files and notes that support that work. No secrets.

Why it belongs here

The feature test is the same as the rest of the platform. If a fact fails all three, it stays in the developer lane or in a staff handbook somewhere else.

State

Does it record the current truth of the company and the site in a way people and agents must share? Yes. Voice, prices, the page map, and approved claims.

Permission

Does it decide who may change those facts? Yes. The owner and the people they invite should govern edits. A worker reads. It does not silently rewrite the board.

Change log

Does it leave a history of what changed and who changed it? Yes. A fact someone relied on yesterday should still be findable tomorrow.

Categories

The home is a category grid, one tile per lane. That shape is the information architecture. It is not an HR handbook. There is no PTO, gear locker, or culture deck.

Brand and company

• Brand & voice: how you sound, words you use, words you never use.
• Company facts: name, who you serve, where you work, what is true about the business.
• Offers & pricing rules: what you sell, what you do not, how price is described.

The site and what you publish

• Website & IA: pages that exist, what each is for, what must not move.
• Blog & content: topics you cover, tone for posts, what not to publish.
• Assets: logos, photos, and files the site may use.

How you answer

• Lead response playbook: how Inbox replies should start, what to ask, when to hand off.
• FAQ & objections: answers you already stand behind.

Guardrails

• Compliance & claims: what you may say, what you must not claim.
• Integrations notes: how a pipe is set up, without passwords or keys.

What it is not

• Not HR, PTO, equipment, or an internal wiki for staff life.
• Not the blog. Posts still live in Blog.
• Not Requests. A change to the live site still files a Request.
• Not a place to store secrets. Integrations notes stay notes.

Who can change it

When the surface ships, edit permission lives on the site, same as other state. Owners and admins should govern what is true. Developers may help fill it. A worker may read it. A worker should not invent a missing fact and write it back as if it were approved.

1. Open Knowledge Base from the sidebar for that site.
2. Pick the category the fact belongs in.
3. Add the fact in plain language. Keep secrets out.
4. Save. The change should be attributed so the next reader can see who wrote it.

What is live today

Coming soon in the dashboard. The first Taste slice is a nav label and an empty category grid so you can see the shape. Filling tiles, permissions, and a change history are later. Until that ships, brand facts still live wherever you keep them today. Agents should not pretend this board already exists.