EPESI Blog

Updating EPESI and new releases

New releases and their frequency

Till recently we tried to make every release a huge thing, a big event, with lots of new features and improvements. This approach had its merits, for example our users didn't have to spend time on updating too often and there was a lot of time to get used to all the changes before the new ones were introduced.

Why another CRM?

There are many commercial and open source CRM applications on the market and some of them are mature products. So why to develop another one? Several years ago we were looking for a decent web based CRM type of application that can be easily customized. After evaluating dozens of products we came to the conclusion that none of them have features that we were looking for.

New feature preview - translation system

Current state

One of the very first things we introduced in EPESI, long before the first public release, was the translation mechanism. We wanted to create a way to translate the system fully to another language, to have all the labels and messages go through the translation procedure, but also to enable the users to label some parts of the system the way they want to use it.

Introduction - the reasons behind this blog

We are starting this blog because we would like to share with you some insights on how EPESI is made, what decisions are driving the development and perhaps explain why certain things are done in a certain way.

In our team we often hold discussion on what could be improved or added to enrich the system. There are many ideas floating in the air - some of them we didn't have the time to implement yet, while many are already part of the system. And through this blog we hope we'll be able to get you closer to the vision that is driving EPESI by presenting those ideas to you.