NeoCMS 3.0 · Open source
Controlled visual editing for the static website you already have — with drafts, revisions, publishing, media and SEO tools, while public pages remain ordinary HTML.
NeoCMS adds a private administration layer to an existing static website. Mark the regions people may change, and authors get a visual editor instead of a source file. The public site keeps serving the same HTML it served before.
There is no database to provision, query or keep in step with the files. Drafts, schedules, revisions and operational records live on the filesystem beside the site, under paths that the supplied server rules keep private.
NeoCMS is for teams that need controlled content editing without rebuilding a working site around a heavyweight platform.
Publishing updates an ordinary HTML page. Visitors do not wait for a CMS database, a theme engine or a page-builder runtime before they can read it.
Add one configurable class to a region and NeoCMS makes it editable. Leave the rest alone and the layout, scripts and components stay in the hands of the people responsible for them.
Editing the browser preview does not quietly change the live page. Authors save drafts; publishers review, publish immediately or schedule the change for later.
Every changed or deleted page receives a timestamped filesystem snapshot. Publishers can inspect the history and restore an earlier version when a release needs undoing.
The authoring tools teams expect, fitted around the files they already own.
Visual editing
TinyMCE opens only the regions carrying the configured editable class. Repeatable blocks can be cloned or removed without exposing the surrounding template.
neo-dupe blocksDrafts & publishing
Save private work without touching the public page. A publisher can release it now or schedule it for a specific time, with a CLI worker available for unattended publication.
Pages
Search, create, duplicate, rename and delete editable HTML pages, including pages in subdirectories. Templates keep new pages consistent with the rest of the site.
Media
Browse uploaded images, reuse them, keep their alternative text, see where they are used and remove files that no page still needs.
SEO
Authors can maintain the title, description, canonical URL, Open Graph image and robots indexing choice without hunting through the document head.
Shared content
Mark a region with a shared key and update every matching page together. Build ordered, nested navigation menus and insert the generated markup into an editable region.
Preview & accessibility
Preview at desktop, tablet and mobile widths, then check common authoring problems: missing alt text, empty links, heading jumps, absent labels and missing page metadata.
Roles & activity
Editors prepare content, publishers release and restore it, and administrators manage pages, media, shared content and menus. The dashboard keeps drafts, schedules, problems and recent activity visible.
Operational safety
Password hashes, expiring sessions, login throttling, request and storage quotas, private data paths, security headers and owner-only files give a simple deployment sensible boundaries.
NeoCMS does not ask you to translate a site into a proprietary theme or component language. Add the CMS directory, mark the regions people may edit, and keep deploying the same HTML, CSS and JavaScript you understand today.
A deliberately short installation path, with the important permissions and credentials made explicit.
Put cms/ and uploads/ in the document root of the existing PHP-hosted website.
Create the untracked local configuration, add password_hash() credentials, assign roles and confirm the required paths are writable.
Add the configured editable class to each region an author may change. Add neo-dupe where a whole block may repeat.
Open /cms/, edit visually, save a draft and publish when it is ready. The live result is still the site's original HTML page.
01You already have a fast static site that does not need rebuilding.
02Authors need to change words and images without touching HTML.
03You want review, scheduling and rollback without a database service.
04Your developers need firm boundaries around what editors may alter.
05You prefer files that can be backed up, diffed and moved with the site.
06You want open-source code you can inspect, adapt and host yourself.
No. It is designed to sit alongside an existing static site. Your public pages remain ordinary HTML, CSS and JavaScript; NeoCMS adds the authenticated editing and publishing layer.
Yes. Drafts, revisions, schedules, metadata, activity logs and configuration are stored on the filesystem. Back up cms/data/ with the website, and deny direct web access to the CMS data and log directories as described in the documentation.
Only the regions carrying the configured editable class. The default is editable, but it can be changed to any valid single class name. Repeatable blocks use the separate neo-dupe class.
Yes. Editors save filesystem-backed drafts without changing the public page. Publishers can then publish immediately, schedule publication, inspect previous revisions and restore an earlier version.
PHP 8 on Linux, the PHP DOM and fileinfo extensions, PHP sessions, a modern JavaScript-enabled browser, and write access to the managed HTML files plus the CMS data, log and upload directories.
NeoCMS is open-source software licensed under GPLv3. You may use, study, modify and distribute it under that licence; the repository includes the complete licence terms and project documentation.
Independent products, built because they should exist.
4ensics Leviathan
A browser-based binary analysis, reverse-engineering and digital-forensics workbench that keeps artefacts local.
See LeviathanBlackwall
Passkey-only identity, standards-based integration and an audit trail designed to prove it was not altered.
See BlackwallFury
A documented format, a Go library and tools for material that must stay unreadable after the mathematics moves on.
See FuryNeoCMS is available now under GPLv3. Download the complete source, installation guide and technical documentation from GitHub.