The right CMS

Content management systems are recommended for websites with a lot of content or multiple editors. However, the confusing variety makes the selection difficult. We classify the content manager and tell you what is appropriate for what purpose.


Content Management Systems (CMS) go much further than Web editors. While an HTML editor like Frontpage stores finished HTML documents with content and layout in a single "Kuddelmuddel", CM systems separate the individual components. Text, graphics, photos, videos or other multimedia types are carefully placed in a database or other sources, and reassembled as necessary.


This sounds simple and is in practice as well. Using a modern CMS to create a website is hardly more difficult than using Word to create a document. An easy-to-use WYSIWYG editor is usually integrated, plus image processing functions for scaling and editing graphics and photos.


The systems work with templates, that is, finished, unique design templates that the user accesses when working. When a document is retrieved from a server, the templates link content from the sources to a common format-for example, HTML, WML or XML. In this way, CM systems ensure error-free link structures and compliance with corporate design requirements.


As clear as the functional principle of CM systems is, the choice of a program is so difficult. Realized in all possible programming languages, swell or commercial, at prices between zero and several tens of thousands of euro, the CM-starter stands against a confusion of systems.


Something to take one thing and to change to another CMS if not, is not recommended. Once a system is selected, a change is only possible with a great deal of effort, because import and export interfaces are partially defective in CM systems. The webmaster should therefore be as clear as possible about the area of ​​application, the requirements, as well as the configuration and administration effort that he can afford

In many cases the use of a CMS is not worthwhile. For webmasters who upload a few HTML pages only once a week, an editor and FTP client is the more appropriate tool. Especially since the better web editors include tools for site management.


Also for certain Web applications other tools are better than CM systems. If web pages are changed by a lot of employees via a browser and without a hierarchy, Wiki systems are better. This is the case when compiling knowledge bases such as creating glossaries or best practice databases. Wikis like Twiki, Dokuwiki or Mediawiki have the CMS their simplicity, which is noticeable in setup and operation.


The same goes for blogs. While wikis have been invented for the thematic grouping of web content, blogs engage in chronological order. So if you're creating sites with timed content, you should look better at blog systems like WordPress or Blogdesk.


However, a full-blooded CMS is not always the best solution. If you only have a small to medium web site and is responsible for this alone, you often have a desktop-based CMS. It creates and manages the content locally on the PC and then uploads it to the server via FTP.


The transition between web editors such as Frontpage and such offline CMS is fluid, the crucial difference is the template-based orientation of the CMS. As a result, an easy-to-maintain, professional web presence can be realized more easily than with pure editors.


Unlike the server-side programs, the performance can be realized with any webspace that provides FTP access. The work is fast, even with slow servers, most programs are easy to learn and comfortable to use. Very good, because intuitive also for laymen usable, are for example Effective Site Studio and Web to date. Wincontent and BuddyW can also be used effectively after a short training period. OneHandContent offers a small range of functions, but it is very suitable for smaller shows. Many systems such as BuddyW and CityDesk offer free basic versions, which are easy for private use.


Local programs play their limits when implementing complex worfkflows. They can not be realized. Also active website elements, which require server-side scripting languages, such as guest books or shops, are thus usually not possible. Nevertheless, there are exceptions. City-Desk and CMS Encore, for example, offer advanced features that can be implemented with powerful scripting languages.