Software developers like to write code and they like it very much. They tend to enjoy writing exhausting tests and continuous integration/continuous deployment configurations to assure top-notch quality of software. However, most of the time one part of the whole software development process somehow goes under the radar. The most overlooked part is writing documentation. We always tend to say to ourselves that we will write the documentation once the project is finished, or that we will release this version first and write the documentation later. LeBlanc’s law clearly states: Later equals never. I think this requires no explanation, but instead forces us to act.

We live in a time where knowledge is at our fingertips and educational programs from all disciplines are available online. Yet, people are people and most of us like to communicate in person. We still prefer going to conferences, meetups, and similar events where we can learn from our peers. The question arises: how to estimate the value you get from a conference?

Web Summer Camp 2018 is slowly but surely closing in. We have defined the tracks (a few surprises there!), finished the speaker selection process, and are working on the track programs and extras – read on!

Site API for eZ Platform is a thin layer on top of the eZ Content Repository API. It provides simple to use features for eZ developer’s everyday work by reducing a lot of boilerplate code, thus saving time and simplifying maintenance.

When we started developing web solutions with eZ Publish in 2004, the architecture was simple. We had a Linux operating system, an Apache web server, a MySQL database, and PHP runtime as an Apache module. You know this architecture by its LAMP acronym.

Over the years, things got a bit more complicated due to performance reasons and because some other tools were suitable for some specific features. The situation exploded with the new stack and eZ Platform. We are now on LNMpPf7VHMS as our default architecture with the possibility of adding a few more letters in the near future.

After several early adopters launched their first websites based on Netgen Layouts at the end of 2017, it was a perfect time to speak to them about their experience using our product – what they liked and what they thought we should improve.

As a service-based company, we have been working for many years on various web projects, building tailored solutions for our clients. It is always great to see a solution we have created put to use, but a quite different experience is creating a new generic product and proving its value in real life projects.