如何让非技术同事能够向您提供 HTML 格式的内容和文档？
我正在开发一个面向公众的基于网络的产品，该产品有一系列帮助文件。
负责制作这些帮助文件的同事精通 Microsoft Word。他们不熟悉 HTML。他们的工作站不包括 Visual Studio。
因此，看起来将会发生的是，他们将在 Microsoft Word 中编写帮助文件内容，然后我必须获取该内容并将其转换为网站最终呈现的 HTML。
Microsoft Word 具有 HTML 导出/保存功能，但上次我看到的输出是噩梦般的，使用起来很可怕。
对此内容的更新（我相信会有很多）将是一个类似的协调麻烦。
我很想向这些同事提供 Microsoft Visual Web Developer 2008 Express Edition 的下载链接，但我不确定这对他们来说是否太难使用，因为它可能太像 Visual Studio，他们不熟悉，而不像 Word，它有他们需要的工具，如拼写检查和等等。
当然，这不是一个独特的问题。当您在该领域的团队主要由提出代码并将帮助文件放置到位的开发人员以及提出帮助文件内容但不是技术人员的同事组成时，最好的最轻松的方法是什么让他们为您提供 HTML 或接近 HTML 的内容？
I'm working on a public-facing web-based product which has a series of help files.
The coworkers whose job it is to make those help files are fluent in Microsoft Word. They're not fluent in HTML. Their workstations do not include Visual Studio.
So what it looks like is going to happen is they will author the help file contents in Microsoft Word and then I will have to take that content and turn it into the HTML which the site will ultimately render.
Microsoft Word has HTML exporting/saving functionality but last time I looked the output was nightmarish and terrifying to work with.
Updates to this content (and I'm sure there will be many) will be a similar coordination hassle.
I'm tempted to get these coworkers a download link to Microsoft Visual Web Developer 2008 Express Edition, but I'm not sure if that will be too difficult for them to use since it may be too much like Visual Studio, which they're not familiar with, and not enough like Word, which has tools they need like spell checking and so forth.
Surely this is not a unique problem. When your team in this area essentially consists of the developers who come up with the code and drop the help files into place, and coworkers who come up with the help file content but aren't techies, what's the best most pain-free way to get them to give you HTML or near-HTML content?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
为该程序以及其他可能的程序设置一个用户文档 Wiki 怎么样？
这样，您的文档人员就可以使用“类似单词”的环境，即使他们将内容从 Word 复制并粘贴到 Wiki 中也是如此。您有一种非常技术友好的方式来管理内容。
What about setting up a user documentation Wiki for the program, and potentially others?
That way your documentation folks have a "word like" environment to work with, even if they are copying and pasting their content from Word into the Wiki. You have a very tech friendly way of managing the content.
与你的同事妥协，让他们使用 Word，但仅限于一组特定的样式，并认真使用这些样式。
最后，您将能够在最终的 HTML 产品中“看到”这些样式，并且可以使用 XSLT 将结果从“噩梦”HTML 转换为非常非常干净的结果。
最后，大部分文本将只是段落和链接。如果您的同事可以坚持有限且一致的格式，您就可以使用您返回的实际格式。
最后，如果您对生成的 HTML 不满意，同样的情况也适用于 DOCX XML 格式。是的，这些文件中有一堆“垃圾”，但其中大部分可以安全地忽略，您只需要标记您希望在文档中使用的特定格式位。
Compromise with your coworkers, and have them use Word, but limited to a specific set of styles, and to use those styles religiously.
In the end, you will be able to "see" those styles in the final HTML product, and you can use XSLT to transform the result from "nightmare" HTML into something far, far cleaner.
In the end, the bulk of the text will be just paragraphs and links. If your coworkers can stick to limited, and consistent formatting, you can tool around the actual formats you get back.
Finally, if you're not happy with the HTML generated, the same applies to the DOCX XML formats. Yes, there's a bunch of "junk" in those files, but the bulk of it can be safely ignored, you just need markers for the specific bits of formatting you wish to use in your documents.
您还可以查看富文本编辑器，例如 CKEditor 或 TinyMCE 并将其设置在内联网环境中，以便他们可以上传内容，并将其格式化为 HTML 并准备好供您使用。您可以轻松地编辑、发布和推送它。
You might also look at a Rich Text Editor like CKEditor or TinyMCE and set it up on an intranet environment so they can upload content and it will be formatted into HTML and ready to go for you. You can edit, publish, and push it live without much trouble.