Aumframe

Aumframe is a visual editor built around one idea: you design a template, and the template decides which pages it draws. Give it a rule — the front page, every post in a category, single products, search results, 404 — and every page that matches is laid out by that one design. Change the design once and all of them change.

Layout is done with frames and relational sizing rather than fixed columns, so a row can say “this part takes the space that is left” instead of “this part is 480 pixels”. The same design holds together at phone width without a separate mobile version to maintain.

What it gives you:

• Templates by rule — front page, singular, archive, taxonomy term, search, 404, plus per-slug rules and a priority when two rules could both match
• A shell with a slot: the header and footer you design once, with each template’s content dropped into the slot
• Reusable components — build a card once, place it anywhere; editing the component updates every instance
• Dynamic data — bind text, images and links to the post, term, author, meta field or query being shown, so one design fills itself from content
• Loops — a row that repeats over a query, with the query written in the editor rather than in code
• Motion — entrance, scroll-linked and looping animation, compiled to the same output the front end uses
• Revisions on every design, with a read-back check so a save that did not land is reported instead of silently lost
• Per-language variants of a design, for sites running a translation plugin
• Kits — export a whole site’s designs, content model, components and media as one file, and import it into another site

Aumframe does not render your designs on every page load. The layout is compiled to HTML and CSS in the browser when you save, and PHP only fills in the dynamic parts. There is one compiler, in one language, so what you see while editing is what visitors get.

Where it stores things

Four tables of its own: aumframe_templates, aumframe_revisions, aumframe_template_i18n and aumframe_components. Your posts, pages and media stay where WordPress keeps them — Aumframe reads them, it does not move them.

WP-CLI

• wp aumframe import <file> — import a kit
• wp aumframe kit-requires <file> — print what a kit needs before you import it

Build

The front end runs the source directly; nothing about it is compiled. The editor is bundled because it is written with JSX, and because one file means one ?ver= to invalidate.

Everything needed to rebuild it ships inside this plugin — packages/core/src, packages/editor/src, packages/runtime/src, build.mjs, package.json and package-lock.json. From the plugin’s own folder:

npm ci && node build.mjs

That writes three files, and the build is deterministic — the same source and the same lockfile give byte-identical output. For this release, sha256:

• assets/editor.js — acb7f130204650a0a9a53f02986362b282ae0343d68eed92a7a4ad143a2bd586
• assets/motion.js — 1992377aa2274be47ce353652169f659032f020694eeb4b84c4048136771b637
• assets/editor.css — 125b366178f856065f4e11bf283cade2182cc09a93c528db1e6ba1e0502de313

Built and checked with Node 24 and esbuild 0.25. The other files in assets/ are written by hand and are not build output.

npm test runs the core, schema, style, editor-store and renderer suites, plus a regression that re-bakes the templates of three frozen reference sites and requires the output to be byte-identical.