Being a cloud-based authoring and hosting platform, one of Infinity’s most significant plus points is quick updates and instant publishing.
Let’s consider two scenarios:
- You just completed work on a release and published the output, but then you notice there’s a missing period (full stop), incorrect version number, or any other trivial change which you cannot ignore.
- You may need to delete a few sections instantaneously. These sections may sometimes consist of a large number of topics (1000+).
Scenario 2 could be rare, but scenario 1 is a common occurrence during a release. In an on-premise/offline tool workflow, you’ll have to traverse through multiple steps just for making that trivial change:
Update content > Make local build > Verify the output > Publish the help on a web server.
There’s also a separate step to upload the updated source files to a VCS such as SVN, Perforce, GitHub, or others.
Infinity proves to be a big time-saver and comfort in this case for two reasons:
- Being database-driven, Infinity works at a topic level. You update and publish individual topics instead of creating an entire help build (sometimes consisting of 100s of topics) just for making that trivial change.
- Infinity has built-in version control and publishing options – instant or scheduled publishing.
With Infinity, you need to perform only two steps: Update > Publish.
Examples of on-premises/offline tool workflows are:
- An offline help authoring tool with a separate web server for hosting the output and a separate version control system.
- A docs-as-code setup with a separate text editor, a separate version control system, a static site generator, and a web server to host the html output.
Infinity doesn’t require so many individual components. It provides all the above-mentioned tools built-in as a single solution.