<aside> <img src="/icons/branch-merge_gray.svg" alt="/icons/branch-merge_gray.svg" width="40px" /> GitHub repos 🔗 Backend repo 🔗 Frontend repo
</aside>
<aside> <img src="/icons/dependency_gray.svg" alt="/icons/dependency_gray.svg" width="40px" /> Live versions
Offline
</aside>
Learning. A word that can have a lot of meaning. To me, learning means trying things out, hitting blockers, and finding ways to go around them, which could summarize this project. When I started I had barely any idea what a Headless CMS is or what it is used for, after 4 weeks of work I can confidently say, I’m happy I’m not studying to become a content administrator. Jokes aside, this has been fun, frustrating, amazing, valuable, and I've learned a lot. Not only about Strapi as a Headless CMS but also about how to leverage Next.js 14’s app router. Following this report, you’ll find out what I created, why I created it, and how I created it including the ups and downs of working on this project.
The idea behind the project is an e-commerce store which sells phone backgrounds, in other words digital content with various pricing. However, entering the site you’ll learn that all products are free because this is a school project with free images for products and therefore no payment required, or implemented.
The purpose of the eCommerceSite, as it originally was called, was to get a better understanding of how, you guessed it, an e-commerce site can be developed. It’s been a good way for me to get a glimpse into functionalities that can be used for such a site and how to structure a project on my own. Although, I have to be honest and say that my main focus was to deepen my knowledge of relevant technologies and front-end programming as a whole. So what did I aim to achieve?
From the thesis proposal, my goal was to create: “…a mock full-stack e-commerce site leveraging state handling, error handling, and headless CMS. The motivation behind the project is to get an insight into e-commerce platforms and to better my understanding of the above-listed technologies which is a deep dive into Frontend Development.”
My measures of success were mostly connected to functionalities I was interested in learning, which were: