Moving toward on-demand template creation

[DanhezCode]

Why change the approach?

The current template setup started with a general base template and two specialized templates: one for distributable packages and one for web projects. Keeping this small set seemed straightforward, but the shared foundation creates maintenance costs that are easy to overlook.

Release notes lose part of the story

Shared features and configuration fixes are implemented in the base template, while the package and web templates focus on their own concerns. As a result, release notes in the specialized repositories can omit improvements they inherit from the base template.

Changes need to be synchronized

When the base template changes, the specialized templates also need corresponding updates to stay aligned. Doing this promptly helps avoid mismatches, but it adds repeated maintenance work and pressure to coordinate releases.

Direction

We are moving toward creating templates on demand through a centralized CLI, with examples kept together in the same repository so people can explore the available approaches. This should make shared behavior easier to maintain and make the available starting points easier to discover.

What this means for the existing templates

The existing repositories remain public and usable, and may continue to receive updates. This is not a shutdown or a restriction on existing projects. It is a recommendation to consider the new approach for new projects as it becomes available.

• Base template
• Package template
• Web template

This discussion is the central place for the rationale and transition as the new approach develops.