Traditional CMS workflows often separate the editing interface from the files that are actually deployed. That works well for large applications, but it introduces friction for smaller organizations that value simple hosting, easy backups, and long-lived static pages.
WYSiteIWYG takes the opposite approach. The HTML on disk remains the canonical version of the page, and the editor arrives as a thin authenticated layer inside /edit/. Logged-in users can move from browsing to editing without leaving the site itself.
Why that matters in practice
Small teams do not need to maintain a separate publishing stack, run scheduled exports, or remember whether the “real” content lives in the repository or in an admin database. They edit the page, save it, and the page itself changes.
That model also keeps hand-edited markup, theme rewrites, and imported legacy pages in one understandable place. When something needs cleanup, source mode is available. When a page just needs a quick update, the block editor is enough.