Keep your product content aligned with its configuration
Use file-based guides and examples that explain the actual SaaS you generated.
Two content starting points
The mother template's website explains how to use the template. The generator starts a new product with end-user content from starter-content/. In the new project, content/ belongs to that product and should explain its users' actual tasks.
Write instructions a first-time user can follow
State what to prepare, where to click or which command to run, what they should see, and what to do if it fails. Distinguish an operator configuration step from a customer action. Say when registration is needed and whether an output is simulated.
Avoid drifting plans and features
Use product/plan placeholders rather than copying numbers into several articles. Read the enabled modules before writing promises. Publish drafts only after checking links and examples; add a redirect when changing a slug.
Customize the product, run content checks, and inspect desktop and mobile before release.