MetaBox

What it is

MetaBox is a WordPress plugin that adds custom fields to any post type. Custom fields = structured data you control. Instead of forcing all your content into a single "body" text box, you define exactly which fields each piece of content has: a portfolio entry gets a client name, a live URL, a year shipped, a tech stack, a testimonial. The admin panel renders the matching inputs. The front-end pulls whatever you've stored.

If you've heard of ACF (Advanced Custom Fields), MetaBox does the same job. Lighter, faster, free where it counts.

How we use it

Every CPT gets a structured field group

The portfolio CPT on this site has fields for client, live URL, year, timeline, services, tech stack, testimonial, screenshots, and a half-dozen case-study-specific stats. A service_area has state, county, population, ZIP codes, drive time, primary industries, landmarks. A tool has status, one-liner, ETA. Each one is a separate field group, each one is its own file.

Field groups live in code, not the admin UI

Every field group is a PHP array in plugins/outerwave/includes/fields/{cpt}.php. We never click through an admin UI to define fields. They are code, they live in git, they deploy with the site:

plugins/outerwave/
  includes/
    fields.php                    <- loads all field groups
    fields/
      portfolio.php
      service.php
      service-area.php
      industry.php
      tool.php
      review.php
      stack-item.php              <- the one rendering this page

Moving a field, renaming an ID, or adding a new option = edit a file, commit, deploy. No production-only admin-UI changes that aren't in git. No "wait, where did this field go?" three months later.

Why not ACF

Advanced Custom Fields was acquired by WP Engine in mid-2022. The free version stagnated. The 2024 WP Engine vs Automattic feud took the entire ACF community hostage for a month while the plugin was forked, renamed, and re-released under contested terms. MetaBox is independent, profitable on its own, and the free version covers about 95% of what we need.

MetaBox Pro is worth it on the rare project that needs it

Most field types are free: text, textarea, number, checkbox, radio, select, image upload, WYSIWYG, post relationship. Pro (~$159/site lifetime, not yearly) adds the map field, repeater groups, conditional logic, and a clone field. We pay for it when a project genuinely needs those, which is roughly one in five.

What you get

• Custom admin panels that match how your business thinks about content, not how WordPress's default editor wants you to.
• Editing a page becomes filling in a form, not wrestling Gutenberg blocks.
• Data is structured. Search, filter, query, integrate. A portfolio can be queried by year or industry without parsing post_content.
• Field definitions live in git. Every change is reviewable, every rollback is one command.
• No vendor risk. The free version is fully featured for our patterns. Paid version (~$159/site, lifetime) exists if a project ever needs maps or repeater groups.

Where we don't use it

If a site is purely editorial (blog + about + contact + a couple of static pages), Gutenberg with reusable blocks is enough on its own. MetaBox earns its weight when content has structure: portfolios, services, locations, products, anything where the same shape gets created 20+ times.

For sites where the client wants to drag-and-drop layouts within a single page (the page-builder use case), MetaBox isn't the right tool either. We'd push back on that requirement entirely (see the WordPress page for why we don't ship page builders), but if a project required it, MetaBox isn't the answer.