Thanks. I plan to continue this series but not very soon, as I have other priorities currently.

I completely agree with you for the advantages. Well said. However I think talking only about templates using DSLs is a bit restrictive. Although DSLs are mostly used to author infrastructure code, there are other solutions that take advantage of existing programming languages (along with their tools, IDEs, ecosystem) to write infrastructure code: Pulumi, AWS CDK and Terraform CDK for instance.

Very interesting ideas, love the article thanks

Interesting topic. However, I think there are a few things to update in your article if you are talking about the latest tools for Vue.js. Vue CLI is in Maintenance Mode, people should use create-vue instead (which is based on Vite that you already mention in your article). The Vetur extension works but Volar has become the official extension. Another thing related to state management that you could have a look is using composables. That can be an alternative to Pinia for simple needs and it's built-in.

Nice pointing out to vueshool and Vue mastery, they really help when you begin. Concerning the store to use however, Vuex is not the recommended one, Pinia is.

Showwcase is great but unfortunately currently the editor to write articles does not provide a great user experience compared to others in my opinion

Nice article. Have you open sourced your code somewhere?

Thanks for the article. I was wondering: do all the publishers you mentioned use canonical url to redirect to your blog and avoid SeO issues (duplicate content).

I noticed you mentioned a few times Vuex which is a perfectly valid store to use in Vue. However, now that the recommended store for Vue is Pinia, you could have also mentioned it.

Nice article 👍. In case some people are interested, I wrote a long article comparing Pulumi and Terraform.https://www.techwatching.dev/posts/pulumi-vs-terraform