I develop Public Pages for Confluence at TypeSwitch.
When working on Public Pages, I wanted to solve a simple problem: a team writes its documentation in Confluence, while customers need instructions they can access without signing in. Moving articles to a separate website creates two copies. Every change then means remembering where else the text needs to be updated.
The main difficulty is that an internal Confluence space and a customer knowledge base serve different purposes. Not everything useful to the team needs to be public. That is why I built Public Pages around selecting pages for publication and setting up a separate site with its own name, logo and custom domain. Working materials can stay internal, while instructions, FAQs and other pages visitors need are available publicly.
Confluence remains the place where the team writes and edits its material, and Public Pages handles its public presentation. For me, the point is to avoid maintaining a second copy of the documentation and give the team control over what customers see.
