Whether using a CMS without a database is worthwhile for your own project depends on a range of different factors. The advantages, as well as the typical problems of non-database CMSs, are summarised here:
+ CMSs without databases are usually quite plain and are limited to the most essential features and therefore users don’t need much of a familiarisation period.
+ Web project backups are easily taken care of since no complex database backup is required, so data just needs to be downloaded from the webspace.
+ The direct transfer of information without having to detour over a database means there is a shorter loading time and faster access to the web project.
+ A small CMS system generally doesn’t require much webspace and doesn’t demand any special requirements from the hardware.
As well as numerous advantages there are also some disadvantages of CMSs without databases:
- The possibilities of non-database CMS systems are limited, which is why the systems are best suited to smaller projects with minimal static sites. Dynamic websites cannot be created without databases.
- Since simple CMS systems usually only offer small communities, the user is often left alone with questions and problems and has to sort through documents to work it out themselves.
- The often unavailable codes and minimal distribution of CMS software can mean that the simple CMS becomes boring for the user since there is less chance of development.
- Not working in a structured and neat manner on a simple content management system could make it difficult to find specific content again.