Knowledge Base
Per-site brand and company facts people and agents share. The dashboard editor is Coming soon.
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 folder tree on the left and the selected folder on the right. That shape is the information architecture. It is not an HR handbook. There is no PTO, gear locker, or culture deck.
How you sound and look
- Voice: how this business talks.
- Visual standards: type, spacing, image treatment.
What is true
- Business facts: services, team, locations, claims.
- Decisions and rationale: why the site is shaped this way.
How you build and what you never do
- Technical: stack, integrations, gotchas.
- Prohibitions: never do X.
Later lanes
Operational playbooks and document provenance come later. The first tree stays these six so the board is easy to taste.
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 facts can be edited, 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.
- Open Knowledge Base from the sidebar for that site.
- Pick the category the fact belongs in.
- Add the fact in plain language. Keep secrets out.
- Save. The change should be attributed so the next reader can see who wrote it.
What is live today
The sidebar opens Knowledge Base to a folder tree and an empty facts list. Adding, editing, and deleting facts is later. Permissions and a change history are later too. Until facts land here, brand truth still lives wherever you keep it today. Agents should not pretend the folders are filled.