Clarification on Drupal 8 and Backdrop.
Drupal 8, the last version in development, is causing a small internal war that it is causing the fist fork of Drupal.
And if the updates of the software projects are never easy for do, if the update is radical and the project is huge, the problems are guaranteed, mainly thinking that Drupal 8 is not an evolution of Drupal 7, being really a radical revolution where most of the project was rewritten. Drupal 8 requiere PHP 5.3, add the famous components of Symfony and get a lot of good modern practices of web development. The result is a code more professional and modern, but too more difficult of develop if you don’t have advanced knowledge of programming.
The problem is that a lot of people think that these change are too and they have decided to balk. This is the reason that some weeks ago, it born the project Backdrop CMS, the first fork of Drupal developed for people that don’t like the new Drupal (more info here: http://www.backdropcms.org ).
The expected audience of Backdrop is those amateur developers that are not happy with the new version of Drupal, a tool too complex to use, and could switch to WordPress (the most direct rival of Drupal). In a simple chart explains these assumptions, where supposedly professional developers will opt more by Drupal 8 and amateur developers mostly used in Backdrop:
For its part, the goals pursued in this project are summarized in 7 points:
- Appeal to existing Drupal 6 and 7 Developers: We will deliver modern features (configuration management, content listings, rich-text editing, etc.) on a traditional Drupal-based architecture.
- Maintain an Easy-to-understand Architecture: We will make sure that new developers can understand the basics of the Backdrop architecture (info files, hooks, and callbacks) with minimal effort. An hour should be enough to summarize the architecture.
- Keep APIs Stable (“Major” versions): We will make the upgrade process easier on end-users by maintaining slower-moving core APIs.
- Deliver New Features Often (“Minor” versions): We will deliver new features at regular intervals with minimal risk of API breakage.
- Ensure Great Performance: We will focus on direct implementations and speed rather than accounting for edge-cases through abstraction.
- Provide a Better End-User Experience: We will constantly be improving the editorial and site-building experience. The intial release aims to improve content creation (matching Drupal 8′s advancements), and deliver a universal layout manager for site-builders (replacing blocks).
- Grow the community: We will focus on attracting new developers at all points of the spectrum, but especially remembering the entry-level developer.
The CMS in PHP more used and required since several perspectives.
Not everything is Drupal in the world of CMS. In fact, since Google Trend place WordPress above Drupal and Joomla. Possibly because WordPress is a CMS not only for developers, but a portal where people create blogs (the page you are reading belongs to wordpress: http://josemmsimo.wordpress.com ).
However, actually Drupal CMS is the most demanding professional by software development companies (at least in the UK, where I have been working this past year). According with ITJobsWatch (web with statistics and trends in the IT sector in UK), it verify that CMS Drupal is the most requested, followed by WordPress (both written in PHP). Joomla (also written in PHP) is less used (more details at: http://www.itjobswatch.co.uk/jobs/uk/cms.do ).
To finish, I made a small graphic considering the number of job vacancies in UK that are required, comparing the 3 CMS: Joomla, WordPress and Drupal. Note that there are jobs in which demand knowledge of several of these CMS, and also that the analysis is performed on only 2 or 3 job portals in that country. Therefore, this is just a small guide to reality:
About the salaries, in that web indicate that with Drupal is where the people win more money (some more of 40K pounds per year) if you compare with WordPress (34K pounds) and Joomla (some more of 32K pounds).
Differences between these 3 CMS:
There are websites which do a great job at the time of purchase between these 3 CMS. Here there are some links that I consider relevant, and too there is an infographic very interesting: