ekino "Rendr" Solutions

The head for your Headless solutions
5 minute read
By Thomas Rabaix

Headless CMS, or sometimes called Headless Ecommerce or Headless solutions has long been seen as a trending approach by vendors to give more freedom to the developers.

That freedom allows the programmers to build a tailored and engaging experience for the end users - headless solution does not provide any kind of HTML rendering (head less, html less) which makes the solution very light and very affordable.

From a frontend developer standpoint this is great: freedom, flexibility and quick preview of the final pages or applications. But not only. All the responsibilities ie: business rules, API calls and functional requirements are managed by the same system.

From a project resource profile, it means the teams will predominantly have more frontend engineers and less backend developers. However, complexity and business rules remain, making it a go-to solution for a very large panel of businesses.

So we say “Headless”, sounds scary right? Well, we still need a head!

So at ekino we have been trying to answer a simple but very common problem.

Can we introduce a cleaner headless architecture? Where frontend developers can focus on frontend tasks only: accessibility, animation, cross platform compatibility, web performance, and where backend developers can focus on providing aggregated and secured data as well as robust integrations?

Well, we made it happen and we now leverage this to match business requirements, performance and most importantly: user satisfaction. We have been working on a framework to help build such platform, not only from a tech perspective, but also from the organisational level.

We recently worked with leading organisations worldwide to help them develop solutions that not only benefit the customer, but drastically change the way organisations use and develop their digital ecosystem.

Our recent work for Liberty Specialty Markets and the replatforming of their digital vitrine is now live in 8 countries and 6 languages.

As a digital transformation partner, we believe we should not be building each piece of a digital platform. We should be leveraging each vendor to build the best customer experience. Each service should be easily swappable, to fit requirements at a valid time. Requirements might change over time.

“Rendr” defines a set of simple objects used to define a page used in two sets:

The input: a headless CMS, any data source, CRM, e-commerce - The output: HTML, but also a PDF, even a native app!

This minimalist approach opens to a wide range of options. We have plugged as input sources: Drupal (Headless mode) or Contentful, as a CMS, aggregated data from Airtable to manage large dataset. And for the output source, use solution like NextJS or simply just raw html for rapid development. This separation of responsibilities helps to produce high scalable and resilient systems.

This minimalist approach also helps reducing the amount of work required to build backoffice, and put this amount of work into the frontend, or aggregation rules to match business needs.

If you believe your business needs a similar approach or if you would like to discuss the solution with one of our experts, please contact us.

Thomas Rabaix
CTO London, Ekino.
15 years of experience in large project developments, open source solutions, consultancy and team management.

more from ekino

7 minute read
How to change your approach and reinvent processes to be ‘tech and design for Good’.
By ekino London