Backend & Frontend
E-commerce platform for Kein & Aber
We took on overall technical responsibility and delivered an integrated e-commerce shop on PHP/Craft CMS, automated complex data imports, and secured robust infrastructure (Kubernetes/PostgreSQL).
The project: an integrated web shop for the publisher
A joint project with our partner dreipol.ch – keinundaber.ch
The publisher Kein & Aber needed a capable e-commerce solution covering book sales, author management and event information in one place. The challenge lay in taking overall technical responsibility and building a stable backend that automates complex data imports and coordinates smoothly with external subcontractors on the frontend.
The solution: overall technical ownership and agile delivery
devs group took on overall technical responsibility and shared project leadership with dreipol AG to deliver an integrated web shop. Our know-how moved the project decisively forward.
Backend engineering: we built the whole backend of the shop on PHP and Craft CMS 4/5, and implemented Vue 3 with Nitro for the frontend, which was created in close collaboration with dreipol.
Automation and integration: automated data imports (books, authors, events) through cron jobs and external interfaces, plus the integration of Datatrans for payments, keep operations running smoothly.
Robust infrastructure: we secured a highly available infrastructure using PostgreSQL, MinIO S3 storage, and container orchestration through Red Hat OpenShift (Kubernetes and Docker).
Project coordination: coordinating the parties involved was handled through clear communication, agile methods and shared project leadership.
The result: a smooth, automated publisher’s shop
With devs group carrying overall technical responsibility, Kein & Aber has a thoroughly modern, stable and automated web shop. The clean separation of design/frontend and backend, together with robust infrastructure, secures efficient payment handling and day-to-day data accuracy without manual work.
Frequently asked about this project
Who did what?
devs group carried overall technical responsibility and built the backend (PHP, Craft CMS); our partner dreipol designed and helped build the frontend. Project leadership was shared; the publisher had one point of contact rather than two building sites.
How do books, authors and events reach the shop?
Automatically. Cron jobs import the data through external interfaces from the publisher’s systems. Nobody maintains catalogues twice, and the shop stays consistent with the publishing programme.
What does the shop run on?
Kubernetes with PostgreSQL, with payments handled by Datatrans. The infrastructure is deliberately the same as on our other projects: versioned, rolled out automatically, and free of knowledge that exists only in one person’s head. For the publisher that means predictable running costs and no standstill when a single person goes on holiday.
