1. ACF as an architecture tool, not just a plugin
ACF is not only a way to add custom fields. It is a way to define how clients manage site content. Every field created has an impact on the editing experience: how easy it is to understand, how easy it is to get wrong, how long it takes to update a page.
Before opening the ACF interface it is worth answering three questions: what does the client edit, how often and with what level of technical familiarity. Those answers shape every decision about field types and group structure.
2. Field types and when to use them
ACF offers many field types. The ones most commonly used in agency projects:
| Field | When to use it |
|---|---|
| Text / Textarea | Titles, short text, descriptions without formatting |
| WYSIWYG Editor | Longer text with formatting: italic, links, lists |
| Image | A single image with alt text and defined proportions |
| Gallery | Multiple images in a section (slider, photo grid) |
| Select / Radio | Choices from predefined options (background color, section layout) |
| True/False | Toggle to show or hide a section |
| Relationship / Post Object | Linking one item to another (related articles, products) |
| Options Page | Site-wide data: phone, address, social links, footer text |
3. Repeater, Flexible Content and Group: when they are actually needed
The Repeater allows adding repeatable rows — for example a list of services with icon, title and text. It works well when the number of items is variable and the client needs to add and reorder them independently.
Flexible Content is ACF's most powerful component: it lets you build a page by composing layout blocks in any order. It requires more development work and can become hard to manage if too many layout variants are added.
Group gathers related fields into a single panel. Useful for keeping the backend organised without structures more complex than the project needs.
Practical rule: Flexible Content makes sense only when the client genuinely needs to build pages with variable layouts. For most pages, a Repeater or a set of simple fields is enough.
4. ACF Blocks vs native Gutenberg blocks
With ACF 6 you can register Gutenberg blocks that use ACF fields instead of block editor markup. This keeps the editing interface within ACF even on sites that use Gutenberg.
ACF Blocks make sense when the team is already comfortable with ACF and wants a consistent experience, when blocks have complex layouts the native editor handles poorly, or when the client needs a simpler editing interface than the default Gutenberg one.
Native Gutenberg blocks are the better fit when the project uses Full Site Editing (FSE), when the team wants to follow WordPress's natural direction without extra dependencies, or when the design uses simple patterns that core blocks already handle well.
5. Structuring ACF for long-term maintainability
A frequent mistake: creating field groups with generic names like 'Section 1' or 'Page Data' that mean nothing to whoever reopens the project six months later.
Practices that reduce confusion over time:
- Name groups descriptively: 'Hero - Homepage', 'Service Cards', 'Footer - Contact Data'.
- Use the Instructions field to document required format, image dimensions or maximum text length.
- Export ACF configuration as JSON inside the theme so it stays under version control.
- Avoid multiplying groups: one well-organised group is worth more than five small ones with three fields each.
Frequently asked questions
Is ACF compatible with Gutenberg?
Yes. ACF 6 introduces ACF Blocks that integrate with Gutenberg. ACF can also run in parallel with Gutenberg: some content through blocks, other content through ACF meta boxes in the backend sidebar.
Is the ACF Pro version needed?
It depends on the features used. Repeater, Flexible Content and Options Page are Pro features. For simple fields the free version is enough. For most agency projects, Pro is worth the cost.
How do you sync ACF configuration between staging and production?
ACF supports JSON-based sync. With the right configuration, field groups are saved as files inside the theme and move between environments as part of the deploy.
Next step
Working on a WordPress project with complex content to structure?
I can help define the ACF field architecture and implement it alongside the team.
Talk about the project