Why a Large Digital Studio From Slovenia Uses October CMS

Spletna postaja is a rather big company - they have 28 employees. This is an experienced team of developers, designers, marketing and support specialists. Their clients range from small start-up companies in need of basic web design to large corporations requiring complex web applications. The company has planned, created and launched hundreds of successful websites since their inception, for many different types of businesses in Slovenia and Europe. Their projects cover a wide variety of web development services, such as website designs, simple website portfolios, blogs, e-commerce solutions, web applications, B2B systems, complex e-commerce platforms, and other custom-tailored services. Early days - home-grown CMS

Like many other digital agencies, Spletna postaja has used its own CMS called Booster. The platform was developed around 2004, as Roman explains in those days every “real” web agency in Slovenia had their in-house CMS. The company had a specific idea of what a CMS should look like and there wasn't anything like that available on the open-source market back then. The intention was to create a user-friendly database editor that their clients could easily use.

Booster was perfectly satisfying the company’s needs for many years, however, there was a growing pile of issues. The codebase was huge and getting progressively harder to maintain. Other problems the team was facing include:

  • There was a huge legacy codebase to maintain, especially the core which included a framework and a CMS.
  • It didn’t use Composer, which made integrating 3rd party packages difficult.
  • All existing 3rd party components were getting outdated and were hard to update without significant changes to the core.
  • It didn’t have an ORM, making it harder to write good object-oriented code.
  • There were some security concerns since a lot of custom solutions were used in critical parts of the system.

Another serious issue was a lack of documentation and difficulties getting and training new developers who would be prepared to work on a legacy system.

With time it became clear that a solution is needed and the team started looking for alternatives. Finding October CMS

The team came across October CMS during the online research (Google, GitHub), when searching for open source solutions based on Laravel framework that would support the company’s workflow. They were looking at open source alternatives that would support the kind of projects the company was working on. The development team had previous experience with Laravel framework. As Roman explains - at that time October CMS was (and still is) by far the most advanced CMS for Laravel and it seemed to fit their needs almost perfectly. A unanimous decision was made to make a gradual transition to October CMS.

One of the main requirements for a prospective platform was the flexibility and support for heavy custom development for the company’s clients. At the same time it needed to be well supported by the open-source community, making it possible for the team to focus on the development of the end features rather than maintaining the core. Good online documentation was also one of the main criteria, which proved particularly useful when training new junior developers.

October CMS fits all of that perfectly. Additionally, the fact that it is based on Laravel framework (which the team already had previous experience with) is a huge plus as well. The transition

Transitioning to a new platform was a tough decision from both the business and technical perspectives. The biggest challenge was evaluating the transition in terms of the required time and cost. The team had to develop a lot of custom code to fully support all of our use-cases that were supported by the previous platform, while at the same time investigating new opportunities that a complete rewrite offered the team.

The toughest decision was between the two options - continue upgrading the old platform or do a complete rewrite. The complete rewrite was only ever an option in case the team used an open-source platform that would enable the company to move away from maintaining a custom framework and CMS and focus on the features. Luckily October CMS enabled them to do just that and they went into it fully aware that it’s a long-term decision.

The full transition took two years in total and was finalized in 2019 when all new projects were started using the October CMS codebase. Happy with October CMS

After using October CMS for a few years the company sees many benefits of the transition. The biggest business-related advantage for the company was the ability to move away from maintaining their old platform and shift the focus to end-features requested by the customers. The other big advantage is the fact that October CMS has a modern codebase and comprehensive online documentation, which makes training new developers on the platform quicker and easier. A complete rewrite offered the team an opportunity to re-think some of the existing solutions and significantly improve upon them, making the company more competitive in the market.

The biggest advantage for their customers was a cleaner and more modern back-end experience, which makes them more comfortable managing their applications by themselves.