WordPress is the right base layer. Everyone keeps wrapping it.
WordPress ships authoring, auth, roles, scheduling, taxonomies, search, and a twenty-year content model. The dominant builders all react by wrapping that base layer in their own runtime, their own database shape, or their own black box. Atlas is the lean alternative: one block, one manifest, one render path.
Three ways WordPress users are currently asked to scale.
Each path solves the immediate problem and creates a larger one: a runtime to maintain, a vendor to trust, or a second stack to host. Atlas refuses all three.
- 01 Page builders wrap WordPress in a runtime.§ Elementor / Divi / Bricks / WPBakery.
- 02 AI builders wrap WordPress in a black box.§ 10Web / Hostinger AI / Wix AI.
- 03 Headless detaches from WordPress entirely.§ A second stack to feed and host.
One manifest in. One block of HTML out.
The manifest is a JSON tree of section, heading, and prose nodes — stored as a single block comment
inside post_content. On render, the plugin walks the tree and emits HTML directly into
the response WordPress was already sending. Same input, same output, every request.
<!-- wp:atlas/manifest -->
"version": 1,
"sections": [
"type": "Section",
"tone": "clay",
"children": [
"type": "Heading",
"level": 1,
"text": "Page builders hold you back."
]
]
<!-- /wp:atlas/manifest --><section class="atlas-section atlas-tone-clay">
<h1 class="atlas-heading">
Page builders hold you back.
</h1>
</section>
<!-- 0 hydration. 0 inline scripts. -->
<!-- Plain HTML in WordPress. -->§ Same JSON in, same HTML out, every render. Determinism is the feature.
Three layers. Each one already exists.
Atlas does not introduce a new database, a new render server, or a new client runtime. Storage is post_content. Render is a PHP callback. Runtime is the absence of one.
- § STORAGE
WordPress.
The manifest is a single block comment inside post_content. No new tables, no custom post type, no parallel database. The post row is still the post row.
wp_posts.post_content - § RENDER
Server-side, on save.
The plugin parses the manifest and emits HTML when the post is rendered. Output lands in the same response WordPress was already sending. Cache plugins see plain HTML and behave normally.
render_callback (PHP) - § RUNTIME
None, by default.
Nothing hydrates in the browser unless a node is explicitly marked as an island. The page chrome ships zero JavaScript from Atlas.
0 bytes JS (default)
Atlas fails open, not closed.
Deactivate the plugin. Uninstall it. Update WordPress. The post body stays readable because the storage shape is the same shape WordPress has always supported.
- § PLUGIN ACTIVE
The block renders the manifest server-side, every request.
WordPress core sees a normal dynamic block. Editors see the Atlas pane.
- § PLUGIN DEACTIVATED
The last rendered HTML stays in the post body.
The block comment is preserved. Re-activate later and rendering resumes from the same manifest.
- § PLUGIN UNINSTALLED
Pages remain readable as plain HTML.
No white screens, no broken shortcodes, no orphaned database rows. The post degrades to its last known render.
- § WORDPRESS UPDATED
No theme rewrite, no migration, no shortcode regen.
Atlas talks to one Block API surface and the post_content column. Both are stable contracts in core.
Five things Atlas does not add to your install.
The shortest list is the product. Everything Atlas refuses to do is something WordPress already does, or something a wrapper would charge you to maintain.
- 01 Atlas does not add A second editor.§ Gutenberg is the editor.
- 02 Atlas does not add A second database.§ post_content is the store.
- 03 Atlas does not add A frontend runtime.§ No hydration tax by default.
- 04 Atlas does not add A theme replacement.§ Your theme keeps rendering.
- 05 Atlas does not add A shortcode dialect.§ One block, one render path.
Install it. Render the manifest. Keep your WordPress.
GPL plugin. WordPress 6.4 plus, PHP 8.1 plus. Activates as one block in the editor and renders deterministic HTML on every save. Read the manifest reference if you want the full schema before you install.
One block. Graceful degradation.