File output & ownership

VoxelSite generates PHP pages, shared partials, CSS, JavaScript and data files you can inspect and edit. Some server features use Studio code; check those dependencies before moving or deleting files.

The generated files

When VoxelSite builds your website, it creates:

Pages

Draft pages are PHP files under _studio/preview/. Publication places them at the live root or in nested folders. For example:

• index.php - your homepage
• about.php - about page
• contact.php - contact page
• services/design.php - a nested page

Pages use PHP include for shared headers, navigation and footers. Keep the included files when moving a page. Studio edits private draft files first; Publish applies the reviewed pages, partials and mutable assets to the live site.

Shared partials

Pages can share files in _partials/:

• header.php - the document from <!DOCTYPE html> through the opening <main>, including <head> and the body wrapper
• nav.php - the full navigation bar with responsive mobile menu
• footer.php - footer content, JavaScript includes, and closing tags
• schema.php - SEO structured data (Schema.org JSON-LD)

Stylesheets

Two CSS files in assets/css/:

• style.css - :root design tokens, keyframes, reveal transitions, navigation and mobile-menu structure, icon sizing and reduced-motion rules
• tailwind.css - Tailwind utilities compiled by PHP from classes in the HTML

Use Tailwind utility classes for visual styling. Keep resets, custom component classes and other overrides out of style.css.

JavaScript

Standard vanilla JavaScript files in assets/js/:

• main.js - scroll animations, sticky header, interactive behavior
• navigation.js - mobile menu toggle with z-index safety, icon hydration resilience, and close button injection
• icon-resolver.js - icon hydration (converts <i data-lucide> placeholders into inline SVGs from /assets/icons/)
• form-handler.js - client-side form validation and submission

The generated site uses vanilla JavaScript. Buyers do not need Node.js, npm or a build step.

Structured data

JSON files in assets/data/ that describe your business:

• site.json - core site info
• memory.json - private authoring facts, excluded from publication and export
• design-intelligence.json - private design context, also excluded from publication and export
• Additional files for menus, services, team members, etc.

SEO files

VoxelSite generates these files when you publish:

• sitemap.xml - for search engines
• robots.txt - crawler rules
• llms.txt - AI discovery map
• mcp.php - MCP server endpoint

Form handler

The installed submit.php handles schema-driven forms. It reads assets/forms/ and stores submissions in _data/submissions.db. Actions use a separate handler.

What happens if you uninstall VoxelSite?

Published pages and their included partials can run on PHP hosting. Removing _studio/ removes code for installed forms, actions and MCP action tools. Use Download & export to prepare a portable copy, then check its limits.

The installed submit.php loads classes from _studio/ through vendor/autoload.php. Keeping the root handler and database alone does not preserve the full form service.

Removing Studio also removes:

• The Studio admin panel
• AI editing capability
• The visual editor
• The undo system and snapshots
• The form submission management UI (viewing, filtering, exporting submissions)

Existing submission data remains in _data/submissions.db; keep a backup before changing the installation.

ZIP exports include a standalone submit.php for basic forms. It reads form schemas, validates fields and stores JSON submissions in _submissions/. Keep Studio for database storage, rate limits, uploads and SMTP. On Nginx, block web access to _submissions/ before accepting submissions.

Download your site

Click Download in the Studio status bar to choose PHP source or rendered HTML. Check Download & export for nested-page, asset and form limits.

Can I edit the files myself?

Open Editor or use Studio MCP to change the private draft. Review the current source before saving. Direct changes to managed published files produce a conflict on later publication; inspect and resolve them instead of expecting an automatic overwrite.

Publication tracks the files it owns. Unrelated files stay outside that managed set. The private workspace controls file access; authored PHP remains trusted server code, so edit permission is a powerful grant.

No proprietary formats

Your pages, styles and scripts are files you can open in a text editor. Studio settings and submission records use SQLite. Check server-side dependencies when moving the files to another host or CMS.