The Confluence Central Pattern (CCP): Building Your Team’s Single Source of Truth

[#1]

* This article is an English adaptation of a Japanese blog post originally published by Ricksoft. The original post was written to help teams reduce confusion and create a central landing page in Confluence for better knowledge sharing.

Feeling lost in your Confluence space?

Have you ever been handed a brand-new Confluence space and told, “From now on, your team will use this” — only to wonder:

• What exactly should we write here?

• Where do I start?

• Isn’t our file server or groupware enough?

• How does this differ from Jira?

If any of that sounds familiar, you’re not alone.

As someone who’s been using wikis for over 20 years, I’d like to share a practical and simple approach to get your team on track: The Confluence Central Pattern (CCP).

What is the “Confluence Central Pattern”?

The Confluence Central Pattern is a lightweight information-sharing strategy that treats your Confluence space as a “basecamp” — the hub that connects all other internal information.

In other words, Confluence becomes your team's Single Source of Truth (SSOT).

It provides clarity, assurance, and alignment across the team.

Visual Overview (see sample map below)

The CCP can be visualized as a single-page map on your team’s Confluence space homepage.

This page includes organized links to relevant team resources — such as:

• Shared folders

• Slack channels

• Jira boards

• Meeting notes

• Team goals

• Onboarding catalogs

This one page reduces confusion and gives the entire team a shared place to anchor themselves.

Start Minimal: “One Space, One Page”

Don’t overthink your structure.

Start with just one page in your team space — literally just one — and gather links to all scattered resources on it. That’s it.

Once your team has a page to “go to first,” you’ll be surprised how much smoother your collaboration becomes.

• Less time spent searching.
• Fewer duplicated documents.
• Lower onboarding friction for new members.

One Important Rule

Don’t abandon your top page.

Keep it up to date. Dead links or outdated info can quickly erode trust.

This page is your team’s shared “source of truth,” and it only works if it’s reliable.

Real Example: A Top Page in Action

Here’s a real sample from a team space homepage I helped design:

This single page helped new members onboard faster and fostered team trust — it’s like a user manual for your team.

Ready to Try It?

You don’t need a perfect setup.

Just create one top page, gather the links that matter, and invite your team to start from there.

Feel free to ask questions or share your team’s experience below!

[Jay Maechtlen]

Great suggestions. Our confluence includes many overlapping and interacting teams, many spaces, and many of those spaces have many, many pages. 

lots to consider, lots to do...