Insights Website Ownership
What are Advanced Custom Fields, and why do we use them?
3 min read
There's a difference between owning your website and having to rebuild it every time you edit it. Structured fields are how a custom site stays easy to update and hard to break, explained without the developer vocabulary.
You probably don’t want complete control over every part of your website.
That sounds strange coming from someone who believes strongly in website ownership.
But hear me out.
You should absolutely have ownership.
You should have access.
You should be able to update the business information your team is responsible for.
But do you really need the ability to accidentally:
Move the headline twelve pixels.
Delete half the homepage.
Change every font.
Break the mobile layout.
Remove the spacing system.
Turn one button green because someone “thought it would pop”?
Probably not.
There’s a difference between owning your website and having to rebuild your website every time you edit it.
ACF separates content from layout.
Imagine a team member page.
You might need to edit:
Name.
Job title.
Biography.
Photo.
Email.
Credentials.
Those are content fields.
Your team should be able to manage them.
But they shouldn’t necessarily need to edit:
- Grid structure
- Typography
- Mobile breakpoints
- Image cropping behavior
- Spacing
- Component layout
Those belong to the design system.
Advanced Custom Fields lets us separate the two.
Your team sees what it actually needs.
Instead of opening a page and seeing a giant visual builder with dozens of nested containers, you may see something like:
- Hero headline. A text field.
- Hero copy. A text area.
- Featured image. An upload.
- Primary call to action. A button label and a link.
That’s much easier to understand.
And when the client experience is designed intentionally, the WordPress dashboard starts feeling less like a generic CMS and more like the backend for this specific business.
Structured content becomes especially powerful as the site grows.
Suppose you have fifty case studies.
If each one is built manually inside a visual page builder, consistency becomes harder.
But if each case study contains structured fields like:
- Client name
- Industry
- Location
- Services
- Challenge
- Strategy
- Results
- Testimonial
- Gallery
then every new project can feed the same strategic design.
That means:
You manage the information. The theme manages the presentation.
This is exactly the model we’re using for Meridian’s own Work and Insights content.
It also protects consistency.
A strategic website shouldn’t slowly become less strategic every time someone edits it.
This can happen when every page is completely free-form.
One person adds a new button style.
Another changes a heading size.
Someone copies and pastes a section from another page.
A year later, the website looks like five people built it.
Structured fields create useful guardrails.
The team still gets flexibility.
The brand gets consistency.
ACF isn’t what makes the website custom.
This is an important distinction.
ACF is a tool.
The custom part is the thinking behind:
- Which fields should exist
- Which content needs to be reusable
- Which layouts need flexibility
- Which things should remain locked
- How the theme displays that information
- What the business will realistically edit
The goal isn’t to say:
We use fancy development tools.
The goal is:
We designed the editing experience around how your business actually uses the site.
The Meridian perspective
Clients shouldn’t need to understand web development to update their website.
If you’re changing a testimonial, you should edit a testimonial.
If you’re adding a project, you should add a project.
If you’re updating an employee, you should edit the employee.
You shouldn’t need to understand how the page was coded underneath.
Good custom development hides unnecessary complexity from the person who doesn’t need it.