Confluence Knowledge Base: Organize Pages for People and AI

A Confluence knowledge base is a maintained collection of pages that answers a defined group of questions. To build one, choose an audience, organize pages around its work, name an owner for each answer, and check that readers can find and use the current guidance.

The pages explain how work should happen; a project also needs a record of what people decided and where they stopped. fenbs can keep that smaller work record beside Confluence through manually curated links and context. fenbs does not connect to Confluence or automatically import its pages.

How do you build a useful first space?

1. Choose one audience and job. For example, start with designers handing approved website layouts to developers, rather than collecting everything the company knows.
2. List the questions that block that job. Turn “Where are the approved assets?” and “Who approves a change?” into clear page titles or entry links.
3. Create a space overview that points to those answers. Group related pages under a few parent pages, such as Getting started, Working instructions, and Reference.
4. Write the first answers with an owner, scope, review date, and source links. Ask the owner to check the instructions against a real example before treating them as current.
5. Give a teammate a realistic question without telling them the page name. Observe where they look, fix the confusing title or navigation, and repeat before adding more material.

Confluence supports parent and child pages, shortcuts, and labels for grouping related content; Atlassian explains these in its space organization guide↗ (opens in a new tab). Use the page tree for the main route and a small, agreed set of labels for topics that cross those groups. A label should describe something readers recognize, rather than an author’s private filing system.

Who owns an answer after it is published?

Assign a person who can verify the substance, not just edit the wording. An onboarding page might belong to the person who runs onboarding; a release checklist needs someone who understands the release process. Write down a backup so an absence does not leave the page without anyone able to check it.

Confluence gives created content an owner and supports transferring content ownership↗ (opens in a new tab). Use that capability when responsibilities change, then confirm that the new owner accepts the maintenance work. An ownership change should trigger a quick review of the most important instructions and their source links.

Keep review dates honest. “Reviewed” should mean somebody checked the answer, tried the relevant steps where practical, and resolved known conflicts. A date changed by habit is not evidence that guidance remains correct. When a page cannot be checked, say what is uncertain and whom a reader should ask before relying on it.

What should each page contain?

Start with the answer and its scope. A page called “Send design files to development” should say which files are required and when the handoff is ready, before explaining background. A reader on a phone should not need to search a long meeting transcript for the actual instruction.

• Purpose: the task this page helps someone complete and the situations it covers.
• Instructions: an ordered sequence, with examples of a successful result and any important exception.
• Evidence: links to the approved specification, original agreement, or other authoritative source.
• Maintenance: owner, last substantive check, next review, and the place to raise a correction.

Choose a published page when the answer needs a deliberate publication step. Atlassian distinguishes pages with drafts and version history from live docs↗ (opens in a new tab), whose changes are immediately visible to collaborators. Match the format to the work instead of treating every piece of writing as finished guidance.

How do you give an assistant reliable source context?

Make the source easy for a person to inspect first. A reference should identify the page title, why it matters, and which part supports the instruction. If a decision depends on a particular published version, record that version or its review date alongside the link. The next reader needs to recognize when the source has changed.

A pasted URL does not give an assistant permission or a way to open a private page. Provide an approved excerpt when that is appropriate, or use a separately authorized source connection. The Confluence MCP guide covers that connection question; MCP is a standard way for an AI app to use an outside tool.

Ask an assistant to distinguish the source statement from its interpretation. “The checklist requires an approved layout” is different from “the layout was approved.” The second statement needs evidence from this project. Keep that project evidence and the remaining action in the shared work record, rather than rewriting the general checklist for every job.

In fenbs, AI context notes can hold the checked explanation and source reference the next assistant needs; how it works describes the record assistants read before continuing.

How do you prevent conflicting and stale guidance?

Maintain one current answer for each question. When two pages disagree, ask the owner to resolve the difference rather than asking readers or AI to choose whichever sounds more convincing. Mark an outdated page clearly and point readers toward its replacement, following your organization’s retention requirements.

Review pages when the underlying work changes: a new approval process, a changed product, or a handoff failure. Also schedule periodic checks for high use guidance. During a review, follow the links as an ordinary reader, check the examples, and remove instructions that no longer describe the job.

For choosing a broader repository, see internal knowledge base software; this setup focuses on making Confluence pages dependable. The wider team brain library covers how that reference material supports shared work.

How to do this with fenbs

1. Create a free account, add one project, and describe the work the Confluence pages support. A personal account is free for one person, no credit card.
2. Add the important page references to Links and listings. Write an AI context note explaining which source applies and what a person has checked; do not copy a whole space.
3. Record the choices a person approved in Decisions and rules, including the reason and relevant source reference. Keep an unresolved conflict open for a person to decide.
4. Connect a supported AI app from Integrations. Ask it to read the project context before working, then save progress and the next step in Where we left off before stopping.

Keep the long instructions in Confluence and give fenbs the current project meaning: which guidance applies, what was approved, and what remains. This is especially useful for an AI handoff when the next assistant would otherwise need the whole discussion explained again.

fenbs is not the right fit for hosting a Confluence-style page library or synchronizing its contents. Keep page publishing and document maintenance in the source system, and update the smaller project record deliberately when their meaning changes.