> Does anyone have recommendations for learning Wordpress if you already experienced with modern practices like GitOps and immutable deployment artefacts (containers/VMs) using more fully featured frameworks like Django and Rails, which have abstractions like ORMs and Migration frameworks to look after all your database changes
Personally, I think trying to apply modern development practice to wordpress development is a waste of time. You're going to fight an uphill battle. Instead, just treat it as a legacy platform and use legacy development methodology: have at least two or three copies of the site (dev, staging and production). Use sftp to live edit the code on dev/staging, then copy to production regularly. Make sure to have a versioned daily backup in place which at least can pull the last 7 days daily backup and the last 6 months monthly backups, and you're set.
If your app is getting too complex for this development method, you can always switch back to django or other modern frameworks with modern tooling.
I don't see why this would preferred over using something like vvv [0] to develop locally and then pull changes from a repository to a production site. That's how I've been doing it for my personal site and it works like a charm.
I agree with this approach. Fortunately, there are managed services specifically for Wordpress that handle all this stuff. Cloudways, WPEngine, there are several others too. Cloudways lets you set up and manage WP using Digital Ocean, Vultr, AWS or GCP if I recall.
Personally, I think trying to apply modern development practice to wordpress development is a waste of time. You're going to fight an uphill battle. Instead, just treat it as a legacy platform and use legacy development methodology: have at least two or three copies of the site (dev, staging and production). Use sftp to live edit the code on dev/staging, then copy to production regularly. Make sure to have a versioned daily backup in place which at least can pull the last 7 days daily backup and the last 6 months monthly backups, and you're set.
If your app is getting too complex for this development method, you can always switch back to django or other modern frameworks with modern tooling.