Frequently Asked Questions about Quanta CMS


Is Quanta a Framework or a CMS?


To answer this, we should first of all clarify the difference between a Framework and a CMS, as - even between developers - there seems to be lots of confusion around the two definitions. 

Frameworks are built for programmers who could code new applications from scratch. A framework provides sets of tools and packages (classes, methods, connectors, etc.) helping developers in doing things faster and better.

Building a project using "Vanilla" PHP (or any other language) is always possible, but it takes hours, or days, or weeks, to re-create what a Framework provides out of the box.

Essentially, a Framework removes the need to re-invent the wheel, where the only price to pay is - you are going to its tools as your starting point. 

On the other side, a CMS is usually built over a Framework. So a CMS is not an alternative to a Framework, but an implementation providing further tools and pre-set functionalities for managing web content. A typical CMS defines several categories of content (text, media etc.), allowing an user to enter, edit and manage the content since the installation is complete, through a simple user interface, that is always expandable.  Wiki software can be considered to be a specific type of CMS, usually an open CMS encouraging just about anyone to create content.

Quanta is a Framework thought for developers, and offering amazing content management features (i.e. Wysiwyg, overlay input forms, multiple file upload, workflow management, etc.) out of the box.

This could potentially place Quanta in the ambiguous Content Management Framework (CMF) right on the thin line dividing the two realms.