It's time to add support for v3. (Even thought that would make this package 2.0)
We can start with just statamic new. (We don't need the version or update commands, since you can use php please version and composer update respectively now.)
It should support selecting the starting point. By default it should start from statamic/statamic but users should be given the option to select a starter kit instead.
It should read starter kits from a JSON file which would just have ours to start with, but would allow people PR their own starter kits into the command, like https://github.com/studio1902/statamic-peak
Take inspiration from laravel/installer, rather than v1 of this repo.
(The Laravel installer uses composer under the hood where ours used a zip downloader.)
Work on a separate branch, and once it's ready we can swap branches around so that master is the new version and the old one can live on a branch.
It's time to add support for v3. (Even thought that would make this package 2.0)
We can start with just
statamic new. (We don't need theversionorupdatecommands, since you can usephp please versionandcomposer updaterespectively now.)It should support selecting the starting point. By default it should start from
statamic/statamicbut users should be given the option to select a starter kit instead.It should read starter kits from a JSON file which would just have ours to start with, but would allow people PR their own starter kits into the command, like https://github.com/studio1902/statamic-peak
Take inspiration from laravel/installer, rather than v1 of this repo. (The Laravel installer uses composer under the hood where ours used a zip downloader.)
Work on a separate branch, and once it's ready we can swap branches around so that
masteris the new version and the old one can live on a branch.