28/04/2023
Jumping in with both feet to help Splash About move from a headless architecture on Magento 2.
We review the case for a standard Magento frontend vs. headless architecture, in terms of maintenance, performance and return on investment. How do you go about removing headless architecture on Magento 2?
Splash About had previously commissioned a Magento 2 website, which had been implemented with a headless architecture using NextJS. Although technologically advanced, the current setup was causing headaches for the client who were struggling to integrate new features due to a setup that was highly bespoke and required extensive development, even for a small change such as a new form field. For this reason, the client wanted to switch back to a traditional Magento website with a standard frontend. We came up with a plan to convert the headless website to a traditional Magento storefront, which could more easily be customised and extended, thanks to Magento 2’s open ecosystem of modules, plugins and extensions.
The end goal was to deliver a solution that:
• Is more portable.
• Integrates easily with other Magento 2 frontend solutions.
• Uses common Magento 2 standards that require much less development time compared to a bespoke build.
• Is not ‘locked in’ to any one developer.
Read our full case study to discover the benefits of headless vs traditional frontend for Magento 2: https://www.absolute-design.co.uk/blogs/case-studies/making-a-splash-about-headless-vs-traditional-frontend-for-magento-2