SiberSafe enables publication of the same content to different media. For example, the user can opt to simultaneously publish a document to HTML, PDF, RTF, HTML Help and CHM Help. Because SiberSafe tracks all the elements required to publish a document, the user need only specify the document to be published. SiberSafe will assemble all the required components from the repository and transform them using the required publication driver.
SiberSafe incorporates both open source and custom transformations to enable teams authoring XML documents using the DocBook DTD to publish to PDF, RTF, HTML, HTML Help, and CHM Help. Published documents can be either stored in the repository or emailed to the requesting user, with multi-file publication results being zipped up prior to emailing.
Via SiberSafe's DITA Open Toolkit integration, users can now easily publish specialized or regular DITA content into formats such as PDF, Word, RTF, HTML, HTML DocSet, JavaHelp, HTML Help, Powerpoint slides, and more. A single server-side DITA Open Toolkit installation delivers the benefits of single-source publishing to all SiberSafe users with no new software required on their own local machines.
SiberSafe lets you specify your own XSLT script to apply to an XML document. The resulting file can be published to a different stream where it could be made available to a different group, or deployed to an external server.
SiberSafe publication drivers automate document assembly based on query templates and parameter files that specify the criteria to be used when executing the queries. Users can assemble documents by executing queries, sorting the result based on the specified sort criteria, and applying the formatting transformations required. For example, if the Document Assembly Driver is used to produce an alphabetically-sorted list of product features, new features will be included in the right location every time a new list is published. The Document Assembly Driver uses the same document templates as the Document Builder, with the parameter file specifying the selection criteria rather than the user.
Users can publish their documents "on the fly" without creating a new publication group, via one of the partially-defined publication groups that exist in the stream. These groups specify a publication target format, and their publication source is dynamically selected.
SiberSafe includes a configurable FrameMaker publication driver that allows XML documents to be published to PDF using all the features of FrameMaker. The standard SiberSafe Publication Driver interface allows the document administrator to use existing Frame documents as templates for publishing XML content. Each XML content type can be published using a different Frame document as its template.
SiberSafe's content deployment component, SiberStage, enables administrators to move content from the repository to external servers, either web servers or build systems.
SiberStage is designed to allow web developers to deploy changes to a web site from a central location. It is fully configurable and runs on any client that supports Java applications.
A SiberStage client can periodically check with the repository to see if any files have changed in the development stream, extract any changed files and process them according to the SiberStage client configuration - for example, it could launch an XSL translation to convert the XML files to HTML, and place all deployed files in the file system, available for access via the web or application server. The client can also handle all the server restarts, registry updates, etc. associated with deploying application components.
The SiberSafe Knowledge Base Publisher enables training teams to use and reference content created for technical manuals and help files. Teams can generate self paced training courses, learning objects optionally published as SCORM learning objects, and hyperlinked training books published as an interactive training course or a PDF.
Once published, the knowledge base can be distributed for use online or via CD-ROM with its convenient, royalty-free Viewer.
The Knowledge Base Indexer address specification uses XPath expressions to selectively include/exclude elements to/from a particular address in the full-text knowledge base index.
To view a knowledge base on CD-ROM, a servlet-based knowledge base viewer is automatically launch before the system browser.
Either random or user-specified file name prefixes can be generated for publication results. This enables teams to integrate SiberSafe knowledge bases with in-house content management systems that require files to have unique names regardless of the folder in which they are located.
