Home » Products » Publicus » Introduction
Last modified: April 11. 2002 12:42PM
|Publicus integrates with content creation systems from a number of vendors, including (but not limited to):
- CCI: Users of the CCI NewsDeskT system can export text for automatic publication in Publicus.
- DTI: Newspapers using past and present releases of DTI's editorial pagination system can automatically publish content to Publicus.
- Microsoft WordT-based systems: Word and RTF files* can be imported from the large number of editorial systems that use Microsoft's word processor.
- Modulo Systems: Users of the Quark Publishing System can save .XTG formatted text for automatic publication using Publicus.
- SAXoTECH: Seamless, two-way integration with the SAXoPRESS Content Management System and the SAXoPRESS NetNews Module.
* Requires the use of pre-defined style sheets.
Create and edit content for the Internet without any knowledge of HTML
Publicus is often used as a Web production "back-end" system for publishing content on the Internet. The system can be used as a stand-alone content management solution, but more often it is employed as an output system integrated with a publisher's legacy content creation systems. In this way, Publicus can be implemented more easily and inexpensively into your existing organization.
Because Publicus separates the content creation (writing and editing) from the presentation (HTML templates), your staff can use your existing editing systems and workflow to create content for online publication.
Publicus can be integrated with just about any legacy system. Through its import filters, Publicus can accept content in 150 different formats, including ASCII text, HTML, XML, RTF1, XTags and Microsoft WordT 1.
Your content systems will be set up to automatically feed content to Publicus, which will store the content based on the information found in the content files. That information tells Publicus where to place the story on the site, how to prioritize the content, when to start publishing it and which other stories are related.
In addition to text, Publicus can receive other media files, including images, audio and video. And if these files are "tagged" properly, the system can automatically store and relate them to other content elements.
Once the content has been received by Publicus, online editors can use the Windows 2000T client software, or a simple Web browser interface to edit and approve content for publication. Access to the database is strictly controlled through several layers of security.
In the browser interface, editors have access to all the content and may modify the header data, thereby changing how the story will be presented, where it will appear on the site and when it will be published.
Based on that header data, Publicus will select and apply a pre-defined template to the content for presentation in the Web browser. If the story has an attached image (or images), it will be placed in the spot reserved for it in the template and sized accordingly.
If an editor has approved the story, on its assigned publication date it will automatically become viewable on the Web site.
It will also automatically be added to the index pages and links to and from it will be created by the system. On its expiration date, all traces of it will be removed automatically.
A template's behavior is automated to a large extent. This means that the system adjusts the template's size and appearance based on the content provided. For example, if an attached image is a very long vertical, the template will know how to best deal with that.
It is also possible to select different templates for the home page, based on the amount of content available, or insert automatic controls that shift in and out depending on the day of the week.
For example, if a major news event occurs, a template can be selected that will present one large story on the front page. And on weekends, when the office is short-staffed, a template that shows a few items, as well as content from wire services, can be automatically substituted by Publicus.