Getting started with the template
Begin with configuration, then replace content in small verified batches.
Start in src/config/template.ts. Update the site name, project name, community URL, official URL, docs URL, and catalog labels. Then update src/lib/site.ts only if the derived defaults are not enough.
Next, replace a small sample of catalog records in src/content/items. Keep the same fields at first: name, number, elements, role, description, stats, attributes, and facts. Once ten records build correctly, migrate the rest.
Finally, rewrite articles and guides. Keep the example structure: one launch note, one source policy, one catalog integration note, one quality note, and a few domain-specific guides.
Adaptation Notes
Use this guide as a working pattern, not as fixed product copy. Replace the example nouns with your project’s real terminology, then verify that each internal link still points to a generated page. If a claim depends on external evidence, attach the source in the relevant content record instead of burying it only in prose. This keeps the guide readable for users and maintainable for editors.
Before publishing, inspect the rendered page on mobile and desktop. The template is intentionally dense, so headings, cards, tables, and callouts should be checked with real text rather than short placeholders. When a section no longer applies to your niche, remove it cleanly or replace it with a more useful workflow; do not leave empty headings behind.