Symfony Finland
Random things on PHP, Symfony and web development
eZ Platform can run with configurations that have multiple separate content repositories. For the most part creating new repositories and sites is self documenting. There is gotcha with setting persistence caching for multiple repositories. This leads to random fatal errors as stash persistence …
I've had the privilege of attending some great events this year: WordCamp, PHP / eZ Publish Summer Camp and finally DrupalCon. These were all great experiences for a professional working with Web Content Management, but the most food for thought came from a much more modest event: A two hour breakfast seminar titled "The right content for the right context".
eZ Platform is the Open Source Content Management Platform from eZ Systems. Previously known as eZ Publish, the first version of the new product was launched in December 2015. Thanks to the Symfony Full Stack approach it is immediately familiar to Symfony2 developers, while extending it with content management features.
Content Management may appear simple to a layman, but when you end up working with multiple sites, multilingual, versioning, media assets and real user needs... it is not trivial. Symfony has been adopted by many popular CMSes. That's great news for all LAMP CMS devs!
It goes unsaid that the internet evolves at a rapid pace. Software is very flexible and on the web you can keep on upgrading continuously. It is, however, not immune to history and decisions made in the past. Many traditional Content Management Systems still focus on big releases, just like traditional desktop software has for decades.
RESTful APIs are on the lips of everyone currently. Everyone is got one or will have one very soon. They are always underlined as being full REST APIs. But if you're not fully utilising your API internally, is it really complete and a priority for you?