A website framework your AI app can read and maintain.
webspine is a small PHP foundation for building and running your own website with an AI app. It works best with Claude Code connected to your server. The code lives in your project folder, and you can change any part of it.
site/themes/Layout, templates, CSSsite/plugins/Forms, data, integrationscore/Routing, storage, updates
Built with HTMLCSSJavaScriptPHPSQLite
No npm, no Composer, no build step.
What a new site already has
Database
SQLite storage for the information your website needs, set up on install.
Contact form
Visitors can write to you. Messages are saved first and then sent to your inbox.
Simple analytics
Page view counts without cookies or tracking of individual visitors.
Works best with Claude Code, connected straight to your server.
Add your server as an SSH connection in the Claude desktop app. Claude then works in the website folder on the server itself, so there is nothing to upload when you are done.
Other AI apps that can edit project files work too. With them you usually build on your computer and publish in a separate step.
- Add your server as an SSH connection
- Describe what the site is for
- Open your domain and ask for changes
Need hosting for your site?
Plain files in clearly named folders.
Every part of the site has one obvious place, so an AI app can find what it should change and leave the rest alone.
webspine is an open-source foundation for building and maintaining a website with the AI app of your choice. Content, themes, components and plugins are kept apart, which helps the AI keep the code organised.
Use any AI app that can work with your project files, such as ChatGPT Desktop, Claude Code or OpenCode. The code belongs to you, and you can keep developing it without waiting for new webspine releases.
It is written in plain PHP, HTML, CSS and JavaScript. There is no frontend framework, no Node.js runtime and no build step, so it runs on any PHP web server with SQLite.
Read the principlesCode your AI can follow
Plain PHP and browser-native code in a predictable structure, so your AI can understand the project and make focused changes.
Updates leave your site alone
Themes, plugins and content live outside the core. Updating the core does not touch your design or your text.
You own the code
You and your AI can maintain and extend the site without depending on future webspine releases.
How a webspine site is organised
The core handles routing, storage and updates. Everything that makes the site yours sits in site/. Choose a folder to see what is inside.
// Templates and styles for one theme
site/themes/
your-theme/
theme.json ← identity & API
layout.php ← shared structure
home.php
assets/
style.css
app.jsA theme can change any markup without touching the core.
// Editable text, kept out of the templates
site/content/
home.php ← default entry
en/
home.php ← English text
de/
home.php ← German textChange the wording without touching the layout. This site keeps its translations in en/ and de/.
// Each plugin declares what it needs
core/plugins/
sqlite/ ← storage provider
smtp/ ← mail provider
site/plugins/field-notes/
plugin.json ← dependencies
plugin.php ← routes & hooks
$app->services->get(Pages::class);Plugins ask for a service by its interface. The configuration decides which provider answers.
// Framework code, replaced on update
core/
bootstrap.php
src/
Contracts/ ← service interfaces
Router.php
Registry.php
Theme.php
Updater.phpA core update replaces core/ and keeps site/, config/ and storage/ as they are.
Themes and plugins talk to the core through documented interfaces. Read about the architecture
Start with one prompt
Copy this into your AI app and replace the part in brackets. The guide explains which apps work and how to publish the result.
Open the guideBuild me a website using webspine.org.
Read https://www.webspine.org/docs#technical-reference.
My website is for: [your idea or business]
Show me a preview so we can refine it together.Your AI reads the docs, sets up the project and shows you a preview.
What works today, and what is still missing
Routing, SQLite storage, themes, plugins, SMTP mail and reversible local core updates are in place.
Content editing in the browser, user accounts, more database providers and signed online updates are not built yet.
See the full status