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.
Let me check with the powers that be, on whether I can stick it on the
corporate samples git. (This might take a few days.)
I have DocBook->Confluence production-ready (we've used it for a couple
years), and Confluence->DocBook largely working but still requiring
hand-tweaking. The main issue with the latter is going back from that
non-nested hierarchy via <h1>, <h2>, etc. to the nested section tagging of
DocBook. It was close enough for what I needed at the time and we're a
fairly time-pressed team so I left it as-is.
On Fri, Feb 7, 2020 at 12:37 AM Chris Despopoulos <
despopoulos_chriss -at- yahoo -dot- com> wrote:
> Hi Helen... Are you able to share the DocBook to Confluence transform
> that you have? It might be interesting to see if we could use that to get
> some content into our WIKI. And also, pull some content out of it... Do a
> reverse transform. If you can do DocBook, then massaging it to DITA
> shouldn't be too hard...
> Thanks cud
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com