Wednesday 29 July 2015 01:17
A month ago we announced opensourcing our Sylius integration with eZ. Today the project is shortlisted for a community stand at the SymfonyLive London. If you would like to support us please place your vote at twtsurvey.com/bbkwh3l82sb55rt.
Tuesday 07 July 2015 03:53
Summer is coming, and the lastest Alpha release of eZ Platform is carpooling with it.
Friday 19 June 2015 10:42
In order to increase the image serving performance of high-traffic websites and improve the editorial user interface around image management, Mugo Web came up with an alternative way to serve content images in eZ Publish. It is aptly titled the "Mugo Image Server for eZ Publish".
Monday 15 June 2015 01:30
There are many means of communication in the community already, but there is never enough. So with raising Slack popularity it was logical we created a domain there:
Wednesday 03 June 2015 01:11
Friday 22 May 2015 07:28
eZ Publish 5 comes with built-in Varnish Cache support. Essentially this means that when content is published in the eZ Publish back-end, it notifies Varnish so that the Varnish cache is cleared. This feature is often called "purge-on-publish" and makes it so that you can cache your pages for a very long time, but that edits refresh the cache and thus appear immediately. To get this native support, you just have to use the "new stack" in eZ Publish. However, even if your legacy site is not ready to be fully upgraded to the new stack and you are running eZ Publish 5 in "legacy mode", you can take advantage of this native support.
Friday 22 May 2015 11:51
Dear eZ Community,
The next episode of The eZ Publish Show will be aired on Wednesday, May 27th at 15:00 CEST (9:00 ET).
I have been thinking a lot about different kind of experiences related to CMSs, a product that is a corner stone of our business. We implement content-centric web solutions so having a solid CMS like eZ Publish is of a vital importance. The problem with CMSs is that they have many different user types to satisfy: end users, editors, translators, developers, designers, etc. With a lot of buzz about customer experience (remember WEM and CXM acronyms), it looks like the editor experience was forgotten, as there are still a lot of editors pulling their hair out when editing content! Did modern CMSs sacrifice good editor experience for improving customer experience?