We are players in Poleetic, and we love challenges and entrepreneurship.

Therefore, we are proposing that our intern, Simon Soustelle to take his best pen and share with you his experience at the CMS day. Here is the result of the visit …

CMSDAYThe CMS Day was held on Tuesday, June 28 at the Paris MAS.

Organized by the European integrator of open source solutions Smile, this was the opportunity to meet several speakers representing various CMS.: Spip, TYPO3, WordPress, Drupal, eZ Publish, Jahia, Ametys, NoviusOS, XWiki, Mura, Liferay, Hippo CMS, RBS Change, CMS Madesimple, Plone, Lutece, Joomla! and Rubedo.



Website performance

Since 2012, Internet users would like to have pages that load immediately. According to webarchive.org, since 2010 until today, pages continue to provide a richer experience for the user but their weight is increasing dramatically. On average, a page takes 5 seconds to load (including javascript).

The case of WordPress is interesting because in recent years we notice almost similar loading times, an identical hardware use level while generating far more data than in the past.

Cache issues were discussed as well as the CDN which have no interest except from an international perspective. However, the use of Lazyload can be a good way to ease loading.

Website factories

Many CMS (eZ Publish, Liferay,Hippo CMS, Jahia, Drupal) now offer the possibility of generating multiple web sites from a single back office.

There are 2 forms of website factories:

  1. The multi-website single-instance in which the content is shared between websites.
  2. The multi-website multi-instances in which the contents are not the same but appealed to the same business structures.

The eZ Publish case is particularly interesting because it allows, for example, people to build both websites and Smartphone applications since it’s the same back office with generation of templates on the fly.
Generally these CMS are ready for website factories. The only limit will be the governance of the user.

What can we expect for the future?

The speakers were unanimous: A CMS is not only about web. A CMS must be the conductor of data. It can, and will be able to, better structure the data for any type of stakeholders and any devices: web, application, smartphone, tablet, television, fridge… The SQL will give way to NoSQL that will offer more flexibility in data management especially with the Big Data era.
The use of metadata and content structure may further be able to do more in the months and years to come by powering a single repository from a variety of external sources.

To conclude with a figure: 7.5% of a companies’ physical documents are lost or misfiled. Hence, the importance of establishing a tagging and metadata system.

The choice of a CMS depends on the chosen strategy and needs:

  • Need to use / reuse of data according to the stakeholders and the technologies to be used.
  • Need for customized information (depending on the interlocutor).
  • Need for information  and speed of access to the information.
  • Need to retrieve the data.
  • Multi-websites need