Problem we must solve
Summary
Create a new documentation section called Frontends Recipes for practical, feature-oriented Shopware Frontends guides.
The goal is to explain common storefront flows end-to-end: UI action → composable → API client → Store API endpoint → generated types → session/state updates.
Motivation
Developers need a place to understand how real storefront features work in Composable Frontends, not only individual packages or composables.
Example topics:
- Login
- Registration
- Product Page
- Mini Cart
- Product Listing
Target Audience
Frontend developers who know Vue/Nuxt or frontend basics, but want to understand Shopware Frontends and Store API flows.
WHY we need to solve it
Developers often need to understand how a complete frontends feature works, not only which composable or package exists.
Today, this knowledge is spread across package docs, examples, templates, generated types, and source code. This makes it harder to understand real Shopware flows such as login, cart updates, product pages, or checkout steps.
Frontends Recipes would provide one consistent place to explain these flows end-to-end, reduce onboarding time, prevent common implementation mistakes, and make generated Store API types easier to use in real projects.
Solution to the problem
No response
WHO benefits
No response
WHERE will we do it
- New Storefront Recipes section exists.
- At least one pilot recipe is added, preferably Login.
- The pilot recipe uses the agreed structure.
- Store API operations and generated types are referenced explicitly.
- Existing docs are linked where useful, but not migrated yet.
Problem we must solve
Summary
Create a new documentation section called Frontends Recipes for practical, feature-oriented Shopware Frontends guides.
The goal is to explain common storefront flows end-to-end: UI action → composable → API client → Store API endpoint → generated types → session/state updates.
Motivation
Developers need a place to understand how real storefront features work in Composable Frontends, not only individual packages or composables.
Example topics:
Target Audience
Frontend developers who know Vue/Nuxt or frontend basics, but want to understand Shopware Frontends and Store API flows.
WHY we need to solve it
Developers often need to understand how a complete frontends feature works, not only which composable or package exists.
Today, this knowledge is spread across package docs, examples, templates, generated types, and source code. This makes it harder to understand real Shopware flows such as login, cart updates, product pages, or checkout steps.
Frontends Recipes would provide one consistent place to explain these flows end-to-end, reduce onboarding time, prevent common implementation mistakes, and make generated Store API types easier to use in real projects.
Solution to the problem
No response
WHO benefits
No response
WHERE will we do it