The struggle I have with project generators is that you can only run them once.<p>If you didn't think you needed the billing module when you ran it but later you find that you need it, the generator is of little use. You end up running it again to create a new project and manually copying in the billing pieces.<p>Or, if the generator is upgraded after you used it, it's to late for you.<p>I wonder if this tool tries to mitigate those issues at all.
I was thinking of building this for Next.js in a very similar way. I love the fact that this exists for a different stack! I think your implementation of the project template is definitely the way to go. As a customer, when I buy something to jump-start me, I want it to be as clean and simple as possible. Generating the project from a configuration handles that nicely.<p>Outside of the generator itself, what have you found most beneficial for converting customers and convincing people to buy? Documentation? Videos? The community access?
For the first Jinja2 template pass, you could swap the Jinja2 delimiters rather than mess with {% raw %} tags: <a href="https://jinja.palletsprojects.com/en/3.1.x/api/#jinja2.Environment" rel="nofollow">https://jinja.palletsprojects.com/en/3.1.x/api/#jinja2.Envir...</a>