Thanks, Ajay, for your answer. That bit I am ok with. What I really want to do is make my documentation multi-channel. I want to publish the manual to PDF (existing functionality) but also use its parts as KB in the Service Desk. I already have a KB and a couple of articles but I want to maintain the one document set.
Thank you for your reply.
I'm not sure if you've been able to progress on this matter but I just wanted to point you in the direction of our apps Scroll Viewport and Scroll PDF Exporter for Confluence Cloud. Both might be interesting to you as they allow you to maintain one document set and then share that with your users in a multi-channel way: one delivers your Confluence content to a public help center which can also integrate with your JSD support system, the other delivers your content to PDFs that you can customise and style in lots of different ways (you can also configure templates).
We're also currently working on extending these capabilities to fully meet the needs of teams who keep their technical documentation in Confluence. If you'd like to learn more about our existing apps or see some of our early concepts for versioning, content re-use or variants management for technical documentation, I'm more than happy to chat: email@example.com
Hey there, folks! For most of us, the past six months- yes, you read that right- have been a journey. More people than ever before have pivoted to working remotely, and navigating being on-scre...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events