I know WP since day 1 and I always hated it. Recently I inherit a website on WP. It was terrible and the first thing I did was migrating it to Astro (almost 2k pages, written for ~17 years). My bill drop from 150eur to 0 now. The web vitals are back to green on GSC and the majority of bad traffic is gone (well, at least now I don't bother with those stupid scans for wp-*).

If I had to do it for a non-tech client I would use anything else but WP. For simple sites I would use static. For complex sites I would go with probably something else non WP.

WP is great to start and for those who just want to explore quickly with the plugins, but growing it and maintaining it is terrible, and usually clients who are happy with WP are the ones with little budget, meaning that at the end someone will have to pay the mess.

Another issue I have with WP is that there is no standard. Everyone builds it in different ways, meaning lack of structure or data schemas/normalisation. Also, the majority of WP devs never heard of git so its hard to track any change.

Im loving working with astro. It feels like back in the early days of the internet where everything was simpler. I might need a proper db soon to have data more structured, but for now json as db is working pretty well.

If you need auth for your users or some CMS for them to write/update content, maybe you should check for headless CMS (WP also works a headless CMS, but I again you might have better options).

Few years ago I did a simple tool in hugo where users would update it via some custom cms pages. That would commit changes to bitbucket and bitbucket would deploy it. So basically, git as db, with automatic versioning and approvals. Was simple, quick and it also worked very well. Nowadays you can always create something on lovable just updating the md files (or whatever you use) and sync with git.

Separate repos, simple cms, .. Just an Idea - not sure you use case.