Over the last few months, we have looked at content management in general and at the open-source Plone content management system (CMS) in particular. Plone certainly is a capable CMS, one that people can use almost immediately upon installation. The main advantage of Plone is its simplicity—it's easy to install, easy to use and easy to customize.
But customizing Plone, or any CMS, can go only so far. If you dislike Plone's boxy look, you undoubtedly can change it in favor of a different model. But if you want a completely different workflow than the one Plone provides, it probably is a waste of time and effort to try to make that sort of change. Rather, it makes sense to write your own CMS or customize one that is designed to be flexible (if more complex) in this area.
Indeed, most CMS vendors recognize that their products need to be customizable if they are going to be useful. If you buy a J2EE-based CMS—and a large percentage of commercial CMS offerings are based on J2EE—you can expect to be able to write new Java objects that describe your content and the way it is published. At a certain point, the division between customizing a CMS and writing your own CMS on an existing infrastructure becomes somewhat blurry.
Enter Zope's content management framework (CMF), designed to provide enough infrastructure for you to create your own CMS. Because Zope development is fairly quick and easy, and because you can use the existing infrastructure that Zope provides, it should be possible to create a CMS at least as quickly (and far more cheaply) than would be possible using a commercial CMS implementation. Plone is implemented on top of CMF, rather than on its own, meaning each time CMF is improved, Plone benefits from those changes.
This month we look at CMF, which is becoming the central focus of the Zope application server. Indeed, although the latest stable version of CMF is 1.3.1, an alpha version of CMF 2.0 is now available. And, if Zope's future directions were any mystery before now, it is clear that CMF 2.0 is “a lightly repackaged head checkout of Zope3”.
We covered how to install CMF several months ago [see At the Forge, LJ, May 2003], so I won't go into detail here. In short, download the latest version from cmf.zope.org and unpack the tarfile into lib/python/Products under your Zope home directory. Then, make symbolic links from the Products directory into the CMF directory for CMFCore, CMFDefault, CMFTopic and CMFCalendar. Restart Zope, and you should see a number of CMF-related products appear in the Add menu within the Zope management screen.
Before we can create any CMF objects, we first need to create a container in which our CMF site can exist. You might notice an obvious parallel here between creating a Plone site and a CMF site. To create a new CMF site, simply choose CMF Site from the Add menu in the web-based Zope management interface. You are asked to name the CMF site, as well as to provide a description.
When you create a CMF site, you also are asked if you want a new user folder within that CMF site or if you want to use an existing user folder. For now, use the existing user folder, meaning that users defined within the top-level Zope site are users within the CMF site. If you prefer to make your CMF site a self-contained unit, without reference (except for the site owner) to the outside world, you may want to create your own user folder.
When you have finished creating your CMF site, you are taken to the home page, which tells you to visit the basic configuration form. Because the CMF originally was known as the Portal Toolkit (PTK), many of the screens refer to portals rather than CMF sites. The information you enter in this form is fairly general in nature, allowing you to set, for example, the e-mail addresses from which generated e-mail appears to come as well as the site's SMTP server.
Things get much more interesting if you follow the directions and go to the CMF management interface, which is really the Zope management interface for the CMF site. In other words, if your CMF site is known as /cmfdemo, you can look at the contents of the site with /cmfdemo/manage. The management screen, as usual in Zope, consists of a small navigation bar on the left. But, as we saw last month, the left side contains a number of portal tools, allowing us to configure and modify our CMF site.
Clicking on portal catalog reveals a vocabulary, Zope's term for an index, that explains how CMF sites are able to provide full-text search without any effort from the site administrator. Clicking on portal types reveals a list of content object classes. These classes form the core of CMF. We look at the content types in greater detail below and will examine how to create our own content types next month.
Finally, click on portal_workflow, which allows you to enter the title of the workflow object you would like to use for each content type. Workflow describes how content moves from writing to publishing, ensuring that only appropriate people are given the authority to perform certain tasks. Authors may write stories, for example, but be unable to publish them to the site. A good workflow system allows you to customize these rules to reflect your organization's needs.
- Considering Legacy UNIX/Linux Issues
- [<Megashare>] Watch Mrs Brown's Boys Movie Online Full Movie HD 2014
- Memory Ordering in Modern Microprocessors, Part I
- Cluetrain at Fifteen
- New Products
- RSS Feeds
- Python Scripts as a Replacement for Bash Utility Scripts
- Getting Good Vibrations with Linux
- Security Hardening with Ansible
- diff -u: What's New in Kernel Development