Client wants custom fields behind posts or pages, what's the clean way.
Advanced Custom Fields (ACF) is the standard. For pure devs, Meta Box or Carbon Fields are lighter, but ACF wins on usability and editor UX.
Try this first
- 1Map data per content type: which fields a case study has (client, service, period, photo), a team member (role, bio, photo), a service.
- 2Create Field Groups in ACF, one per content type. Use Repeater only where it's true repetition, not as a hidden page-builder.
- 3Render fields in templates with get_field() or the_field() in PHP, or via blocks if you use Gutenberg.
- 4ACF Pro adds Repeater, Flexible Content and Options Pages. SMBs with more than two content types tend to recoup the license.
- 5Version Field Groups via local JSON: set ACF to Save and load JSON so field definitions land in Git. Keeps staging and prod synced.
- 6Test on staging before pushing to production. Forgetting or misconfiguring ACF fields loses data.
When to bring us in
Building a complex content model (relations across ten types, conditional fields, nested repeaters)? An experienced WP dev avoids data-modelling mistakes.
See also
- WordPress, plugins and theme have gone 6+ months without updatesOut-of-date WP is the number-one entry for malware. Don't just hit 'update all', back up first.
- Theme update broke the layout or threw a fatal errorThemes overwrite custom CSS on update unless you use a child theme.
- WordPress shows a blank screen after a plugin install or updateWSOD (white screen of death) is usually one crashing plugin. You isolate it.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.