Symfony and Content Management
As an Open Source technology, sharing has always been a natural part of working with PHP. The catch is that it was not that easy and practical to cherry pick certain functional components from the vast libraries of code to use in your own applications. Thanks to improvements in PHP, the PSR iniatives and Composer this has changed: PHP and Symfony - Structure, Stability and Flexibility
In Drupal 8 CMS the Drupal community has decided to embrace many shared components from the PHP ecosystem. The most well known set of components are the Symfony ones. The HTTPKernel, Twig and others make it easier to work across projects built with different tools. If you use the Full Stack framework, you can easily tap into Neo4j, MongoDB, Redis and ElasticSearch from inside your CMS.
To give the Drupal community a different perspective the session will compare how different content management tools use Symfony:
- Bolt CMS - Building a new system from scratch with Silex (a Symfony microframework)
- Drupal 8 - Introducing PHP modern components into a legacy application
- eZ Platform - Transitioning the tool to the Symfony Full Stack Framework
We will take a look at the pros and cons of their implementations, how to share code between them and a brief introduction to the Symfony CMF project and the Sulu CMF. Loosely related to my talk on Content Management, Technology and Refactoring.