Drupal
Spip
Typo3
Plone
CMS data is stored in a dynamic database. This data externalization helps to improve the editing process and provides a unique source of data. Thus, multiple pages can display the same data and only the database has to be edited in order to update every page.
Web pages display is driven by templates, which are structure files. They are a kind of containers which support data (content). Those templates control the positioning of each element on the page and the insertion of content by following preset rules : content age, type, or weight. One template can control either the whole display of a Website, or only a part of it (section or sub-section).
An administration interface eases content updating. Website architecture can be modified, and new sections created, renamed or re-positioned. Content can be edited to add text, links, or images. Content can also be formatted : text can be highlighted in italics, in boldface, or underlined. The main benefit is the ease with which it is possible to update Website content : it is not necessary to know any programming language, and the Web interface can be potentially be accessed from anywhere.
With a CMS,
it is possible to set up a scheme that allows constant
and automated updating of syndication files from Website
data.
To know
more about syndication, see : Web standardization
Globally, three user levels of a dynamic Website can be distinguished, each having a different function :
It is thus possible to set up more or less complex organisational schemes, for example : an editor creates a page and submits it to administrators who will evaluate this content before it is published (spelling, size, color, etc.) and then validate it.
CMS can handle data organization at different levels. It is thus possible to create an organizational model by language. A link can then be made between translations in order to improve translation process.
Some CMS allows content versioning, which means maintaining a history of content revisions. When a page is modified and updated, the previous version is automatically filed. This makes it possible not only to view past versions and to recover related data, such as : its author, creation date, etc., but also to restore content to the way it was at a given time.
The following table offers a quick comparison of some of the features of different CMS we use and suggest to our customers based on the mandate we are entrusted to accomplish.
| Plone | Spip | Typo3 | Drupal | |
|---|---|---|---|---|
| Web server | Apache, IIS, built-in | Apache, IIS | Apache, IIS | Apache, IIS |
| Framework | Python | PHP | PHP | PHP |
| Database | MySQL, PostgreSQL, Oracle, SQLServer, built-in | MySQL | MySQL | MySQL, PostgreSQL |
| User authentication | LDAP, SMB, ActiveDirectory, built-in | MySQL, LDAP (limited) | MySQL, Active Directory, Novell e-directory, Oracle, MS-SQL Server, Sybase | MySQL, LDAP, External 1 |
| User roles | X | X (static) | X | X |
| Workflow | X | X | X | - |
| Caching | X | X | X | X |
| Search engine | - | X | X | X |
| Poll | - | X | - | X |
| Membership | - | X | X | - |
| Security level | *** | ** | ** | * |
Drupal : http://drupal.org
Spip :
http://www.spip.net
Typo3 : http://www.typo3.com
Plone : http://plone.org
[1] external authentication modules : Jabber, Blogger, LiveJournal or another Drupal website