# Unified product portal

**Combine multiple Confluence spaces into a single, cohesive portal that surfaces everything about your product in one place.**

Your product has user docs, API references, release notes, and guides - but they live in separate Confluence spaces, separate tools, or both. Customers bounce between bookmarks, search across disconnected systems, and never quite feel like they're in one product experience. Your team spends time maintaining duplicate navigation and cross-links instead of writing better content.

Capable Sites lets you stitch multiple Confluence spaces together into a single branded portal at a URL like `portal.yourproduct.com`, with unified navigation, consistent theming, and no content duplication.

---

## [#](#the-problem)The problem

Product teams juggle documentation across too many places. User-facing docs live in one Confluence space, API references in another, release notes in a third, and maybe a changelog lives in a completely separate tool. The result is a fragmented experience for customers and a maintenance headache for your team.

Common pain points include scattered content that forces customers to hunt across multiple URLs or bookmarks, inconsistent branding where each space or tool looks slightly different, manual cross-linking between spaces that breaks over time, and no single entry point where someone new can start and find everything about your product.

For product teams, this fragmentation undermines the polished, professional experience you've built everywhere else in your product.

## [#](#the-solution)The solution

With Capable Sites, you map multiple Confluence spaces into a single site with shared navigation, a unified homepage, and custom URL paths - all published to your own domain.

Here's how it works in practice. You start by mapping spaces like "User Docs", "API Reference", and "Release Notes" into one site. Each space becomes a tab or section, and you designate a homepage (or a dedicated home space) that acts as the portal's front door. Visitors see one coherent site, not a patchwork of Confluence spaces.

Next, you assign custom space slugs - `/docs/`, `/api/`, `/changelog/` \- so URLs are clean and intuitive. Add header links pointing to your app, status page, community forum, or support desk, and the portal feels like a first-class part of your product ecosystem rather than a bolt-on wiki.

For teams with API or developer content, Capable Sites renders Swagger/OpenAPI specs, code blocks, diagrams, and other interactive macros directly on the published site. There's no need to export to a separate developer docs platform.

When you restructure content or version your docs, redirect rules (both permanent and temporary) keep old URLs working so you don't break bookmarks or search engine rankings.

Finally, you fine-tune the look with custom CSS, design tokens, and dark mode tokens so the portal matches your design system - not Confluence's default look.

## [#](#key-features)Key features

* **Multi-space publishing** \- Combine any number of Confluence spaces into a single site with space tabs and a shared homepage. Each space retains its own page tree but appears as one unified experience to visitors.
* **Custom URL structure** \- Assign slugs like `/docs/`, `/api/`, and `/changelog/` to each space. Add header links to external destinations (your app, status page, community) for seamless product-level navigation.
* **Rich developer content** \- Swagger/OpenAPI rendering, syntax-highlighted code blocks, Mermaid and drawio diagrams, and other interactive macros publish natively. No separate developer docs tool needed.
* **Redirect management** \- Set up permanent (301) and temporary (302) redirects when you move, rename, or version content. Protect your SEO and keep existing links working.
* **Staging and production** \- Preview the entire portal in staging before pushing changes live. Especially useful when restructuring multiple spaces at once.

## [#](#who-this-is-for)Who this is for

This use case is ideal for product teams at SaaS companies who want a professional, unified product portal without adopting a dedicated docs platform for every content type. It's especially valuable when you already have content spread across multiple Confluence spaces and want to bring it together under one roof - and one URL - without migrating away from Confluence.

## [#](#get-started)Get started

1. Identify the Confluence spaces you want to combine (e.g., user docs, API reference, release notes, guides).
2. Create a new site in Capable Sites and add each space, assigning custom slugs and tab labels.
3. Set up a homepage or designate a home space to act as the portal's landing page.
4. Add header links to your app, status page, and community.
5. Apply your brand's CSS and design tokens, including dark mode if needed.
6. Preview in staging, then publish to your custom domain.