Documentation
Stride's guides ship with the source. While the main repository is private before 1.0, the command line is the quickest way in: every command answers --help with its options and examples.
The visual editor and the admin
Applying themes, the package format, making one
Writing a plugin, the plugin kits, the permission model
Routes, errors, and building a site with curl
Connecting Claude and other models over stdio or HTTP
Scopes, built-in and custom roles, site access
Backup, restore, upgrades and running as a service
Building and serving Git repositories
One guide per hosting provider
The command line
stride serve
Start the server: pages, the editor at /admin/, the API and MCP
stride doctor
Check this machine and its configuration, with a fix for each issue
stride backup <file>
Write a consistent snapshot of the database while it runs
stride restore <file>
Put a snapshot back
stride mcp
Serve the Model Context Protocol over stdin and stdout
stride plugin new <id>
Scaffold a plugin in Rust or TypeScript
stride theme new <id>
Scaffold a theme that passes validation
stride update
Install the newest release over this binary
Open registries
Read the source of every plugin and theme, see how releases are signed, or send your own.
Install Stride, open the admin, and publish a page in the time it takes to read the WordPress system requirements.
$ npm install -g @guuslab/stride