Workflow for making private changes then going public?

[Thomas Summerall]

I have a published confluence wiki. I'd like to make a number of edits to existing pages over the next couple of weeks, as well as add some pages, but not have the changes available to the general public until I'm finished with all of them.

What's the best workflow for this?

One I can think of is cloning the space, making the edits to the privat eclone, then somehow replacing the original with the clone. Is something like that possible?

[Roberto Dominguez]

Hi!

Ad hoc Workflows allows you to collaborate before making pages public.

You can define a workflow on a page or for all the pages on a space, which would make the page only visible to you (or a predefined group), and once is approved it (publish) it becomes available to all the users.

The plugin comes with a set of predefined workflows, but they can be customized using our workflow markup.

We have a new version coming out very soon for Confluence 3.5 and 4.0, have a look at what you can do at http://coma.la/awp32

More complex publishing also is possible (from one space to another, and from one instance of confluence to another) in combination with the Content Publishing Plugin.

Give Ad hoc Workflows a try and feel free to contact us if you have any question.

Roberto

[Thomas Summerall]

I see on this page from October 2010 that the way Atlssian does it is copy an existing page, restrict it, edit the new copy, then, when finished, manually paste the new version contents into the old version. Really?

There has to be a better way!