|
|
|
|
|
by MilStdJunkie
1225 days ago
|
|
If it's got exposure, complex document requirements will always go for Asciidoc over Markdown. Hell, it's got transclusion and conditionals, Asciidoc satisfies the requirements for most DITA systems. The trick is whether or not people know about Asciidoc, and of course, whether they're allowed to go for a Git+LML stack over a vendor stack. That last one can be a pretty big deal, as it involves swallowing a fair amount of liability. No one wants to spend the extra cash on writers who know how to git, they'd rather get late middle age chair warmers who've been suckling down a TW2 salary their entire professional life. Leadership would rather leave the tech stuff outside the org. The trick here is that most of these XML pubs vendors couldn't give ten strained s##ts for liability, and they disappear on pubs teams with depressing regularity. Usually right before some big contract deliverable. How's your low risk option looking now? |
|