Forums / Discussions / Expanding the developer community

Wednesday 03 August 2011 7:59:04 am - 6 replies


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.

» Read full blog post

Author Message

Ivo Lukac

Wednesday 03 August 2011 10:46:25 am

I can only agree with you, Sebastian. I am sure most of eZ partners feel it as we do too.

My blog post on this topic from November last year:! with some interesting discussion discussion afterwards.

Robin Muilwijk

Wednesday 03 August 2011 11:07:17 am

Hello Sebastiaan,

Thanks for your thoughts, and feedback. I briefly read it and I think there are some good ideas to increase adoption of eZ Publish. I'll need to read it again and let it sink in. I'll make sure it get's the necessary attention also.

Regards Robin

Board member, eZ Publish Community Project Board - Member of the team - Key values: Openness and Innovation.

LinkedIn: // Twitter: // Skype: robin.muilwijk

André R.

Wednesday 03 August 2011 2:56:24 pm

Excellent post!

Actually we have already taken this to heart (and action) for the last 6+ moths, and you'll see what I'm talking about when we will publish code, blog-post(s) and calls for feedback on API later this month.

To give a peek of how far we have taken it* (making eZ Publish easier to learn):

  •  Concepts have been renamed to make them more intuitive, some:
    • Node -> Location
    • Class -> Content Type
    • Attribute -> Field
  • Full use of PHP5 and it's oop model with high amount of code reuse, and less code needed to extend / develop against it.
  • Fully documented API (and fully unit tested, but that goes without saying)

It does not stop with API (Annapurna) though, after API the rest of the kernel should receive a similar treatment making eZ Publish easier to use, more intuitive, lighter (far higher degree of code reuse, thus easier to maintain and grasp), faster and more modern, all while still being the most powerful, extendable, adaptable CMS(/F) out there.

Nico and others have also been hard at work making sure there are more educational content online, making training and especially certification more accessible.

So once again, great post!

* These things will of-course to some extent be open to debate, but we hope they make sense to all or most of you.

eZ Online Editor 5: || eZJSCore (Ajax): || eZ Publish EE

Sebastiaan van der Vliet

Wednesday 03 August 2011 11:32:57 pm

Hi André, thank you very for your feedback on my blogpost. I am looking forward to see how the new updates will make it easier for 'novice' developers to work with eZ Publish. However, I would like to emphasize that, in addition to technical innovation and simplification, there needs to be an all pervasive marketing effort to push eZ Publish to potential developers. This should have a high priority - many of the suggestions mentioned in this post spring from issues that have been around for years but have never been properly addressed. The point here is that I think we are starting to run out of time and I really don't think we can afford to have these issues lying around for another 6+ months. In my opinion this is too important to be left to the community alone - eZ Systems should take the lead in this. Hi Ivo, I like your blog post - many good ideas in there!

Certified eZ publish developer with over 9 years of eZ publish experience. Available for challenging eZ publish projects as a technical consultant, project manager, trouble shooter or strategic advisor.

Felix Laate

Monday 08 August 2011 5:49:05 am

Great and important post!

In addition to the allready mentioned suggestions, I would like to emphasize the importance of extensions. Even with skills, extending eZ Publish can be quite cumbersome and even difficult. Systems like Drupal and WordPress, thought one can argue that they have messier API's, have easier entrypoints when it comes to extension. Hence they have lower startup costs. eZ Publish should have an easier interface when it comes to extensions.

Another thing is documentation. Luckily things are improving in this area, but more could be done. Specifically in the areas of tutorials and books. Tutorials make people start. Books make them stay.


Publlic Relations Manager
Greater Stavanger

Igor Vrdoljak

Thursday 11 August 2011 6:22:56 am

I could not agree more with this post. Thanks Sebastian for keeping the torch lit :)  

Additionally, I would like to emphasize on the need to develop more concise and straightforward documentation material for introducing newcomers to eZ.

Right now there are nuggets of knowledge spread on multiple sites (,,, and a number of blogs and sites), but I see the need for an "official", up-to-date, step-by step introduction material that would help climbing that steep learning curve for newcomers. Ranging from defining content classes and publishing objects in adminsitration interface, to developing custom extensions. There is some really great content on, but it needs to be presented more clearly and also kept in sync with new eZ releases to be of help for novice developers.

We are right now getting ready to train a few new developers in our company, and this kind of content would really help a lot.


You must be logged in to post messages in this topic!