Hey anyone who happens to read this. A few days ago I wanted to try compose my own music because I can't play on the Piano what's in my head.
I dedicate it to Nadine, a dear friend of mine :) May a piece of her soul live in this forever.
Hey anyone who happens to read this. A few days ago I wanted to try compose my own music because I can't play on the Piano what's in my head.
I dedicate it to Nadine, a dear friend of mine :) May a piece of her soul live in this forever.
I hacked together a small POC framework / boilerplate tonight which I’d like to share with you. But let’s first take a look at why and how this framework was born out of proven real world concepts and architecture.
Take for example Redux quite a while ago. Immutable states and centralized state management had such an impact that React added a useReducer
hook to the core.
Ever since useReducer
has been available I haven’t really found a need for Redux anymore. Pure reducers can be used in a similar fashion to Redux and Sagas can easily be implemented with useEffect
. However; a few principles stuck with me that simply made life easier because it just works.
In Part III of the Strapi + Next.js series, we roll up our sleeves and dive into building the Strapi backend. You’ll learn how to create a localized "Article" content type, configure permissions, and expose a clean API for your frontend to consume. We also walk through defining custom routers, controllers, and services for full flexibility—plus how to manage environment variables for seamless integration with your Next.js app. By the end, you’ll have a powerful, multilingual CMS running locally and ready to scale.