DEV Community

Maxym Babenko
Maxym Babenko

Posted on

I built a simple way to publish Confluence pages to the web

Hey DEV community 👋

I recently built Public Pages for Confluence, a small app for teams that write content in Confluence but need an easier way to publish some of it publicly.

The idea came from a simple problem: Confluence is great for writing internal docs, product notes, guides, and knowledge base content, but publishing that content to the public web often means using another CMS, a heavy site builder, or copying the same content somewhere else.

I wanted to make that workflow simpler.

What it does

Public Pages for Confluence lets you publish selected Confluence pages as public web pages.

It is useful for things like:

  • help center articles
  • knowledge base pages
  • product guides
  • release notes
  • public documentation
  • customer-facing content

The goal is not to replace a full documentation platform. It is more focused: keep writing in Confluence, choose which pages should be public, and publish them to the web.

Why I built it

A lot of teams already have useful content inside Confluence, but it stays hidden from customers, prospects, or search engines.

Native public sharing can work for simple access, but it often feels limited when you need a more polished public page, SEO metadata, analytics, branding, or a custom domain.

So I built a lighter workflow for publishing Confluence pages externally without moving content into another system.

Current features

  • publish selected Confluence pages publicly
  • clean public URLs
  • SEO title and meta description
  • Google indexing controls
  • automatic sitemap support
  • GA4 analytics
  • Search Console verification
  • logo and site name branding
  • custom domain support

It is also free for teams up to 10 users.

Marketplace link:
https://marketplace.atlassian.com/apps/356517983/

I would love feedback from anyone who uses Confluence for documentation, help centers, product guides, or public knowledge bases.

Especially curious about this question:

Would you prefer a lightweight publishing tool like this, or do you usually need a full site builder for public documentation?

Top comments (0)