Blocks, made to fit

Custom Gutenberg Blocks Your Editors Can Fill In and Cannot Knock Out of Line

The home page looked right on launch day. Six months later the testimonial sits in a third font, one button has turned purple, and the hero photo is stretched to a shape last seen on a fax cover sheet. Nobody broke it on purpose. The editor simply let them.

November 12, 2026 · 8 min read

acmedentalstudio.com/wp-admin · block library
Fields an editor can change, by custom block
Six blocks, nineteen fields, no color pickers
Sample
Hero band4 fields
Service card4 fields
Testimonial3 fields
Team member3 fields
Call to action2 fields
Current offers feed3 fields
Illustrative: a sample block library for a fictional dental office

The short answer

Custom Gutenberg blocks are page sections built for one site, such as a service card, a pricing row or a testimonial, that editors drop onto a page and fill with words and images while the layout stays fixed in code. They are registered from a block.json file, the method the Block Editor Handbook describes. DataCram builds them from $575, depending on complexity, with a fixed written estimate.

On this page
  1. Freedom to edit, and the freedom to wreck the page
  2. What the Block Editor Handbook says a block is and how it registers
  3. A service card, taken apart: what editors touch and what stays in code
  4. Four kinds of block we build for small business sites
  5. Why the blocks ship as a plugin and not inside the theme
  6. Price, upkeep and when a block library is the wiser spend

Freedom to edit, and the freedom to wreck the page

The WordPress block editor hands people a remarkable amount of control. Colors, spacing, columns, fonts, borders. For a designer, that is a toolkit. For the office manager updating the holiday hours at 4:55 on a Friday, it is a cockpit, and every button is live.

Page builders made the same trade years earlier and sold it as a feature. Our comparison of page builders and Next.js covers where that road leads. If your editor screen and your live site simply disagree about how things look, that is a theme problem, and our guide to a block editor that does not match the theme is the right read.

Custom blocks take the opposite approach on purpose. Each one asks only for the content that changes: a heading, a paragraph, a photo, a link. The spacing, type and colors are decided once, in code, by someone who will still be accountable next spring. The editor stays fast and the page stays on brand. Fewer choices, offered deliberately, turn out to be a kindness.

What the Block Editor Handbook says a block is and how it registers

The Block Editor Handbook, read in November 2026, defines the unit plainly: "A block is a discrete element such as a Paragraph, Heading, Media, or Embed." The editor "uses a modular system of blocks to compose and format content," and the handbook calls it "a powerful developer platform with a rich feature set of APIs that allow it to be manipulated and extended in countless ways." Custom blocks are one of those extensions.

Registration follows a documented path. The handbook's page on registering a block says "Blocks in WordPress are typically bundled in a plugin and registered on both the server and client-side," and "The register_block_type() function registers a single block type by reading metadata from a block.json file." For a set of blocks, it adds: "Since WordPress 6.8, the recommended way to register blocks is wp_register_block_types_from_metadata_collection()."

Bright blue duotone of a person seen from behind stacking large solid rectangles and squares into a neat grid, with circles and triangles floating nearby
Custom blocks give editors fixed shapes to arrange, so the grid holds no matter who builds the page.

The block.json file is the block's definition. The handbook's block.json page says it "simplifies the process of defining and registering a block" by using the same definition in JSON format on both the server and the client, and that using it has "several benefits, including improved performance." We will not list more benefits than the handbook does. Its render property "specifies the path to a PHP template file responsible for generating a dynamically rendered block's front-end markup," which is how a block shows information that changes after the page is saved.

A service card, taken apart: what editors touch and what stays in code

Take a service card, the block most small business sites repeat a dozen times. Here is how we split it between the person typing and the code that keeps it looking like your brand.

The editor fills in

  • The service name and a two-line description
  • One photo, chosen from the media library
  • The page the card links to
  • An optional badge, chosen from a short list your team approved

The code decides

  • Fonts, sizes, colors and spacing
  • How the photo is cropped at every screen width
  • How many cards fit in a row on a phone and a laptop
  • The button style, so no card ever turns purple

The same split works for testimonials, team members, pricing rows, before-and-after photos and calls to action. When the brand changes, we change the block once and every page that uses it follows. Nobody has to open forty pages and fix a button color by hand.

There is a quieter benefit. A new hire can build a landing page on the first afternoon, because each block asks short, plain questions: what is the headline, which photo, where does the button go. No lessons on margins and padding. No screenshot of the approved layout taped beside the monitor. The block already knows the answer, and it gives the same one to the intern and the owner.

Four kinds of block we build for small business sites

Common custom blocks, what editors supply and what the code keeps fixed
What the editor suppliesWhat stays locked in code
Layout sectionsHeadline, text, image and button label for a hero or two-column bandProportions, image crops, type scale and spacing at every screen size
Repeating contentOne entry per testimonial, team member, FAQ or projectOrder rules, card design and how many appear per row
Live informationWhich feed or category to show, such as current offers or recent projectsA server-side template, named in block.json's render property, that draws fresh data each time
Calls to actionThe offer line and the destination pageButton design, phone number format and tracking attributes

Live blocks are where custom work pays most. A block can show WooCommerce products by a rule your store sets, covered on our WooCommerce extensions page, or data that arrives from another system through an API integration plugin. A block that displays a booking form or a lead form can sit on any page, with the logic living in a custom form plugin.

Why the blocks ship as a plugin and not inside the theme

The handbook's phrase is "typically bundled in a plugin," and we follow it for a practical reason. A plugin survives a theme change. Content built from your blocks stays in place when the design is refreshed, because the code that defines the blocks never lived in the theme. The plugin versus functions.php page explains the wider rule, and if the theme itself needs work, our WordPress theme customization and WordPress theme developer pages cover that side.

  1. 1

    Inventory the sections

    We go through the pages you edit most and list every repeated section. Most sites need fewer than their owners expect.

  2. 2

    Agree on the fields

    For each block, we agree on what the editor can change and what stays fixed, in writing, with the person who edits the site.

  3. 3

    Build and register

    Each block gets its own block.json and is registered from a plugin, the way the handbook describes.

  4. 4

    Test in the editor, not just the browser

    We build real pages with the blocks, try to break them the way a busy editor would, and fix what gives.

  5. 5

    Hand over with a short guide

    Your team gets a one-page guide to each block and a walkthrough. The code is documented so another developer could pick it up.

The handover also lists every block, what it is for and which fields it offers. When a section retires, nobody has to guess what it did, and when a new developer joins, that list is the first thing worth reading.

Price, upkeep and when a block library is the wiser spend

Custom blocks start at $575 to build, depending on complexity, with a fixed written estimate before work starts. A handful of layout blocks sits near the start of that range; live data, many variations or a large library push it up, and the estimate says how far. Hosting and maintenance runs from $55 a month and includes updates checked on a staging copy first. Changes to the blocks after launch are quoted. The custom plugin pricing page explains how estimates are built.

Some owners discover they want an editing system built around their content from the start. Our explainer on what a custom CMS is describes that option, and Athena is the content system included with every custom site DataCram builds.

DataCram is a web studio in San Antonio, Texas, building for the web since 1999. We work with teams across the US by phone, video and a shared project page; learn about DataCram or look through past projects. The custom plugin development page covers how a build runs, and the custom WordPress plugins hub lists every type of plugin we write. Or call (210) 346-0848 and tell us which page your team keeps breaking.

Questions owners ask about custom WordPress plugins

Often not. If one person edits the site a few times a year and the sections your theme offers already look right, keep using them. Custom blocks earn their cost when several people edit, when the same section repeats across dozens of pages, when the brand must hold no matter who is typing, or when a section needs live data from your store or another system.

It is the method the Block Editor Handbook describes, read in November 2026: register_block_type() "registers a single block type by reading metadata from a block.json file," and since WordPress 6.8 the recommended way to register a set of blocks is wp_register_block_types_from_metadata_collection(). We follow that documented path so the blocks match what other WordPress developers expect to find.

No. New blocks appear alongside the ones you already use, and existing pages stay as they are until someone edits them. We usually rebuild the most-edited pages with the new blocks first, test them, and leave the rest for your team to convert over time, or not at all.

Because we ship them in a plugin rather than the theme, the blocks and the content built with them stay in place. The new theme may change the surrounding page, and some block styles may need adjusting to match a new brand, which is quoted. The WordPress theme customization page covers theme-side work.

From $575, depending on complexity, with a fixed written estimate before work starts. The number of blocks, how many variations each needs, and whether any of them pull live data decide where in the range you land. Hosting and maintenance runs from $55 a month, and changes after launch are quoted.

Yes. Block.json's render property points to a PHP template that draws the block's front-end markup when the page loads, per the Block Editor Handbook as read in November 2026. That template can show products chosen by a store rule, current offers, or records sent from your CRM through an API integration.

Keep reading

Free · No obligation

Find out which blocks would stop the page from breaking

Send us the pages your team edits most. We reply with a list of blocks, a fixed written estimate, and an honest note if your theme's existing sections would do the job.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote