Confluence WordPress plugin
Content Publisher for Confluence imports the pages you edit in Confluence and publishes them on WordPress. A sync updates that copy after the next edit. Readers use your site, with no Confluence license.
The docs team stays in Confluence. WordPress is the site customers, or members, actually open.
Writers keep working in the Confluence space they already use. WordPress receives a copy. You are not maintaining a second draft in the WordPress editor after every product change.
A sync pulls the published Confluence pages you selected. On Free you press Sync Now. On Pro the same pull runs on a schedule: every 15 minutes, hourly, every 6 hours, or daily.
Once the page is on WordPress, the reader uses your site. They do not need a Confluence license, a guest seat, or an Atlassian login. That is the point of a public docs site or a help center.
A published page is a WordPress page or post. It uses your theme, your menu, and a URL you control. An embed is the other option, when the Confluence page should sit inside a page you already have.
These are different jobs. A docs site usually wants the first. A single article inside a marketing page wants the second.
The Confluence page becomes a WordPress page or post. Parent and child order stay, and internal links stay. Images and files go to the Media Library. Import as draft or private first, read it on the site, then publish. The plugin only pulls pages that are already published in Confluence.
The shortcode places one Confluence page inside a WordPress post or page you already wrote. You do not have to sync the whole space to do that. Use it for a single guide on a product page. Use publish when you are building the documentation site itself.
Still comparing tools? Read best Confluence WordPress plugins.
Standard page content converts: headings, tables, images, code, and attachments. Confluence-only macros do not. Status badges and Jira issue lists are skipped, because WordPress has no equivalent. Comments and task lists stay in Confluence.
Free is Sync Now. Pro can run every 15 minutes, every hour, every 6 hours, or once a day. A run skips pages that have not changed. Large syncs run in the background. This is not a live mirror of every keystroke.
Confluence page restrictions do not transfer. On WordPress, Free publishes the synced pages in public. Pro can set them to public, any logged-in user, or a specific role, for the whole sync or for one page.
Three steps. You can stop after a draft import and decide whether the pages look right.
Install the plugin from WordPress.org. Connect Cloud with OAuth, or with an API token. Data Center and Server can use a personal access token or basic auth. Use the method your Confluence admin already allows.
Pick one space on Free, or more than one on Pro. Select the whole space or only the pages you want public. Import as draft or private if someone should review the WordPress copy before it goes live.
Publish as posts or pages. Hierarchy and links stay. Images land in the Media Library. After the next Confluence edit, run Sync Now, or wait for the Pro schedule. Only changed pages are fetched again.
Publish, embed, sync, and decide who on the WordPress site can read the result.
Turn selected Confluence pages into WordPress pages or posts. Parent and child order and internal links stay intact. Start as draft or private, then make them public when the import looks right.
A shortcode shows one Confluence page inside any WordPress post or page. It works with your theme. You do not need a full space import for that one article.
Free: Sync Now, up to 10 pages, one space. Pro: unlimited pages and spaces, on a schedule of 15 minutes, hourly, every 6 hours, or daily. Unchanged pages are skipped.
Images and attachments from the Confluence page are saved with the rest of your WordPress media, so the public page is not depending on a Confluence URL the reader cannot open.
Free pages are public. Pro can limit a page to logged-in users or to a WordPress role, including a custom role from a membership plugin. Set a default for the sync, then override a single page.
Headings, tables, images, and code come across. Confluence macros that have no WordPress equivalent are skipped, including status badges and Jira issue lists. Page comments stay in Confluence.
Same plugin. The difference is who is allowed to open the WordPress page.
Product teams write in Confluence, then publish that space to a public WordPress documentation site. Customers get the current guide without a separate publishing step after every release.
Support writes the article in Confluence, then shares it on WordPress. The help center can match the internal wiki without giving every customer a Confluence account.
Engineering documents a feature in Confluence. The same page becomes the help article on the product site, so the internal note and the customer guide are not two files someone has to remember to update.
The WordPress site can be the front end for a members-only documentation site. Pro limits pages to logged-in users or a role. Free cannot. Those pages stay public on the free plan.
It publishes Confluence onto WordPress. It does not replace Confluence, and it does not sync the other direction.
This keeps Confluence as the place you write. If the plan is to move the docs into WordPress and stop using Confluence, a one-time import is the job, not an ongoing sync.
A Confluence public link or guest seat is enough when a handful of people need one page and you do not care about your theme, your URL, or search. A WordPress docs site is the step after that stops being enough.
An iframe can show Confluence inside a page until the reader hits a login wall or the frame breaks your layout. Publish the page when you want a normal WordPress URL instead.
Zapier and similar tools can move a single event between apps. They are a poor fit for a space of nested pages, images, and links. Use them for notifications. Use this plugin for the documentation.
Install the free plugin, connect one space, and import a draft. You can check hierarchy, images, and links before you pay for a schedule or a second space.
Free to install from WordPress.org. No card required for the free plan.
Use Free to prove the import on a real space. Move to Pro when you pass 10 pages, need another space, want the sync to run itself, or need to hide pages behind a WordPress role.
A small public doc set, or a test import before you commit. Install it from WordPress.org.
$99/year. For a docs site that should keep updating after the first import, across more than one space.
Sync timing, embeds, access, and what does not come across from Confluence.
Ask us about your spaceConnect one space and publish a draft. You will see whether the hierarchy, the links, and the images survive before you pay for a schedule.
Get support
We reply within one business day.
We got your message
Someone on the RippleStep team will follow up shortly. No need to resubmit.
Email supportBook a demo
Tell us about your stack. We will follow up with a focused walkthrough of RippleStep.
