Now available · Static site editing
WYSite puts a live editor directly onto your published HTML files — no CMS database, no deployment pipeline, no migration headaches.
Core Capabilities
WYSite's editing model is intentionally lean — built around the filesystem, not around a database that replicates it.
Click any editable region on your live page and start typing. Changes are written directly to the HTML file on disk — no preview environment, no sync step.
block-level · rich text · source modeThe editor reads and writes the actual published pages — not a detached copy in a database. What you see is what's live, always.
direct writes · no sync · no dbEdit the main navigation once and have it propagated across every page that uses it. Nested lists, styled by the active theme.
nested nav · theme-styled · one editPreview any registered theme against your live pages. When you're happy, apply it — all pages and templates are rewritten in one operation.
live preview · bulk rewrite · swappableBring unmanaged static pages into the current theme without rebuilding them by hand. Split any page into multiple independently editable regions.
migration · multi-region · no rebuildTag blog posts with #hashtags in the page metadata. WYSite auto-generates static tag-index landing pages — no dynamic query needed.
The editor lives at /edit/ — a single PHP file dropped into an existing host. Authenticated users get the editor; everyone else sees the public page.
Switch between the WYSIWYG toolbar and raw HTML at any time within the same editing session. Full control when you need it.
wysiwyg · raw html · per-block togglePost pages live at the root level and are indexed into tag archives automatically. Edit each post in place like any other page.
root-level posts · tag-driven · static outputDeployment Model
WYSite has no install wizard, no build step, and no database to provision. Upload one folder to any PHP-capable host, set your password, and your editor is live.
The public site stays as plain HTML files. Authenticated editors work against those same files — reads, writes, and theme operations all go straight to disk.
Read the full checklist →# Your existing site public_html/ index.html about.html blog/ my-first-post.html site.css # Drop in the editor edit/ ← new folder index.php ← the whole editor config.php ← your password + settings themes/ ← theme files live here # That's it. Navigate to: yoursite.com/edit/
Editorial Workflow
The whole cycle from visiting a page to publishing an update takes seconds — because there's nothing between you and the file.
Navigate to any page on your site as a logged-in editor. A subtle toolbar appears at the top of the page.
Click any editable region — a paragraph, a heading, a content block — to enter edit mode inline.
Use the rich-text toolbar or flip to source mode to edit raw HTML. Change text, links, images, or structure.
Hit Save. The editor writes the updated region back into the actual HTML file. The page is live instantly.
Why WYSite
Most CMSes move your content into a database and reconstruct your site on every request. WYSite keeps content where it already is.
The best CMS is the one that disappears — leaving you with nothing but your content and a save button.WYSite design philosophy · whatyou.site
Start Here
The philosophy behind the filesystem-first model and why it avoids the problems of a detached CMS database.
The full list of editing and publishing capabilities — from block editing and shared menus to tag archives.
A practical rollout checklist for getting the editor live on any PHP-capable shared host in minutes.
How editors update pages, menus, metadata, and posts in day-to-day use — the full editing lifecycle.
Previewing and applying themes, plus importing unmanaged legacy HTML into editable blocks.
Launch notes, workflow guides, and migration tutorials. Tagged with #launch, #workflow, #migration.
Drop the editor into /edit/ and start publishing in minutes.