Download - CMS Evaluation with test implementations
CMS Evaluation with test implementations
TYPO3 Camp Berlin 2015
Drupal – Contao – Joomla! – Wordpress – TYPO3 – Neos
Gernot Schulmeister | [email protected] 20.06.2015 Seite 2wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
Gernot Schulmeister… Lives in Mönchengladbach… Developes websites with TYPO3 since Version 3.7
(2005)… Works for wfp:2 … Has a migration background and comes from
Southeast-Europe (Austria)… Likes operative CMS evaluations
Contact• facebook.com/gernot.schulmeister• twitter.com/mistakanista1
Gernot Schulmeister | [email protected] 20.06.2015 Seite 5wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
Order of implementation
• Drupal• Contao• Joomla!• Wordpress• TYPO3 • Neos
Gernot Schulmeister | [email protected] 20.06.2015 Seite 6wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
Features• Main-, sub-, breadcrumb-, language and metamenu • News• Special content elements• Contact form• Header images• Slideshow on the homepage• Search• Lightbox• Sitemap
Gernot Schulmeister | [email protected] 20.06.2015 Seite 8wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
Motivation• I wanted to test Neos• I wanted to know something about other CMS• I had to write a master thesis• TYPO3 loses market share• CMS evaluation is a big topic• I did not find any information about tests like this• Achieve knowledge on how to get started with other
CMS• Learn from other CMS
Gernot Schulmeister | [email protected] 20.06.2015 Seite 10wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
Proceeding
Gernot Schulmeister | [email protected] 20.06.2015 Seite 11wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
Criteria catalogueImplementation of the frontend (14 criteria)• Main part of the evaluation• Effort and usability of the solution is analysed
seperatelyCMS functionality (8 criteria)• Usually main part of other CMS evaluationsDeveloping and developer profile (5 criteria)• Personal, subjective conditions of the
implementations
Gernot Schulmeister | [email protected] 20.06.2015 Seite 12wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
• Create an order of the results• Key of points: 6-5-4-3-2-1 point• No CMS can have equal points• Time effort is easy to evaluate• Arguments for evaluating the usability have to be
found• Intensive work with the results necessary• Difficult to enlarge the methodology to additional
CMS
Evaluation methodology: Ranking
Gernot Schulmeister | [email protected] 20.06.2015 Seite 13wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
• Point system from 6 to 1 point• More CMS can receive the same points• Easier to enlarge on additional CMS• Challenge: how to rate time effort
Evaluation methodology: Rating
Gernot Schulmeister | [email protected] 20.06.2015 Seite 14wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
• S: Scale, HE: Highest effort, EpP: Effort per Point• Calculation: Highest effort divided to 6 rounded to half
an hour is the effort per point• Example: CMS 1: 6h, CMS 2: 3h, CMS 3: 2h → Scale 2• Result: CMS 1: 2 points, CMS 2: 4points, CMS 3: 5
points
Rating: Time effort
S HE EpP 6 5 4 3 2 1
1 4 0,5 to 0,5 1 1,5 2 2,5 from 3
2 8,5 1 to 1 1,5 – 2,5 3-4 4,5 – 5,5 6 - 7 from 7,5
Gernot Schulmeister | [email protected] 20.06.2015 Seite 16wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
Evaluation: time effort
Effort Ranking Rating
Contao 22,5 69 73
TYPO3 23 64 72
Wordpress 25 52 66
Joomla! 33,25 42 62
Neos 45,75 36 57
Drupal 47 31 51
Gernot Schulmeister | [email protected] 20.06.2015 Seite 17wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
Evaluation: implementation quality
Ranking Rating
TYPO3 69 64
Contao 52 54
Drupal 48 48
Joomla! 47 47
Neos 41 46
Wordpress 37 45
Gernot Schulmeister | [email protected] 20.06.2015 Seite 18wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
Evaluation: developer – developing profile
Ranking Rating
Drupal 26 25
Neos 21 23
Joomla! 21 21
Contao 16 15
Wordpress 13 16
TYPO3 8 6
Gernot Schulmeister | [email protected] 20.06.2015 Seite 19wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
Drupal
• Content based CMS• Based on a node system • Easy to create and configure content elements• Easy to style without changing source code• News and Lists with views• Many modules have to be installed• No full text search for content elements• Problems with translations on static pages• Login Url hard to remember ?q=user/login
Gernot Schulmeister | [email protected] 20.06.2015 Seite 20wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
Contao• Page based CMS• Similar to TYPO3 CMS • Unified development process: Create content in a
module → Assign it to a frontend plugin → make the frontend plugin visible through a page layout → assign the page layout to a page
• No source files had to be changed for the implementation only the styles
• CSS can also be stored in database• No translation handling → Multi tree concept
Gernot Schulmeister | [email protected] 20.06.2015 Seite 21wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
Joomla!• Content based CMS → only one content element per
uri• 3 types of extensions: components, modules and
plugins• Menu types for different content on pages: default:
article, category lists for news and room lists or form• Modules are positioned in a part of the page layout• For each header image own module necessary• Not easy to add fields to content elements• No translation handling in the frontend
Gernot Schulmeister | [email protected] 20.06.2015 Seite 22wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
Wordpress
• Content based CMS• Good facilities for translation handling and adding
additional fields• A lot of changes in php source code files were
necessary• Code with mix of php and html• Only static pages were used
Gernot Schulmeister | [email protected] 20.06.2015 Seite 23wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
TYPO3
• Update from 6.1 to 6.2 caused problems• Indexed search did not work out of the box• Configuration languages like Typoscript or yaml only in
TYPO3 products• The form content element was not usable• Extensions are often buggy
Gernot Schulmeister | [email protected] 20.06.2015 Seite 24wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
Neos
• Installation caused a lot of troubles• More memory and more expensive hosting packages
necessary than for other CMS• SSH access for flow scripts necessary for example to
create new nodes• Backend is not always stable• Errors when publishing changes• Multilanguage behaviour caused double input of
content
Gernot Schulmeister | [email protected] 20.06.2015 Seite 26wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
Conclusion• All features can be implemented with all CMS• Everyone will defend his favourite CMS• Its important to catch the starters• Objectivity is restricted by the developer and
developing profile and circumstances• The evaluation still has a lot of deficiencies• Maybe a unified developing process on top of
configuration would be a good idea for TYPO3 products• For Neos it would be good to become cheaper in
memory and resources to have better chances on the market
Gernot Schulmeister | [email protected] 20.06.2015 Seite 27wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
Recomendations (besides TYPO3)
• Drupal → Community websites• Contao → for starters who need a websites very
quickly• Joomla! → websites with a lot of out of the box
features• Wordpress → Blogs• Neos → Business Applications with little CMS, if you
want to implement everything yourself and use modern implementation techniques
Gernot Schulmeister | [email protected] 20.06.2015 Seite 28wfp:2 GmbH & Co. KG Mönchengladbach | www.wfp2.com
CMS Evaluation
Links
• Drupal: drupal.p256913.mittwaldserver.info/• Contao: contao.p256913.mittwaldserver.info/• Joomla!: joomla.p256913.mittwaldserver.info/• Wordpress: wordpress.p256913.webspaceconfig.de/• TYPO3: typo3.p256913.webspaceconfig.de/• Neos: neos.p256913.webspaceconfig.de/