 |
|
Content Management Solutions
Key Features: Topical Structure and Informal Content Types
A Uniquely Structured, Topic-based Approach
Pervasent CMS stores content in a uniquely structured way. In our system, content is not simply a list of assets, such as files and images, but is instead a collection of "elements." For example, the elements of a news article could include a headline, byline, abstract, body and photo. Elements can also be arbitrary tags, such as subject and category, which can be leveraged by search engines.
Comparing Approaches: Pervasent Interwoven Content is database-driven Content is file-based Content is organized by topics Content is organized by directories Can set up run-time presentation rules to leverage content properties, e.g. go-live and expiration dates Need to develop custom code to make use of manually inserted meta tags to control presentation Page templates are built using our template editor or Java/JHTML/HTML Page templates are built in PERL Content item dependencies are automatically tracked Content item dependencies must be manually tracked Pervasent's topic-based approach provides real-world benefits that file-based systems can't deliver. Using Pervasent's CMS, website content can be decomposed in a much more granular way than with file-based systems, e.g. a single "blurb" or testimonial quote.
This content is organized logically by user-definable "topic" folders, not directories, offering a more intuitive and flexible way to view data than file systems provide. On the same screen where content is entered, users can easily assign one or more topics to content. A single piece of content can be placed under any number of topics.
Because content is stored logically, it never has to be replicated to be reused. Change text, a headline, a link or an image in one location, and it's changed everywhere on the site.
Topic-based Deployment
Content is deployed to the web by topic with all the underlying assets (images, media files) automatically deployed regardless of asset location.
The Pervasent CMS understands the dependencies between content items. Content cannot be deployed unless all associated content items are available, eliminating website errors such as broken images.
With a topic-based approach, a user has maximum flexibility on how to publish content. For example, a user can choose to publish all "XYZ" articles or list all links regarding "XYZ."
Informal Content Types
One of the strengths of the Pervasent CMS is "informal content types." This feature allows non-technical users to create custom content entry forms for their content creators.
Users set up their own informal content types and define the unique elements for that type. For example, an informal content type "product alert" could be created with elements such as product type, description and date. Another informal type, e.g. "bug fix," could be defined with all the elements of "product alert," but adding elements for patch location and install notes.
As another example, under the informal type "music file," a user could create elements for "Windows Media Player" and "Real Player" or "small," "medium," and "large" to organize content by application use.
Templates Leverage Informal Types
A template is a framework containing the layout data and rules used to render a web page. Templates determine what content is published to the web and how it appears.
With Pervasent CMS, a template’s business rules can determine how to present content based on content type. Using the informal type example above, a template could decide the type of music file to publish based on the media player available on a visitor’s computer.
Template Editor
Templates are the key to the separation of presentation and content. By applying new templates, the look and feel of a web site can be easily modified without touching the content. Pervasent’s templates are “format neutral” so they can output to any page format, including JHTML, XHTML, ASP and JSP pages.
Pervasent includes a built-in editor to assist in creating and modifying templates. Any existing web page can be imported into the template editor, including HTML, ASP, JSP and JHTML pages. Users can then “point and click” on the page’s text and other content items, replacing each item with a content reference in order to “templatize” the page.