The argument is a full blown CMS should somehow be able to grant and deny create/read/update/delete access and permissions to users.

Whilst they do let you manage your content they aren’t full blown as they don’t let you authentication/authorization. Some people will argue that these flat-file CMS systems aren’t real content management systems.

There are certain advantages of not using a database like:Īre they “CMS–Like Systems”, shouldn’t they be called “Content Publishing Systems”? There are several ways to populate and parse content, xml and markdown being the most popular. The flat-file system generates dynamic pages and each blog post or page is simply in a folder of its own (depending on the system and how you structure it). This means you don’t have to query any database of any kind in your system -there is no database. Without a database the flat-file CMS stores content in files and folders unlike a traditional database. We’re not talking about static site generators here, text of XML driven file CMS’s. We respect Wordpress and it will always be there, this small project simply aims to give people out there a chance to work with Flat File CMS’s also known as file–based CMS’s. Lot’s of these features aren’t needed by folk who merely want to blog without the bloat.

Wordpress was built as a simple blogging platform and has evolved over the years into a feature rich CMS. Lot’s of folks are leaving Wordpress for a flat file CMS system with no database.

Php flat file add, edit delete