5 ways conditional fields improve your daily content editing

As a content editor, your work often starts in the CMS—writing blog posts, updating pages, adding links, or adjusting SEO settings. It sounds straightforward—until you're staring at a long list of fields, half of which aren’t even relevant to the thing you're working on.

Maybe you’re editing a simple blog post, but the interface shows options for advanced layout controls, metadata and more—even if you don’t need them. Or you're updating a product listing, and you're forced to scroll through fields meant for completely different product types.

The result? More time spent figuring out what to ignore.

To help you solve this challenge, we introduced Conditional fields—an update designed to make the editing process cleaner, faster and more intuitive.

But what are conditional fields?

Conditional fields let you show or hide specific fields—or even entire sections—based on what the editor is doing. In other words, the editing interface adapts in real time to your content choices, keeping things clean and focused.

You can set a field’s visibility based on the value of another field. So depending on what you select or type, the interface shows only what’s relevant—and hides what isn’t. This makes your workflow more efficient and keeps your editing experience clean and organized.

In your day-to-day as a content editor, your needs can change depending on the content you're working on.

Sometimes, you only need certain fields to appear, like when switching between internal and external links, or editing product listings with different options. You may also want to show extra fields only when necessary, like customizing SEO or adding a CTA.

That’s why we’re breaking down five real-world use cases where a cleaner, more focused interface makes all the difference.

Let's take a closer look.

Let’s say you’re editing a blog post and need to add a link. Sometimes that link goes to another page on your own site (an internal link). Other times, it’s pointing to an outside website (an external link).

Normally, you’d see fields for both options—whether you need them or not. But in reality, you only ever use one of them at a time.

With a Boolean condition (true or false), you can now choose what kind of link you’re adding—internal or external—and only see the field that matches your choice. So if you pick “internal,” the external link field stays hidden. If you choose “external,” you won’t see the internal link field.

When editing a product or page, not everything should look the same. Different product types require different fields, and showing everything at once can create unnecessary confusion.

For example, if you're adding a car to your product listing, you’ll need fields like mileage, fuel type, and vehicle condition. But if it’s an electronic item, fields like warranty, brand, and model number are more relevant.

With list value conditions, you only see the fields you need, based on the product category you choose. Instead of showing every possible field, you can select a product type from a dropdown, and only the relevant fields will appear—keeping the interface clean.

This approach works for pages too. Sites often have different templates for landing pages, contact pages, or blog posts, with similar but slightly different fields. Using a page type selector at the top, the CMS can show or hide fields based on the type of page you’re working on, ensuring editors only see the relevant fields. For developers, this means fewer templates to manage, making the system more flexible.

Sometimes, content editors need a bit of extra guidance, especially when it comes to SEO. That’s why it can be helpful to include contextual info boxes that explain things like how to write a strong meta title or what makes a good description.

With section conditions, you can add a toggle like “Learn more about SEO.” When it’s switched on, helpful tips and best practices appear right in the editor—ideal for newer editors who are still getting the hang of things. But if you already know your way around, you can leave it off and keep the interface clean and simple.

Sometimes you’re working with a component—like an icon grid or a banner—and there’s an option to include a Call to Action (CTA). But not every version of that component needs one.

So what happens? You often end up with extra fields sitting there: CTA text, CTA link, button style, even when there’s no CTA being used.

With conditional fields, you can set it up so those extra fields only appear if the CTA text field is filled in. If it’s empty, everything else—like the link and styling options—stays hidden.

This works using an "is empty / is not empty" condition. It’s a small change that makes the editing flow feel much smoother, especially when you’re working with reusable components that don’t always need all their options.

When you're adding a video link in the CMS, not every platform needs the same settings. YouTube videos, for example, often require extra options like start time or show captions, while other platforms don’t.

With conditional logic, the form can detect a YouTube URL using a regex pattern and show only the fields that matter.

So:

• If you paste a YouTube link like https://www.youtube.com/watch\\?v=.+$ the form reveals start time and show captions fields.
• If you enter any other kind of video URL, those fields stay hidden, keeping the form focused and relevant.

These small changes might seem simple on their own—but together, they make a big difference.

Conditional fields help create an editing environment that feels smarter, cleaner, and more focused. You spend less time digging through irrelevant fields, and more time doing actual content work.

Whether you're writing blog posts, managing product pages, or fine-tuning a CTA, the interface adapts to what you need—when you need it. It’s all about making the CMS feel less like a form to fill out, and more like a tool that works with you.

To learn more about conditional fields, take a look at our docs.