I recently twittered "The documentation for #ezpublish should be made more welcoming and more focused on common tasks." Here is my feedback on the FAQ pages (http://doc.ez.no/FAQ)

I have been working as a developer with eZ publish since 2002 and version 2. For the past 10 years I had my own company and exclusively developed eZ Publish websites. As the technical director I was responsible for the sales, marketing, development and support of eZ Publish, clients including Hitachi and the UNESCO. eZ Publish has been my main source of income for those years, and I consider myself a loyal supporter of the product. However, as a mid-sized company it has been a continuous and very tiresome struggle to find and keep developers who were capable and motivated enough to work with eZ publish for more than a year. I think my company was not the only mid size company with that problem.

I needed a PHP script to export the template output from a module ($module_result.content) to a file stored in the storage folder. Of course this could be achieved by curl or  get_file_output, but I wanted a script to generate the template output rather than fetching it.

According to various online comparison tools for content management systems, eZ Publish and Drupal offer a similar range of functionalities. As a first step in comparing both content management systems, in this blog post the ecosystems of both are compared. The ecosystem surrounding an open-source product usually consists of the community of users, developers, clients and often a company and its partners. A subsequent step will be a functional and technical comparison of both systems.

This post is an abstract of the report "Comparing eZ Publish 4.x and Drupal 7.x", commissioned by Contactivity bv, based in Leiden, the Netherlands. The report is based on two days of web research and published online in order to collect feedback from both the Drupal and eZ Publish ecosystem. Please contact me directly if any of the quotes in this post should be corrected.

Over the past few years, community and web 2.0 functionality in eZ publish has been slow to develop, both as part of the eZ publish kernel and as extensions contributed by the community. However, the pace seems to have picked up considerably. Is it time to revive the eZ community extension project?