Turn AI-assisted site drafts into maintainable WordPress composition.

PromptingPress is an open-source AI-first WordPress theme. It gives small WordPress teams a bounded page-composition layer: AI can draft sections, humans can inspect props and style slots, and changes can be validated and screenshotted before review.

promptingpress runhome / draft
brief lockedprops boundedreview frame
prompt: turn agency brief into WordPress composition
output: sections, props, validation evidence
01Brief becomes a page map.
02Lightweight sections keep editable props.
03Inspect, validate, screenshot before review.

AI speeds up the first draft. Agencies still own the mess after launch.

agency cost surface
first draft speed / revision debt / review path

01 / draft speed

The page appears done quickly.

Then the agency inherits unclear structure, scattered styling, and a page that is hard to inspect.

02 / client revision

The next change exposes the cost.

Speed is not enough if every update creates handoff debt, builder bloat, or fragile one-off sections.

03 / PromptingPress path

Make the next edit reviewable.

WordPress sections, component props, style slots, validation, and screenshots stay in the workflow before changes are treated as done.

Files own the design. WordPress owns the content.

composition boundary
theme files / WordPress data / validated edits

01 / files own design

The repeatable system stays in the theme.

Templates, components, tokens, CSS, spacing, and rendering rules stay maintainable instead of being scattered through generated markup.

02 / WordPress owns content

Pages stay editable as page data.

Copy, section order, and component props live in WordPress composition data, so client-facing pages can be inspected later.

03 / AI edit boundary

Agents get a bounded map of what can change.

Components, props, style slots, validation, preview, and screenshots define the review path before work is treated as done.

adoption record

The two adoption reasons: speed and trust.

Speed gets the first draft moving. Trust is what keeps the next revision safe to review.

  • 01 Speed: Lightweight performance

    Client sites should not need a heavy visual-builder runtime just because AI helped produce the page. PromptingPress keeps output close to plain WordPress, PHP, CSS, and small JavaScript.

  • 02 Trust: AI-safe structure

    The next agent pass should not guess through hidden state. Pages expose components, IDs, props, and style slots so edits can be inspected, validated, and reviewed.

  • 03 Trust: Readable handoff

    Agencies can explain what was built, where content lives, and how future changes should happen without handing clients an opaque AI artifact.

  • 04 Trust: Safer revisions

    Preflight checks, screenshots, and rollback-aware actions make AI-assisted updates easier to trust on live WordPress work.

review path

The split keeps AI work commercially maintainable.

The first draft only matters if the next change is still inspectable, explainable, and safe to hand off.

maintainability record
first draft / next revision / client handoff

00 / commercial rule

Optimize for the work after the generated draft.

Most AI website workflows optimize for the first page. PromptingPress keeps the next revision, client change request, page expansion, and post-launch handoff inside a reviewable WordPress composition path.

01 / files

Design remains the system of record.

Templates, components, tokens, spacing, and CSS stay in files instead of being scattered through generated output.

02 / WordPress

Content stays inspectable.

Copy, section order, and component props live in structured WordPress composition data that an implementer or agent can inspect later.

03 / review

AI edits leave evidence.

The agent can inspect the page, edit bounded props, validate the result, render screenshots, and leave a trail before work is treated as done.

Get the open-source PromptingPress theme.

PromptingPress is available on GitHub for WordPress teams that want an AI-first theme built around inspectable composition, bounded edits, validation, and review evidence.

View theme on GitHub