D
D
Dru Dro2015-11-17 20:31:30
CMS
Dru Dro, 2015-11-17 20:31:30

Which CMS to choose for documentation of multiple projects?

In my line of work, I have to work with many tools for writing docs, user guides, developer guides and other guides. Every day the tasks are different, solved in different ways and tools: from Help & Manual and Microsoft HTML Help Workshop to self-written programs that compile and assemble help files into the required formats.
The company I work for releases a lot of developer products for different purposes, programming languages, IDEs, operating systems, databases, etc. Hence the need to collect many formats of the same help: PDF, CHM, HXS, DOC, as well as online help. And now the moment has come when, to write documentation for each product, you have to use different third-party tools that differ in the generated help format.
In this regard, I am looking for a CMS with the following features:

  • Separation of the rights of writers docks in the admin panel. So that each participating TW can edit their documentation branch on the site (for projects, products, product lines).
  • The ability to create and maintain multiple projects, with different designs, different authors, ideally on different subdomains or branches of the site
  • Export/Import/Converter of various help formats: CHM, PDF, RTF, XML and its subsets (FB2/EPUB)
  • Ability to add individual HTML articles
  • Multilingualism
  • Advanced WYSIWYG editor
  • CNC

The implementation environment does not matter, at least in Delphi - if only all this could.
Any answer would be helpful.
PS if you have come across modules for non-specialized CMS - share links - I will be happy to test.

Answer the question

In order to leave comments, you need to log in

3 answer(s)
D
Denis _______________, 2015-11-17
@LuchS-lynx

xwiki :
- like any wiki engine, it allows you to flexibly configure access rights, both for groups and for individual users;
- there is nothing simpler - inside the Site, the wiki engine allows you to create an arbitrarily large number of subwikis, with their own local / global users, rights, privileges, settings, plugins, skins, etc.;
- by default, it allows you to save any page in pdf, if you put an addon, then supposedly (I did not test it personally), you can upload the entire wiki to pdf . As far as support for other formats, pages from pdf, provided that they are typed in the xwiki editor, are easily copied to the office and then exported to everything;
- html syntax is supported, as are programming scripts (Velocity, Groovy, Python, Ruby and PHP ), there is also an option for html with a macro ;
- the interface is translated into many languages, including Russian. The translation and display of texts in Russian is correct, there are no problems with the Cyrillic alphabet, except for the semantic search (the forms of the word "window" and "windows" for internal search are one and the same words);
- there is support for OpenOffice (you need to configure it manually), the WYSIWYG editor is standard, while it is convenient to switch (2 tabs) to plain text and back;
- if we are talking about links, then:
support for the Russian language rests on the mechanism for working with links, which for the Russian language creates links of the form:
Wiki Home\Test page\page with spaces
http://*Your_site*/xwiki/bin/view/Test +page/%D1%81%...
As far as I understand, this is Unicode, or an analogue. In principle, if you don’t get hung up on what is displayed in the link input line in the browser, the engine itself will offer to create a link of the form:
is an internal link, although it digests and appearances: http://*your_site*/*your_path*

E
Edward Tibet, 2015-11-17
@eduardtibet

Format: Docbook/XML (since 5.1) or DITA
Storage: GIT/SVN
Authoring tool: whatever writers adapt to
Publish - Apache Cocoon (for realtime publishing) or scripted build (if you just want to "serve the file")
Default are present:
1. Multilingualism.
2. The output is deliverable depending on the goal (audience/OS/customer, etc.)
3. Formats: PDF, html, ePub, word roundtrip (but needs improvement).
4. Version storage (diff/merge).
You can list for a long time, but if you are really interested in the details (the use of each item, features, etc.), then let me know with a comment.

S
Stanislav Salangin, 2016-07-21
@Salangin

Atlassian Confluence

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question