Get Started: Publish

Publish in-app guidance with the same attention to quality that you do with your entire application.

Rollback with Revisions

Each time you make an update to your content, a revision is saved. Browse to a single topic on your site, and view the Revisions available for that topic. You can export and import your previous versions.

Use Releases for QA & Testing

You can save a state of your revision by making a version of that topic.

We've borrowed from software development terminology, which might be familiar to you if you're involved in QA testing your applications.

  • Production environment is where your visitors are using your application. This is sometimes called the Live environment.
  • Staging environment is where you are testing your improvements.
  • Head is the latest version. Head is where you'd be currently working on changes and improvements, for example in a staging environment.
  • Releases are usually numbered versions of, in this case, topics or content.

Note: You would need a site for each environment. Having a site per environment in Inline Manual means you will have a unique install code for each of your Staging and Production Environments.

Imagine e a case where you have a walkthrough working perfectly on your current Production Environment, and that is saved as 'Version 1.0.' Next week, there's a change coming to your application which means that steps in your walkthrough won't be needed

You can test the latest HEAD version of your existing walkthrough on a Staging Environment, where you can see the planned changed. When everything looks ready, you can mark that as 'Version 2.0.'

When your new application releases to your Live Environment, you log in to Inline Manual, and change the walkthrough from 'Version 1.0' to 'Version 2.0.'

Was this article helpful?