SchemaPress is a structured content system for WordPress, giving teams the modeling discipline of a headless CMS without leaving the platform their site already runs on. You define a collection type — a named shape with typed fields — and the plugin gives you an admin for filling it in and a REST API for reading it back. If you know Strapi, you know the model, living inside WordPress instead of beside it.

Underneath it is still WordPress. Entries are stored as posts, so existing queries, capabilities, and backups keep working. A whole entry's values live in a single JSON blob — the right shape for reading a record, the wrong shape for querying across a collection — so a derived index mirrors every scalar into its own meta row where SQL can reach it. The blob is the record; the index is rebuilt on every publish.

The plugin deliberately renders nothing. A collection describes what content is; what it looks like stays the theme's business. Three delivery surfaces sit over one shared query grammar — a PHP API for themes, Twig functions for Timber, and the opt-in REST API — so a filter means the same thing in a template as it does in a URL. The admin's transport is separate and capability-checked, so editor changes can never widen what the public can read.