Satori Cloud
Product documentation

Publish product documentation from Confluence

Turn selected Confluence pages into a customer-facing documentation site without copying your guides into another CMS or sending readers into your internal workspace.

Start publishing See how it works
Keep writing in Confluence Select only customer-facing pages No Confluence login for readers
yourcompany.satoricloud.com
Example product documentation website published from Confluence
Navigation
Branding
External site

The publishing problem

Your team already has product documentation. Publishing it is the extra job.

Product teams often use Confluence for setup guides, feature documentation, implementation notes, troubleshooting and release information.

That works well while the audience is internal. The difficulty comes when customers need the same information but should not have to enter the workspace where it was written.

Copying those pages into another documentation system solves the presentation problem, but creates two versions of the same knowledge.

One writing workflow

Keep product knowledge in Confluence. Give customers the external version.

Keep authors in Confluence

Product, engineering and support teams continue maintaining documentation in the spaces and pages they already own.

Choose what customers see

Publish the pages that belong in the customer documentation while leaving internal notes and unrelated content out.

Give readers a documentation site

Customers read the published version instead of navigating your internal Confluence workspace.

Documentation structure

Turn your existing pages into a useful customer journey.

Start with the content customers need to understand, configure and use your product.

Getting started

Prerequisites, initial setup and first steps.

Configuration

Explain settings, integrations and configuration options.

How-to guides

Task-focused instructions for everyday product use.

Troubleshooting

Known issues, checks, fixes and next actions.

Product changes and release information

Keep product changes alongside the guidance customers use, rather than scattering updates across emails and files.

How it works

Confluence in. Customer documentation out.

Satori sits between your team's existing Confluence workflow and the external site customers read.

01

Connect Confluence

Connect the Confluence workspace containing your documentation.

02

Select your pages

Choose the pages that should be part of the customer documentation.

03

Sync and preview

Sync the latest content into a draft and check it before changing the live site.

04

Publish

Publish explicitly when the customer-facing version is ready.

Documentation navigation

Bring useful Confluence structure into the published site.

Satori can preserve useful page and folder grouping so the external site does not have to become one flat list of articles.

You still choose which pages are actually published.

Documentation
Getting started
Create your workspace
Configure your account
Integrations
Connect Slack
API and webhooks

Avoid duplicate documentation

Update the source instead of chasing copies.

Your team maintains the Confluence version. Satori provides the draft and published customer-facing versions.

Source
Product documentation maintained in Confluence

Confluence

The content your team owns and edits.

Customer-facing
Published customer-facing product documentation

Published product documentation

The version customers read.

Go deeper

Some product documentation needs its own experience.

External API documentation

Publish API setup, authentication and implementation guidance for developers.

Explore API documentation →

Developer portal

Bring technical guides and developer resources together in an external destination.

Explore developer portals →

Customer onboarding

Turn setup and implementation documentation into a guided onboarding destination.

Explore onboarding →

Product docs or knowledge base?

Publishing support answers rather than product guides?

If the primary job is helping customers find answers to common questions, troubleshooting and support issues, a knowledge-base structure may be the better fit.

Create a knowledge base

FAQ

Publishing product documentation from Confluence

Can I use Confluence for customer-facing product documentation?

Yes. Your team can maintain the source documentation in Confluence and use Satori Cloud to publish selected pages as a separate customer-facing site.

Do customers need Confluence accounts?

No. Readers visit the published Satori site rather than logging into your Confluence workspace.

Do I need to copy the documentation into Satori manually?

No. You connect Confluence and select the pages you want to publish. Confluence remains the source.

Can I choose individual pages?

Yes. You choose the pages that belong on the external documentation site rather than automatically publishing the whole workspace.

What happens when the Confluence documentation changes?

Sync the latest Confluence content into the Satori draft, preview the changes and publish when you are ready for the live site to update.

Can I publish product documentation without exposing the rest of Confluence?

Yes. Satori publishes the pages you select. For the broader model, see our guide to publishing Confluence without giving people access .

Related guides

Other ways to publish Confluence externally

External sharing

Share Confluence pages externally

Read the guide →

Customer support

Create a public knowledge base from Confluence

Read the guide →

Developer content

Publish external API documentation

Read the guide →

Your product documentation is already in Confluence. Publish the version customers need.

Connect Confluence, choose your customer-facing pages and publish them as an external documentation site.

Start publishing