[Feature] Migrate to composer create-project to generate a new project

[titouanmathis]

This PR drops usage of SAO to scaffold a new project and replace it with support for the composer create-project studiometa/wordpress/project <project-name> command.

Benefits:

• Auto-update of Composer and NPM dependencies with Depfu
• More tasks are automated, creating a project is faster
• Easier to update existing projects

This feature can be tested locally by creating a packages.json file:

{
    "packages": {
        "studiometa/create-wordpress-project": {
            "dev-master": {
                "name": "studiometa/create-wordpress-project",
                "version": "0.0.0",
                "dist": {
                    "url": "https://github.com/studiometa/create-wordpress-project/archive/refs/heads/feature/composer-create-project.zip",
                    "type": "zip"
                }
            }
        }
    }
}

And then running the following command:

composer create-project --repository=packages.json studiometa/create-wordpress-project <project-name>

The global PHP version must be set to PHP 7.3 for this command to work, you can also specify a custom PHP version:

php73 $(which composer) create-project --repository=packages.json studiometa/create-wordpress-project <project-name>

Once the project created, you only have to go in the created directory and start ddev:

cd <project-name>
ddev start

Changelog

Added

• Add a default ddev configuration

Removed

• Remove prompt to customize the project's configuration
  The default values should be considered as sane defaults ; the project's name is the name of the folder in which the project is create

Changed

• Set the default target to modern when building assets (see studiometa/webpack-config#37)

To do

• Complete the changelog
• Add more explanation on how this work

[perruche]

🚀

[perruche]

improvement add the new way to kickstart the project composer create-project ...

[titouanmathis]

The issue is that this README.md file will be the one used for the project, it should not contain instructions on how to create a project. Or maybe they could be removed on creation to avoid any confusion.

[titouanmathis]

Another idea would be to migrate the new structure to the studiometa/wordpress-project repository and to keep this repository as documentation.

[perruche]

I like the idea of replacing the README after install. Kind of what we do with .env.example or wp-config-sample ?

[lusimeon]

issue: I don't think it's the role of this package to initialize git. Maybe we would like to create a project without git (only to test a feature locally). Moreover, it really depends on user access on repository.

suggestion: Maybe this script should be run in a manually separated script based on arguments.

[titouanmathis]

issue: I don't think it's the role of this package to initialize git. Maybe we would like to create a project without git (only to test a feature locally). Moreover, it really depends on user access on repository.

I think that initializing Git is not out of scope for this repository. We can still create test projects locally with Git, it should not have an impact on a test.

I can remove adding the origin as it is the action that could change between projects.

suggestion: Maybe this script should be run in a manually separated script based on arguments.

We might as well just do a git init command 😉