The client-editing excuse for WordPress is gone

For a decade the honest reason small clients stayed on WordPress was one sentence: "but the client needs to edit their own content." The plugin sprawl, the database and the monthly patching were tolerated because the alternative seemed to mean phoning the developer for every phone-number change. A demo shows client editing on a purely static site: page copy, images, global details such as the phone number, then publish and deploy.

• The category is real, not one niche tool: git-backed editors such as Decap, Sveltia, TinaCMS and Keystatic do this today, without a database.
• What you stop carrying matters more than convenience: no database to breach, no plugins to patch, no PHP runtime to keep current. Content is text in version control; publish is a commit.

• Static suits brochure sites. Shops, membership, multi-author editorial workflows still need a real backend somewhere.
• The client learns a new editor and someone owns the build pipeline; "no maintenance" is never quite true.

Source: Demo επεξεργασίας περιεχομένου από τον πελάτη σε καθαρά static site με στρώμα CMS (YouTube)