The component system behind every page we build.
ACF flexible content is the editing layer underneath every WordPress build we deliver for industrial companies: editors assemble pages from a defined set of components with defined fields, so a product range, a technical document library or a case reference can be maintained by the marketing team without a developer in the loop.
Generic page builders look flexible in a demo and come apart under real content: inconsistent spacing, broken responsive behaviour, a design that drifts a little further with every page an editor adds. A component system built in Advanced Custom Fields, scoped tightly to the approved design, avoids that failure mode by defining what a page can contain before anyone starts filling it in.
A component library matched to your design system, field definitions per component with sensible defaults, validation that prevents broken combinations, integration points where a component needs product data from an external system, and documentation so the next person to extend it stays inside the pattern.
For an industrial company the model is the interesting part: products and their variants, technical documents and their revisions, applications and the sectors they serve, case references, certifications and the relationships between all of them. Structured that way, a product page can list its own documents and related applications automatically instead of a marketing manager maintaining the same links in three places.
A B2B marketing team is usually one or two people who also run trade fairs, the newsletter and the product launch. The editing layer has to be obvious enough that someone returning after two months can add a product, publish a datasheet or write a case reference without asking. That constraint drives how many components exist and how each one is named.
Some components are entirely editorial. Others combine editorial fields with attributes read from a PIM, an ERP or a document management system, so a product block carries hand-written positioning copy alongside dimensions, materials and availability read straight from the system of record. Those components have to be defined with that split in mind from the start.
Each component is scoped to what the design supports rather than opened up as an unlimited builder. That discipline is what keeps the system dependable years after launch, when the people who signed off the design have moved on and the team maintaining the site has only the component set and its documentation to work from.
Code Industrial is the industrial B2B practice of Code Barcelona, an agency building corporate websites and digital platforms since 2015. The same strategy, design and engineering team works on every industrial project, from the first scoping session through to life after launch.
The right component set changes with who edits and how often. ACF flexible content starts from that.
What comes up when scoping a component-based editing system.
No, and the difference is deliberate. A generic page builder offers unlimited layout freedom, which is precisely what erodes consistency over time as different editors interpret the design differently. ACF flexible content offers a defined set of components matched to your approved design, each with its own fields and constraints. Editors gain speed within a structure that holds, rather than freedom that has to be policed afterwards.
Yes, and that is a normal part of a site’s evolution. The documentation built alongside the component system exists so a new block gets designed, coded and added consistently with the existing set rather than becoming a one-off that breaks the pattern. Most new requirements turn out to be met by extending an existing component with an option rather than adding another one to the list.
Typically yes, since the flexible content field type at the core of this approach belongs to the Pro tier rather than the free plugin. The licence cost is modest relative to the reliability it buys compared with a generic page builder, and we account for it during project scoping rather than presenting it as an unexpected addition later. The licence is registered in your name, not ours.
It is the editing layer inside a broader WordPress build for industrial B2B rather than a separate product. WordPress provides the platform, the hosting and the publishing workflow; the component system provides the structure inside it. Together they are what turns a content model into something a marketing team uses every week rather than a technical layer they never see.
Yes, and on a catalogue site they normally should. A product component can hold editorial fields written by marketing while reading dimensions, materials, part numbers and availability from the system that owns them, whether that is Akeneo, Pimcore, SAP, Dynamics, Infor or Sage. See PIM and product data for how those feeds are structured and kept current.
That is the point of building it this way. Once the components exist, adding a product, publishing a datasheet, writing a case reference or building an application page is editing work rather than development work. Structural changes, a new component or a new content type, still need us. The intention is that routine publishing never does, so a launch is not waiting on an agency ticket.
ACF flexible content connects closely with these related technology pages.
A site on a page builder that keeps coming apart, or a new build that needs a real component system your team can maintain. Tell us your design and we will tell you how we would approach ACF flexible content.