Frontend Specialist for AI Automated workflow to make Presentations easily editable

Overview I publish presentation / landing-page-style decks online and need a clean, reliable way for non-technical colleagues and clients to edit them, mainly text and images, without touching code or breaking the layout. Edits should save to a single shared version so everyone sees the same up-to-date page live. Before any building happens, I want an expert to recommend the best approach. Scope of This Engagement This is consultation-first. The initial deliverable is your expert recommendation on the right architecture and tooling for the goal above, along with the trade-offs. If your recommendation is a good fit, there's a strong possibility of a follow-on build engagement to implement it, but the first priority is sound advice, not code. What I'd Like You to Advise On The best overall approach for making published, landing-page-style web pages editable by non-technical people. How to let users edit content only (text and images) while keeping the design, layout, and styling locked so they can't break it. Where the editable content should be stored, and how a single shared "source of truth" is maintained so everyone sees the same version. How edits get published and go live (instant vs. review/approval, draft vs. published states). Realistic cost: setup, any licensing/subscription fees, and ongoing running costs. Ongoing maintenance and reliability: how much upkeep this needs and who can do it. WordPress is one option I'm considering, but I'm open to others. Compare WordPress against the alternatives (e.g. headless CMS, inline/visual editing tools, page builders, SaaS deck/site tools, static sites with a lightweight editor) and tell me what you'd choose and why. Required Skills & Experience Strong front-end background (HTML, CSS, JavaScript) and an eye for keeping published pages pixel-stable. Hands-on experience building or configuring systems where non-technical users edit live web content. Working knowledge of multiple CMS / editing approaches, including WordPress and at least one headless or inline-editing alternative. Solid grasp of content storage, publishing workflows, and "single shared version" mechanics. Ability to weigh cost, maintenance, and ease-of-use trade-offs and explain them in plain language. Clear written and verbal communication; comfortable giving a straight recommendation. Nice-to-Have Experience with non-technical client handover and writing simple editing guides or documentation. Familiarity with image handling/optimization for web (uploads, sizing, performance). Exposure to access control / user permissions for editors. A portfolio of live sites or decks that non-technical people actively maintain themselves.