How do I expose product documentation to customers in wiki format?

[Bryant Eadon]

All documentation we provide today is in PDF.  I want to convert this into wiki and arrange it in such a way that customers have the ability to suggest edits to our documentation.  I don't want to have customers change the documentation directly and with immediate effect, I want documentation and development teams to get a JIRA ticket to incorporate this into the documentation wiki when it's raised.

These customer requests could be along the lines of : "this section is too confusing" , or legitimate issues with the documentation that may be incorrect, but needs review by support teams/development to enhance documentation.

Can confluence handle this ?

[Nic Brough [Adaptavist]]

You're going to need to find or write something that can de-construct a pdf and convert it into a format suitable for import into Confluence.

Once you've got it in, then you can control who can edit the pages with space permissions and restrictions.  A typical use case would be allow the customers to comment on pages, but not edit.  On the JIRA side, you could use an issue collector instead of allowing customers to comment directly - that allows you to gather requests and changes without having to monitor pages for comments.

[Milo Grika]

If you have Acrobat (not just Reader), you can save a PDF as a Word doc and then import it into Confluence.