Question

Hello, i#m thinking about using TWiKi in our comapny for documentation purpose. But for this, i miss a function similar to the "stable version"-function in the german Wikipedia.

That means that an authoritised User can mark a version of a website as "stable". After this, all guests of the wiki see only this marked version, but not the actuall modified versions.

This function is important for us because we are creating the documentation for our customers and they should only see those versions that have been checked and not the ones that are in work and maybe contain a lot of distressing errors.

Also i dont want to administrate two different WiKi-sites and copy always documents from the "working"site to the "official"-site.

I have searched the TWiKi-documentation for this function, but didnt found it.

Environment

-- RasmusThorden - 13 Sep 2008

Answer

If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.

Can't you 'freeze' a content by simply publishing it to a static site?

-- FranzJosefGigler - 14 Sep 2008

Rasmus, I guess that with TWiki the only solution would be to have a script copy the whole "dev" site to the "official" one. Otherwise, you will have plenty of details to fix (such as separate email notifications & RSS for the dev & stable, etc...). If you do not want your customers to be able to modify the official version, I would suggest just create such a script that would be basically a copy (via rsync) and a change of the copied lib/LocalSite.cfg to change the host name (or just do not copy this file), or perhaps better for you, just use the PublishContrib or PublishWebPlugin. If you want your users to give feedback, you can put a link in the official wiki site skin to a comment system like http://js-kit.com or to the dev wiki pages, or to a forum, mailing list, ...

-- ColasNahaboo - 14 Sep 2008

Hello Colas, thanks for your suggestion. I think the best practise ist to publish special pages with the PublishContrib to a static html or a pdf. Is it possible to do this by just a click on a special button in the pages on the "dev" side?. So that the writers does not need to fill out those export form, what, i suggest, will make some confusion (well, maybe).

The PublishWebPlugin is not suitable, beecause automatic export with every Save-action is really not that what we need.

-- RasmusThorden - 15 Sep 2008

Ah yes. And pubslishing the whole "dev"-web is also not suitable. We should make it page by page. You know, we had the big problem that we are less people, many work and less time for documentation. So only little parts will be writen and checked at one time and those parts should then be published as fast as possible.

-- RasmusThorden - 15 Sep 2008

Some of the points in HowToImproveDocumentPublishWorkflow might be of use. For example, you could define your 'dev' and 'stable' states with the WorkflowPlugin .

-- SeanCMorgan - 15 Sep 2008

-- RasmusThorden - 26 Sep 2008