Satori Cloud
Developer documentation

Create a developer portal from Confluence

Turn API guides, developer onboarding, implementation documentation and technical resources from Confluence into one focused external destination.

Create your developer portal See portal structure
Keep Confluence as the source Publish selected developer content No Confluence login for readers

Acme Developers

Developer resources

Developer portal

Overview
Getting started
API guides
Integrations
What's changed
Support

Welcome

Build with Acme

Everything you need to understand the integration, get access and start building.

Get started

API guides

Confluence publishing advisor

How should you share your Confluence content?

Answer four quick questions to find the best way to share Confluence pages with customers, partners, employees, or the public.

Get a clear recommendation in under a minute

We will compare public links, anonymous access, guest access, manual sharing, and publishing as a simple website.

The developer experience problem

Developers need a starting point, not a pile of internal links.

Useful developer knowledge often already exists across Confluence: API setup, authentication, implementation guidance, architecture notes, troubleshooting and support information.

Internally, those pages may work perfectly well because your team knows where everything lives and why it was written.

External developers have none of that context. They need a clear route from understanding your integration to getting access, building successfully and finding help.

Where things break down

The developer content exists. The external experience often doesn't.

Guidance is scattered

Setup, authentication, implementation and support information can live across several internal areas.

Internal docs feel internal

The content may be accurate while its structure and surrounding context still assume an internal audience.

Workspace access is too much

External developers need useful documentation, not access to the environment where your team collaborates.

Copies drift

Copying developer guides into another CMS gives your team another version to maintain.

Onboarding lacks a path

Developers need a route from “what is this?” to “my integration works”.

Questions repeat

When developers can't find the right guidance, product, support and engineering answer the same questions manually.

Lightweight developer portal

Satori is the documentation layer — not your entire developer platform.

Different developer experiences need different infrastructure. Satori has a deliberately narrower job.

Full developer platform

Platform capabilities

Developer accounts, API keys, app registration, usage dashboards, API catalogues, sandboxes and other operational capabilities.

Confluence

Authoring and collaboration

Product, engineering, support and implementation teams create, review and maintain the written developer knowledge.

Satori Cloud

External documentation

Publish selected Confluence pages as a focused external destination developers can navigate without joining your workspace.

Developer portal structure

Organise around the developer journey.

A useful portal does more than group technical pages. It helps somebody understand where they are and what to do next.

Developer overview

Explain what developers can build, who the integration is for and where to begin.

Getting started

Give developers the prerequisites and steps needed to begin integrating.

API guidance

Authentication, access, environments and explanatory API documentation.

Implementation guides

Publish integration patterns, workflows, examples and practical guidance.

Changes and migrations

Give developers somewhere to understand important changes, upgrades and migration guidance.

Support routes

Explain where developers should go for questions, access issues and integration support.

Developer journey

From “what can I build?” to “my integration works”.

01

Understand

Learn what is available and whether it fits the use case.

02

Get ready

Understand access, authentication, environments and prerequisites.

03

Build

Follow implementation guidance and integration patterns.

04

Operate

Find troubleshooting, changes and support when needed.

How Satori works

Keep developer knowledge in Confluence. Publish the version developers need.

01

Connect Confluence

Connect the workspace containing your developer knowledge.

02

Select developer pages

Choose the content that belongs in the external portal.

03

Sync and preview

Pull the latest source content into a draft and review the portal first.

04

Publish

Explicitly publish when the developer-facing version is ready.

Only need API documentation?

A developer portal can contain more than API guides.

If your requirement is specifically to publish authentication, API setup, implementation and troubleshooting guidance, the external API documentation guide is the more focused use case.

External API docs guide

When this approach fits

Best when useful developer knowledge already exists in Confluence.

Product, engineering or implementation teams already maintain useful developer guidance in Confluence.

Customers and partners need that information without access to your internal workspace.

You need a documentation destination rather than a full API-management platform.

You want to keep the maintained source in Confluence instead of recreating the docs elsewhere.

Related documentation

Connect developer content to the wider customer journey.

External API documentation

Publish focused API and implementation guidance from Confluence.

Explore API docs →

Product documentation

Publish broader product guidance alongside your developer resources.

Explore product docs →

Customer onboarding

Bring technical setup into the wider onboarding journey.

Explore onboarding →

FAQ

Creating a developer portal from Confluence

Can Confluence be used for a developer portal?

Confluence can be a useful place for your internal teams to maintain developer documentation. Satori Cloud lets you publish selected pages as a separate external developer-facing site.

Is Satori Cloud a full developer portal platform?

No. Satori is a lightweight publishing layer. It does not replace capabilities such as developer account management, API-key generation, application registration, sandbox provisioning or API management.

What can I put in a developer portal?

Useful content can include developer overviews, getting-started guides, API guidance, authentication instructions, implementation documentation, troubleshooting, change information and support routes.

Do developers need Confluence accounts?

No. External readers access the published Satori site rather than logging into your Confluence workspace.

Does this replace an OpenAPI or Swagger reference?

No. Generated API reference is still better suited to structured endpoint information. Satori is useful for the narrative and explanatory developer guidance maintained in Confluence.

What happens when the developer documentation changes?

Sync the latest Confluence version into your Satori draft, preview the portal and explicitly publish when the updated version is ready.

External Confluence publishing

Developers need your documentation, not access to the workspace where it was written.

See the broader Satori model for publishing selected Confluence content while keeping the internal workspace separate.

Read the publishing guide

Your developer knowledge is already in Confluence. Give developers somewhere designed for them.

Connect Confluence, choose the developer-facing pages and publish them as a focused external portal.

Create your developer portal