Re: Content Management ... was RE: Tools

Subject: Re: Content Management ... was RE: Tools
From: Nina Barzgaran <nina -dot- barzgaran -at- barzgaran -dot- at>
To: arh -at- groupwellesley -dot- com, annette -dot- reilly -at- computer -dot- org, 'Syed Zaeem Hosain' <Syed -dot- Hosain -at- aeris -dot- net>, techwr-l -at- lists -dot- techwr-l -dot- com
Date: Sun, 6 Dec 2020 21:39:45 +0100

Perhaps a little late-in-the-day answer, but I can only confirm what has been said about Confluence before. Beware:
* It is a pain to use if you know anything about proper technical documentation and its management as well as output formats.
* If you want to publish not just internally but have proper customer-facing documentation online, it becomes worse at every turn.
* Confluence is being marketed as a tool you can use for technical documentation. But it is not.
* You need heaps of plugins to make it work that way. Often those plugins are only partly compatible. That lands you, bluntly put, in 'plugin hell'.
* I can only agree with previous posters on this thread:
** Get your requirements sorted and properly specified, incl. all departments concerned and outputs you know about so far.
** Find out more about the near future of possible extensions to this as regards customer service or developing technologies and standards.
** Evaluate tools and then test.
** Only then make a decision that includes at least the informed voices of all concerned.
** Everything you mentioned can be solved using a well-defined tool-chain.
* Confluence is NOT a HAT (help authoring tool). It never was.
It is great for collaborating! As a kind of Wiki, with loose standards behind it as regards standards of writing or formatting. It is not less - but also not more!


Am 11/11/2020 um 03:41 schrieb Alan Houser:

I wanted to second Annette Reilly's recommendation of ISO/IEC/IEEE 26531:Â 2015. The specification is exceptionally well-done and thorough, and will inform requirements identification and selection for any organization that is deploying a content management system for documentation.

The specification is not inexpensive; approximately $100 US, depending on format and IEEE membership status of the purchaser. However, this is a trivial investment compared to the cost of a CMS. It's also a sound investment for consultants who support CMS selection and adoption.

You can purchase the standard here:


On 11/10/20 5:31 PM, Annette Reilly wrote:
ISO/IEC/IEEE 26531:Â 2015 contains requirements for content management and for a CMS.

This International Standard provides requirements for the management of the content used in product life cycle, software, and service management system documentation. Content management allows an organization to control the storage and retrieval of content objects, track content revisions, maintain a content audit trail, and enable a collaborative environment. Component content management supports the reuse of content objects among deliverables and supports multiple deliverable formats. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. The standard defines the characteristics of an effective and efficient process through which content is gathered, managed, and published, including the requirements of a system that is supported by an electronic database.

-----Original Message-----
From: Syed Zaeem Hosain <Syed -dot- Hosain -at- aeris -dot- net>
Sent: Monday, November 09, 2020 3:44 PM
To: Nina Barzgaran <nina -dot- barzgaran -at- barzgaran -dot- at>; techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Content Management ... was RE: Tools

Does anyone have a Requirements doc for a content management system that they could share with me?

Thanks much!


Nina Barzgaran, M.A.
Technical Communicator
Linzer StraÃe 434-436/3/23
1140 Wien

Visit TechWhirl for the latest on content technology, content strategy and content development |


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

Previous by Author: Re: email Client Thunderbird and this Techwr-l List... Duplicate Messages?
Next by Author: Re: Content Management ... was RE: Tools
Previous by Thread: Re: Looking for a free or very low cost HAT
Next by Thread: Re: Content Management ... was RE: Tools

What this post helpful? Share it with friends and colleagues:

Sponsored Ads