Establishing a workflow-driven review cycle for a client-facing knowledge base

[Alyssa Mattson]

I am creating a space with external-facing pages and would like to leverage Confluence macros/features to establish a workflow-driven review cycle for our materials.

I am looking for suggestions on effective ways to establish a structure in the space that launches a scheduled workflow-driven document review process. Ideally, I would want page owners to receive a prompt to review and update content, then move the page to next level steps for finalization. And of course, I would want this to happen outside of user visibility until the final edits are ready to be published. And icing on the cake would be documentation on the admin side of the review so at-a-glance, we can monitor the status of our full library.

I have played with a handful of macros, but I am hoping to gain insight from anyone who might manage a knowledge base in this manner. 

Thanks!

[Dave Rosenlund _Trundl_]

Welcome to the community, @Alyssa Mattson  👋

Confluence has many great notification features so users can be notified about new content or changes to existing content. And, lots of cool Macros. However, I think most long-time Confluence would agree it's difficult, if not impossible, to set up an effective approval workflow with those notifications + out-of-the-box-Macros.

If I were you, I'd have a look at Confluence Workflow solutions available on the Atlassian Marketplace.

One that I see frequently, is Comala Document Management for Confluence Cloud. It enables a multi-tier document approval process for Confluence spaces or pages. 

But there are others, too.  This screenscrape shows just the first six...

Best of luck to you.  I hope this helps,

-dave