Question Recommended AI / Git Workflow for WordPress Development on Plesk?

[Alfrules]

Our development team is increasingly using AI-assisted development tools for WordPress sites, and I’m trying to determine what the best workflow looks like when hosting those sites on Plesk.

The main goal is to allow developers to work locally using tools such as Claude Code, Cursor, etc., while still allowing clients to use WordPress normally to update pages, posts, media, menus, and other content.

My assumption is that Git should probably sit somewhere in the middle, with developers managing the custom theme/child theme and possibly custom plugins through a repository, then deploying those changes to the Plesk-hosted WordPress site.

Something along the lines of:

Developer / AI tools → Git repository → Plesk deployment → WordPress

While the client continues making content changes directly within WordPress.

Where I’m less certain is what people consider the optimal setup in practice.

For example:

• Should only the theme/child theme and custom plugins be managed through Git?
• Is Plesk’s built-in Git deployment generally the best approach, or are people using GitHub Actions or another CI/CD process?
• How do you avoid developers accidentally overwriting changes made through WordPress?
• Are there particular problems with page builders, ACF, theme settings, or plugins that store configuration in the database?
• Is there a better workflow entirely for AI-assisted WordPress development that still keeps the CMS usable for clients?

Ultimately, I’m looking for a setup where developers can freely use modern AI coding tools and version control, while WordPress remains WordPress from the client's perspective.

I’d be very interested to hear what workflows other Plesk users are using successfully, particularly for sites that continue to be actively maintained by both developers and clients.

Any input, examples, or lessons learned would be greatly appreciated.

Thanks,

Tim