tome.host is a SaaS ("software as a service") designed to simplify the process of creating and maintaining technical manuals, user guides and other structured documentation.
Within our system, we call these documents 'tomes'.
Unlike traditional content management systems, data in a tome is structured in sections, which can be nested to any number of levels, rather than pages.
Multiple authors can collaborate on tomes, with a permissions system preventing multiple users from overwriting each other's work.
Selected changes, or all changes, can be published to the public version with a couple of clicks.
The simplicity of the system and collaboration features mean that developers can work on documentation for features concurrently with coding them, reducing the time and cost required for finished documentation to support a software release.
tome.host is essentially software which runs on the web. This means it can be used by anyone with access to a modern web browser (Chrome, Edge, Firefox, Safari, IE 10+). It's responsive, which means that the page layout will reformat on smaller screens like mobile phones or tablets, to make it easier to use.
SaaS requires no special hardware, software, infrastructure or IT expertise - all of these are handled by the platform subscription.
Most organizations still deploy documentation in paper versions, or electronic files like World documents or PDFs.
tome.host has a number of advantages over these more traditional methods:
tome.host has three sets of content - draft, public and archive.
Content is created in the draft area, and when sections are ready, they can be selected and published. They will then appear on the public version. The draft screen has a grey background.
Only logged in users with permissions can see the draft version of content.
The public view has a white background. It can be seen by the public without logging in. Logged in users can switch between the published and draft content using the tabs to the top right.
Whenever new content is published, any existing content which is to be replaced will be moved to the archive. At present this cannot be viewed or accessed, but in future there will be methods available to view the history of changes, view content snapshots by date and restore content (rollback).