WordPress Packagist VS bedrock

If I have to use WordPress for something, I'll build it as a standard PHP project, requiring WordPress and any themes/plugins as a Composer dependencies from johnpbloch/wordpress and WordPress Packagist (more info here). If I need to do any significant templating, I like to use Timber.

Use it together with https://wpackagist.org/ and you can update all plugins/themes by latest or by version number.

Another option you can look at is Bedrock by Roots - that is sets WP as an app with composer already set up. It allows you to install WP plugins (from official WP repo) via composer (WP Packagist). The structure is set up to allow for git workflow. Also helpful if you want to make use of a bunch of composer packages on your site.

https://wpackagist.org/ in the example you see "repositories", now in that array you can put your plugins github-link and set the other settings. with composer install you install them and with composer update you update them

Side question: I know that the WordPress ecosystem has been moving toward better support for Composer – e.g., with WPackagist. But wouldn't plugins installed/updated via Composer run into the same issue?

There are ready-made boilerplates like Bedrock and Sword but, at an architectural level, I'm not a fan of any I've seen.

Node (within the docker container) to build theme assets, composer to manage WordPress core + plugins and other dependencies. I built something similar to Roots for project boilerplate, custom starter theme and in-house mu-plugin within it.

Is this any good? https://roots.io/bedrock/ for a plugin?

As I only really use it for keeping stuff up to date, I'm looking at using Roots Bedrock for my next project. I'll then be keeping everything up to date via composer.

What advantages does WordPlate have over Bedrock[1], some of whose packages WordPlate also uses?

[1] https://roots.io/bedrock/

Probably looking for a https://roots.io/bedrock/

WordPress on containers is a very different beast if you actually want to use any of the advantages of containers. You probably need to figure out how to run upgrades by building a new image and not with the WP installer (which you need to disable to not have sudden version rollbacks). You probably want your plugins managed by compose and not a user. You probably want an S3 plugin for media. In fact, you probably want Bedrock. This is not a "single day task", just taking in the requirements and design phase is easily a day or two.

I'd strongly advice using Bedrock ( https://roots.io/bedrock/ ) and possibly even Sage

No, as far as I know it’s not that easy to accomplish with WordPress. You can use Bedrock (https://roots.io/bedrock/ ) as a Boilerplate for your development process. The Database can not be cloned to each environment that easily. Because every instance is working on it’s own. So if others want to work on their local machine they need a database dump which they have to setup manually on their machine. The only way that comes in my mind is to set up a development site that is accessible for every developer. You could then connect your local WordPress environment with the database from that development site. Everyone would than be working in the same database and everybody could see the changes someone else is making. But I think that wouldn’t be best practice but could be an option.