A reusable starter should make the next product easier to build. Its own website has a different job: explain the foundation and show what people have built with it.
Three clear responsibilities
The official website introduces the template. It serves static content and does not need a product database or a user session.
The working demo exercises the product foundation: tools, accounts, saved history and the interface. Its sample tasks demonstrate delivery behavior; they are not evidence of demand or completed independent product launches.
Generated products live in their own projects. Each one owns its brand, domain, configuration, data and product-specific code.
Share the interface, keep the product local
The shared UI package owns design tokens and components with real consumers. Navigation receives links and actions from the application. It does not decide where the workspace lives or which product plan is available.
The same rule applies to content. Official build notes and a product’s user guides have different readers, so they have separate collections even when their cards share a visual component.
Let real use guide abstraction
The first product reveals missing pieces. The second reveals which pieces repeat. Reuse is strongest when it captures a behavior that has already earned its place in more than one product.