A file-based CMS stores website pages or content in files you can inspect and move. VoxelSite uses AI to edit PHP pages and JSON content on your server. SQLite stores Studio accounts, settings, revisions, and metadata.
Pages, content, and shared files
A generated page is a PHP file such as index.php or about.php. Shared header, navigation, and footer partials keep repeated elements in one place. Styles live in CSS files and browser behavior in JavaScript. Business data can live in JSON files under assets/data/.
Collections also keep their field schemas and item data in JSON files. The Studio uses a SQLite index to manage them. Published PHP pages load their shared files and assets outside the Studio.
The file output documentation explains the directories and the boundary between the Studio and the public website.
Editing with AI
Describe the website or edit you want. VoxelSite writes the page files. You can then refine the result through chat, click-and-edit controls, the built-in code editor, or an external editor.
Review business facts, navigation, mobile layouts, accessibility, and forms before publishing. You can inspect and edit the source code throughout.
File-based and database-driven publishing
| Need | File-based approach | Database-driven CMS |
|---|---|---|
| Inspect and move pages | Copy and read the page files. | Move the application, content database, and assets together. |
| Large editorial workflows | Check the available roles, collections, and publishing tools. | Often a stronger fit when mature workflow extensions are needed. |
| Custom layout changes | Edit the generated markup, styles, and partials. | Use the theme, template, or component system. |
| Backups | Back up site files and any Studio or form databases. | Back up the application, database, and uploaded files. |
Speed and security depend on images, scripts, templates, server configuration, and maintenance. Self-hosted WordPress also gives you source access and hosting control, with publishing tools and plugins for larger content workflows.
Running the website without the Studio
VoxelSite’s published PHP pages use shared partials and assets outside the Studio. Removing the Studio removes the editing interface and its management tools; the website files remain. In an installed site, the form handler and submissions database also live outside the Studio.
ZIP downloads have a separate standalone form handler with fewer features. Static HTML can run without PHP, but server-side form submission still needs a PHP-capable host or a service you configure. The code export guide explains that distinction.
Websites that suit VoxelSite
Consider VoxelSite for business websites, portfolios, landing pages, and content sites with AI editing and source access. Check its collection and publishing tools against your needs. Ecommerce, complex applications, and large editorial teams need a closer feature review.
Compare VoxelSite and WordPress, then use the demo to see whether file-based editing fits your work.