In reply to Rick Conlee.

headless WordPress will allow for a setup [..] where content can be stored in Git and generated on deploy?

That is not the idea here – headless WP still needs a web server to run.

From what I understand the idea is: The WordPress instance can be hidden and is usually not directly accessible from the frontend. So no more “attacks” on /wp-login.php, etc. Also: you can separate frontend and backend, meaning WP runs in a secret webserver somewhere (only known by editors) and when generating the static site, you deploy to another host (just as you do with Hugo/Jekyll/Nuxt), e.g. AWS S3 or Netlify.

The big advantage here is – in my opinion – that you can setup your WP so, that editors will love it. It will be a better experience for them than editing Markdown files in your GitHub UI explorer. In addition to that, since you can easily automate deployment, much less headaches of “can I update this or that plugin?” and more “oh, my pipeline broke because update X removed Y”.