cpt-forge · content models

g cpt

Fields that bake themselves into a plugin you keep

Post types, taxonomies, field groups and options pages, built in the admin and compiled into a standalone mu-plugin. Delete the builder and the content model keeps running.

40

Field types

AND/OR

Location rules

mu

Bakes to plugin

git

Plain PHP out

01 — No lock-in

One button turns definitions into a portable mu-plugin.

The report says exactly what went in. The result is ordinary PHP on WordPress APIs: readable, committed to git, deployed to production without the builder installed.

Output

mu-plugin, plain PHP

Needs builder

no

Bake report

types · taxonomies · groups

02 — Rules you recognise

The ACF idiom, with values offered as lists.

Post type, page template, taxonomy, user form, options page. AND inside a group, OR between groups — and each field shows the get_field() call to copy.

get_field('service-details')

03 — What the client sees

A form an editor fills without instructions.

Labels, hints and repeaters instead of raw meta keys: number, price chip, typical range, a note and an Includes repeater.

04 — Fields to page

g box blocks pick fields from a list, not from memory.

The service cards read that same field group — the 01, the “from $189” chip and the bullet list all come from g cpt.

compared with what you use now

topic

acf pro / pods

g cpt

If you remove the builder

Fields disappear

Baked mu-plugin keeps working

Version control

Export JSON, import by hand

Plain PHP plugin in git

Field slugs in blocks

Typed from memory

Picked from a list

Location rules

Rule builder

Same idiom, values as lists

Field types

Core set plus add-ons

40 including repeater and flexible

questions

g cpt · straight answers

What do I keep if we part ways?

The baked mu-plugin. It is plain PHP in your repository and runs without anything of ours installed.

Is the baked plugin editable by hand?

It is ordinary PHP calling WordPress APIs, so yes — though re-baking overwrites it.

Can you import from ACF?

Not today. There is no migration path from ACF, Pods or Meta Box.

next

g box