Is your question: You are developing a desktop/web/mobile application that should link to pages in Confluence based on the context of the link?
If that's the case, then there's no built-in mechanism to handle this, nor is there any step-by-step set of instructions. You basically add links in your app to pages on your Confluence implemenation.
However, there are strategies you can employ to make sure this works well. One such strategy, that I use, is to use the web server front-end as a "map" of help links to Confluence pages (currently we do this with URLrewrite, but there are other ways). I replace the links in the app with "GO URLs", and map those GO URLs to actual pages in Confluence. That way, if the page name changes, or if we upgrade to a newer version and the version number in the path changes, I can update the links in once place and not require the app to be rebuilt.
Here's an example.
Our SDK installer includes a readme file that links to a page with additional installation information:
http://devcenter.verivo.com/display/doc/5.+Install+an+Akula+License
In the release notes, the URL is something like this:
http://devcenter.verivo.com/go/1.0/online_activation
When the page name changes (if it changes), or if we add version 2.0 (and subsequently change the 1.0 URL to /display/1.0/5.+Install..., then I can add a new GO URL for the older content and update it without changing the SDK.
hth,
matt
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.