Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

What is the average cost of software for DITA authoring?

+1
−0

I'm looking to buy some software for technical document authoring with DITA. The tech writing group will have at least 5-10 users, writing 100-pages long documents for several products in various languages, sharing a moderate amount of content between documents, and requiring professional styling.

What is the average pricing of state-of-the-art software for this technology? What cost per user can I expect, and is it better to go for on-site single-payment license or a SaaS solution? We're trying to assess whether moving to this kind of solution is makes sense from a budget point for a department this size, and pragmatic information of the actual costs involved is woefully difficult to get without prior experience.

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

This post was sourced from https://writers.stackexchange.com/q/14684. It is licensed under CC BY-SA 3.0.

0 comment threads

1 answer

+0
−0

DITA is an XML format, so any editor or IDE that supports XML will work for you. Options with good XML support range from Eclipse (free) to Oxygen and Epic (several hundred dollars per seat). Of course, anybody who's comfortable getting up close and personal with the XML can use Emacs, vim, or Notepad++, too. (Don't laugh; I write all my XML and HTML in Emacs.)

Aside: MadCap Flare has some support for DITA, but it's not a complete solution. I use Flare for HTML projects and find it a good tool, but for DITA I would look elsewhere.

If you have several writers working on the same document suite, I hope you are already using source control. If you aren't, you should factor in those costs. Source control can be free (git) or not (svn, Perforce). If source control is already being used in-house, try to leverage that.

Doc tools and source-control products are frequently offered with both per-seat and enterprise licenses. The pricing break-even points vary, so you'll need to evaluate those options individually once you've decided on a tool set.

Finally, if you are setting up source control or a build system (to produce published docs from the DITA source) for the first time, you'll need to factor in the cost in someone's time to set that up and administer it. On the other hand, you'll no longer lose so much time to the costs of "informal" management -- someone has the document on the shared drive open so you can't edit it now, or two different people made conflicting edits to their own copies of a document, etc.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »