[Framers] I'm pretty sure the answer is structured content with DITA but I'll ask anyway

I worked in an environment that sounds somewhat similar to your's for a few years. I produced "comprehensive" Release Letters that sometimes reached 300 pages. Each new feature was discussed in its entirety and I was also the lone writer. I argued against that approach, but I did not win that

Re: [Framers] I'm pretty sure the answer is structured content with DITA but I'll ask anyway (LONG)

Take a look at Paligo. It gives you structured authoring (DocBook), a CMS, and reuse in a single package without having to hire a developer to build a custom system. On Tue, Jul 26, 2016 at 3:20 PM, Pat Christenson wrote: > I'm the only tech writer in my group.

[Framers] I'm pretty sure the answer is structured content with DITA but I'll ask anyway (LONG)

I'm the only tech writer in my group. Everyone else is a trainer/presenter (although they do quite a bit of writing). Our software has numerous components, each on its own release track. At the end of each month, I post extensive release notes on EVERYTHING from the month (written in