Scroll and Context sensitive help
My team and I have been looking into context sensitive help.
We cannot find the process for generating and maintaining the mapping file ANYWHERE.
Is this process documented? Are there best practices we can follow?
We run Scroll viewport, Versions, Runtime, Report Publishing endpoint, platform, and PDF & HTML Exporter on server/data center versions of confluence.
Additionally, any feedback regarding scale of the mapping file is appreciated. We will have over 100 spaces potentially looking to make this transition.
Thanks for reaching out to us. In order to further support you can you provide some additional information in relation to the mapping file that you're referring to? How does this work / what were you trying to achieve?
When using Scroll Versions alongside Scroll HTML Exporter, you can define unique page keys for each Confluence page within your documentation space. When exporting these pages managed by Scroll Versions, you can choose to have file names containing those page keys. This allows you to provide your online help resources with links that remain stable even when changing the Confluence page title. You can read more about this process here: https://help.k15t.com/scroll-html-exporter/using-the-scroll-versions-page-key-functionality-for-context-sensitive-help-90407415.html
Does this help?
Thanks, Thomas (K15t)
Please sign in to leave a comment.