DITA vs维基vs CMS vs？ [英] DITA vs Wiki vs CMS vs?

问题描述

我被要求找到一个适当的文档框架/应用程序在我的组织内使用。我需要支持以下内容的内容：

• HTML（单页）


• HTML Page）


• PDF


• 多种语言（英语和法语，但不限于这些）

我正在寻找一些东西来抽象Look&

解决方案

我谦卑地认为，最重要的问题你在选择工具之前需要问自己：

谁需要编辑文档：

• 你有一个作家或一个小团队的专职作家，他们可以花一些时间学习一个中等复杂的（但从长远来看更高效的再利用，本地化支持，跨渠道发布...）

或

• 您有大量的内容提供者，他们没有时间和/或动机学习新工具吗？

根据我的经验，如果你有一个小型的专门团队，你可以去一个专门的工具，如DITA XML，或更复杂的DocBook XML。如果你有很多潜在的作家，wiki是要走的路。

本地化有多重要？

• 您是否要将网页手动导入一种或两种语言？

• 您会使用翻译公司并支持八种，十种，十几种语言？

<




维基服务器通常支持本地化，但只支持一定的程度。导出内容进行翻译并不容易，需要插件或自定义开发。 DITA XML等文档框架是专为翻译而开发的，并且由专业翻译工具支持开箱即用，因此代理商不会对其进行任何处理。





所以...





如果重用是你的首要考虑，一定要转向一个框架，如DITA XML（我使用它在我的工作场所，我们真的很高兴我们做出的选择）。您将能够根据过滤器属性，使用不同样式表将不同的输出格式（HTML，PDF，EPUB，...）输出到不同的目标受众，并以各种方式重用内容。 / p>



然而，如果你设想让许多不同的人贡献，一个现代的维基例如Confluence可能是一个更明智的选择。我们正在以这种方式为我们的知识库，以降低支持工程师，产品经理和其他临时作家贡献的门槛。





希望有帮助！




I've been asked to find a proper documentation framework/application for use within my organization. I need something that will support the following:

• HTML (Single Page)
• HTML (Multiple Page)
• PDF
• Multiple Language (English & French, but not restricted to those)

I'm looking for something that would abstract the Look & Feel from the content, therefore able to reuse content as much as possible.

解决方案

In my humble opinion, the most important questions you need to ask yourself before choosing a tool are the following:

Who needs to edit the documentation?

• Do you have one writer or a small team of dedicated writers, who can afford to spend some time learning a moderately complex (but in the long run more efficient in terms of reuse, localization support, cross-channel publishing, ...)?

OR

• Do you have a large number of content contributors, who will not have the time and/or motivation to learn new tools?

In my experience, if you have a small dedicated team, you can afford to go for a specialized tool such as DITA XML, or even more complex, DocBook XML. If you have a lot of potential writers, wiki is the way to go. In this respect, it is hard to beat Atlassian Confluence.

How important are localizations?

• Do you intend pages manually into one or two languages?

OR

• will you use a translation agency and support eight, ten, a dozen or more languages?

Again, those are two vastly different scenario's.

Wiki servers typically support localizations but only to a certain extent. Exporting content for translation is not easy, and will require either plug-ins or custom development. Documentation frameworks like DITA XML are built for translation and are supported out of the box by professional translation tools, so agencies will not have any trouble dealing with them.

So...

If reuse is your primary concern, by all means turn to a framework such as DITA XML (I am using it at my workplace, and we're really happy we made the choice). You will gain the ability to output one source to different output formats (HTML, PDF, EPUB, ...), to different target audiences based on filter attributes, to different brandings using different stylesheets, and to reuse content in various ways.

However, if you envisage getting many different people to contribute, a modern wiki such as Confluence might be a wiser choice. We are moving this way for our knowledge base, to lower the threshold for support engineers, product managers and other occasional writers to contribute.

Hope that helps!

这篇关于DITA vs维基vs CMS vs？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！