How to create a headless frontend framework that works for global eCommerce? Piotr Karwatka takes you through it, from ideation to release day and far beyond.Download
Piotr Karwatka, CTO of Divante and co-creator of Vue Storefront, has worked with over 2,000 developers across the world and with Fortune 1000 companies including Marc O’Polo or SAP.
In this book, he’ll take you through the phases of building your own framework from scratch, lessons learned along the way, and some case studies that prove the facts. You’ll also find out about headless solutions, the no-code movement, and managing a global development team. It’s everything you need to know before you start your adventure with a headless framework.
You probably know the methodologies and theory behind project management. But do you know which are more effective than others in headless projects? Do you know how to prepare for the unexpected and utilize patterns that simply work best?
Or, more importantly, how you can benefit from it? How does it change our approach and what benefits can it bring to your project? Piotr Karwatka is a no-code evangelist who can answer all your questions about this growing trend.
Now that we are all remote, building a team that truly cooperates and brings value is both easier and harder than ever before. It's all about balance. How do you give people power and freedom but make sure they stay focused and goal-oriented?
How to create a new software architecture by Harvesting vs. Designing
With Vue Storefront Next, Storefront UI, and other frameworks we've build, we had a chance to test different ways. Learn from our good and bad experiences and choose the best possible way for your headless framework.
How you design agnostic, reusable architecture for a modern frontend framework
Re-usable at the core, customizable at the edge: these are the key principles for building headless frameworks. It is possilbe to achieve if you know how.
What elements of the app-scape should you own, which should you build yourself, and why?
Frontend web applications were (and sometimes still are) seen as templates which you can copy-paste. Sometimes it's an effective approach but there are times when you need a custom solution. Find out when and why.