Starter replaced by npx elm-pages@latest init my-app?

[nova-nowiz]

As there is a new version of elm-pages that was released in april and the last commit here is from march, I suppose that this is not a starter for v2.
Could it be updated or is it totally replaced by npx elm-pages@latest init my-app?

[dillonkearns]

Hello @Narice, I've been thinking about this as well. I think it would definitely be useful to have different starters (skeleton app and blog, for example). I'm still trying to decide if the official starter repo has value in that format (for example, being able to browse through the code on GitHub could be nice), or if it's confusing to have something in two different places.

I'm considering just making the starter repo into a blog starter template.

[nova-nowiz]

Hi, thank you for the response!
Being able to browse through the code of a specific template on Github would be pretty nice.
I don't personally think it would be confusing if the readme and/or description of the repository stated that this is for browsing the code and made note of the command(s) that exist to instantiate the template(s) contained in the repo.
If there are no commands associated to this repository, it might still be a good idea to mention the npx elm-pages@latest init my-app command so that people discovering elm-pages know that this is possibly the simpler way or the default way of instantiating a new elm-pages project.
If this repository becomes a starter repository for a blog, changing the name to avoid confusion could also be a good idea as it would be probably more specialized than a general starter.