How to Let Your Marketing Team Edit the Website Without Breaking It

A marketing manager at a mid-size B2B company asked for two things from their website in a single sentence on Reddit this summer:

“I want my team (none of them code) to be able to ship copy and new sections themselves, on brand, without the ability to nuke the live site.”

They want control and they want a guarantee, and the guarantee is the part that usually gets skipped. I’ve written my share of “easy drag-and-drop editing” pitches, and none of them actually help a manager whose engineer still brings up the half-day outage from the last time a non-developer touched the production site.

You let a marketing team edit a website without breaking it by locking the micro elements (every heading level, paragraph styles, named font sizes and button styles) and handing over a documented library of pre-built blocks, so every edit is basically like picking out which Lego bricks to use and how to snap them together.

What should be locked on a company website?

The micro elements should be locked: headings, paragraph styles, font sizes and button styles. On the WordPress sites we build at Classic City, that breaks down into four specific things.

Every heading level, H1 through H6, has an exact font family, font size and styling attached to it. All of your paragraphs (your regular body content) have stock styling, so no matter where you drop a paragraph, it looks the same. Font sizes are names: if you put a paragraph on a page, you can bump it to large or extra large, or drop it to small, straight from a dropdown menu. And buttons come pre-designed in three styles (a solid button, an outline button, and a plain text button), so all anyone has to do is pick the right one.

Why go that granular? Because that’s where drift starts. It almost always begins with ONE small font size change. Somebody wants a little extra emphasis on one line, so they make the text bigger by hand, and then the rest of the site’s font sizes start moving to match. Named sizes take that decision off the table. Nobody on your team should be choosing pixel values, and with a short dropdown of named sizes, they never have to.

When the headers, the paragraphs, the bulleted lists and the buttons all have locked-in styles, the person building a page doesn’t have to think about any of it. The easier that is, the easier it’s going to be for people to maintain their website long term.

What should the marketing team be free to change?

Your marketing team should be free to choose which blocks go on a page, what order they go in, and everything inside them: the words, the images, and the colors from the theme’s palette. That’s a lot of freedom. A new landing page for a campaign is a set of choices from a menu your team already knows, and the menu is what I like to call the block library.

The block library is a page on the site that has every building block laid out, named, described, and showing how to use it. Our sites usually ship with 10 to 15 branded blocks, and during the build we also put together a handful of page layouts that use those blocks in a particular order, so people can see how the blocks work together. In practice, most people look at their site, find a page they want to base the new one on, and start from there. I think that’s great, and it’s exactly how it should work.

Color is a good example of where the line sits. We’re designing for a client right now that has about five product lines, each aimed at a very different customer (one is all hardware, one is very beachy, one is for folks who live in the mountains). We wanted their site to feel completely cohesive, but allow each segment to still remain a smidge different. They have a slew of different blue-to-green hues in their brand palette, and now each product page uses one of them as its “base color” throughout the page, along with its own imagery and iconography. What doesn’t move is the layout and structure of the pages, and the call-to-action color, which is orange on every single page. A visitor on the beach page and a visitor on the hardware page both know that orange means there’s an action here.

What’s the difference between custom blocks and drag-and-drop blocks?

Custom blocks have their design built in, and drag-and-drop blocks (plain WordPress Gutenberg blocks) give your team full control over what’s stacked inside them. We build both, plus a handful of blocks that mix the two.

A fully custom block is one where, if you looked at the design, you’d think laying it out by hand would be pretty difficult. It might have swooshes, patterns, or overlays that don’t make sense in a drag-and-drop editor. Your team fills in the words and swaps the images, and the design takes care of itself. A fully customizable block is the opposite end: images and text stacked on top of one another, with full control over the arrangement.

I honestly haven’t figured out a great way to describe the distinction between both of these yet. The closest I’ve gotten is a gut check. Look at a block on your site and ask yourself: would I love to recreate that whole thing from scratch, or does that sound daunting? If it sounds daunting, it should be a custom block, and nobody on your team should ever have to rebuild it. If it sounds pretty simple, it can be a drag-and-drop block and your team can have at it. (It’s not a perfect test….. but it’s the closest I’ve come.)

This matters for the “without breaking it” part of the request, because the custom blocks are where the hard-to-reproduce design lives, and they’re the hardest blocks to knock off-brand by accident. (For the record, no site is drift-proof. WordPress is powerful enough that someone determined can change almost anything, whatever platform you’re on. The goal is to make an off-brand change take several deliberate steps.)

Why not lock the whole site down?

Because the more you lock, the more your team pushes back, and a team that feels boxed in starts working around the system. You could remove all optionality from a client and lock them into specific layouts where all they do is fill out a form. And then people want more flexibility. It’s a constant move along a line between flexibility and consistency: the more flexibility you give, the less consistency you can potentially have.

WordPress has its own tools for the strict end of that line. The block editor can lock a pattern into a content-only mode where people change text and images and nothing else. That’s useful for specific templates, but a whole site built that way turns every new idea back into a developer ticket, and a ticket for every change is the exact thing your marketing team was trying to get away from.

The other end of the line doesn’t work either. A completely blank canvas with nothing locked down at all basically allows everybody to be a full custom designer. And that is also a problem.

Built correctly, anybody on your team can update a WordPress site. The words “built correctly” are absolutely key in that sentence though: the micro elements are locked, the blocks are documented, and your team knows which ones they can pull apart.

How do you train a team that only edits the site twice a year?

You train them twice: once live at launch, and then with a video library they can go back to when they’ve forgotten everything. If your team doesn’t open the site for months, they lose the muscle memory no matter how good the training was, because a CMS has a lot of options. So the handover has to assume they’ll forget.

Right before or right after a site launches, we host a live training session for about an hour. It covers the basics and lets people see the site, poke around, and ask the gut-reaction questions everyone has. Then we send over a library of training videos, organized by what your team will actually be working in:

• A video on all the custom blocks
• A video on the blocks that are pure Gutenberg drag-and-drop
• A video on the handful of blocks that mix both
• A video on the core of WordPress itself: how pages work, how posts work, and how your navigation and footer work

Together, those get a team to 90 or 95 percent. I’d never say it’s 100 percent, because I know there’s always going to be something missing. The point is that someone who hasn’t edited the site since spring can open the library in October, find the exact block they need, and get a quick reminder on how to use it before they start building.

If your team is in that twice-a-year camp, you’re in good company, and that’s perfectly fine. Managing a website shouldn’t require website experience. It should be something a person who understands content and layouts can do.

I will say that no matter how fluent you are in website work, every new website is going to be a learning curve. All the different things are going to be in very different places than you’re probably used to, and that’s okay. Websites are not the simplest things to edit, there are a lot of moving pieces to them, and it is totally okay if the first few weeks (or the first couple of months) of working in the site feel slow.

Getting a new website is not like buying a new car. If you know how to drive a sedan, you can probably drive an SUV. It might not be as comfortable, given that it’s a lot larger, but you can totally do it. Websites are a little more complicated than that, and they take a little more time behind the wheel before you get into the flow of how this particular one works. Obviously, with the live training and the videos, our goal is to lower that learning curve as much as we can, but it’s still going to be there.

What happens when nobody sets this up?

Without locked micro elements and a block library, a website slowly stops looking like itself as the team edits it, and I call that “design drift.” Every person on a team has a slightly different design eye, designer or not. One person makes a heading bigger, another picks a new shade of blue to make a button stand out, somebody rounds the buttons a little differently, and someone else can’t find the image style everyone else used and ships square photos instead. Nobody breaks the site on any single day.

You start to notice it when you can kind of tell which pages got designed and which ones got built in a hurry. The phrase to listen for is “Is that good enough?” When someone on your team asks that about a page, it usually means the page doesn’t quite match the rest of the brand and they know it.

Left long enough, drift ends with a team that’s locked out of its own website. The admin can’t stand working in it, because everything is so customizable that it’s hard to stay on brand, and building a new page turns into a design exercise every time. That’s usually when the redesign conversation starts (and if you’re already there, I broke down what a website redesign costs in a separate post). I’d rather you never get there, and I wrote more about why this comes down to process in design drift is an operations problem.

Does the handover hold up over time?

The longest-running example I have is a site we built around 2015 that the client’s team used through 2024. This was before we had a team, and before we could save patterns or sync blocks. When it launched, we taught their people how to add the buttons, how to add a two-column block, and how to add the image texture to the side, and that was about it.

Over the next eight or nine years, we slowly added more building blocks to their library. Some looked better than others, but none of them looked disconnected from the rest. When they finally needed a rebuild (they had a big marketing push and needed a lot of pages quickly, and the old system couldn’t save patterns), the new site was only about a 20 percent visual jump from the old one. Their customers barely had to relearn anything. I tell the longer version of that story in healthy evolution versus design drift.

The owner of The Frame Brain put it this way in a Clutch review:

“I can add a section or swap out the content and still maintain all the header tags, colors, and styling.”

That’s what a handover is supposed to buy you.

What can you check on your own site this week?

There are a lot of us out here selling how easy a site is to edit. The harder promise, “without the ability to nuke the live site,” is a design decision that actually gets made before launch: which micro elements get locked, which blocks get built custom, and how your team gets reminded of all of it six months later. One thing you can check this week, whoever built your site: open your editor, add a paragraph to a draft page, and see whether you can change its font size to anything you want. If you can, so can EVERYONE else on your team, and that’s the first thing I’d lock. And if you can’t, and your team has been shipping pages on its own that still look like they belong together, that’s hard to pull off. Be proud of that. And if you want a second read on it, the brand drift quiz takes a few minutes.

If you’re trying to give your team control of the site and you need the guarantee that comes with it, book a call with us. Tell us what your team is trying to ship and we’ll tell you honestly what we’d lock and what we’d leave open.

FAQ

Should everyone on the marketing team have admin access to our WordPress site?

Not by default. You want one person who acts as the gatekeeper for the site: someone who makes sure the brand, messaging structure and design principles are followed, and who also knows when it’s a good time to break the rules on purpose. Once you have two, three or four people in marketing, more of them will be editing, and that’s fine as long as one person still holds the keys. I go deeper on this in who should edit your company website.

Do we need a developer every time we want a new block?

For a fully custom block, usually yes. That’s fine, because a new block should be a deliberate addition. If someone on your team has an idea that fits the brand, try it, add it to the library, and if it works, keep it. What you want to avoid is designing one-off pieces for one page that never get reused.

What if our current site wasn’t built with a block library?

Start one anyway. Create a page called “block library” (make it unindexable by Google if you can), and once or twice a week, find a pattern of blocks already on your site, save it there, and give it a name. If your CMS lets you save it as a reusable pattern too, use the exact same name. The order of operations for building a new page picks up from there.

How long does website training take for a marketing team?

About an hour live, at launch. The part that does the heavy lifting is the video library afterward, because that’s what people come back to when they haven’t touched the site in months.

Is WordPress the right CMS for a marketing team that wants to edit its own site?

There’s no perfect CMS, and every one of them has a pros and cons list. We build in WordPress’s block editor (Gutenberg) because it lets us lock the micro elements and still give teams drag-and-drop blocks. Webflow is a good platform, but it shows you the code in the sidebar and uses the same names for things, so you’re still doing code, just visually. Pick the one whose trade-offs fit the team you have.