TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Developments in the review cycle From:Ryan Young <ryangyoung -at- gmail -dot- com> To:Robert Lauriston <robert -at- lauriston -dot- com> Date:Wed, 6 Apr 2016 15:40:42 -0700
Interesting. Why is it like rolling back the clock? I know Markdown doesn't
support finer-grained elements, but you can use XHTML elements in Markdown
as a supplement. That said, some people have made a good argument for rST
instead: http://ericholscher.com/blog/2016/mar/15/dont-use-markdown-for-technical-docs/
Using Git and Markdown is still good for collaboration: developers would
largely rather stick with their tools (Git/text editor or IDE/command line)
than something even as easy as Confluence. It might be a drawback for other
contributors.
If you use your 10-user Confluence scheme, the price point comparison is
true. If you have to work with a Confluence instance that has over 50
users, though, they start to equal out (if you get the desktop Prince
licenses, which we did).
On Wed, Apr 6, 2016 at 2:48 PM, Robert Lauriston <robert -at- lauriston -dot- com>
wrote:
>
>
> Switching from XHTML source in Confluence to Markdown in files seems
> like rolling back the clock five years, unless there's a wiki that
> uses Markdown source. And even then, Prince is way more expensive than
> Scroll PDF Exporter.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com