How to Iterate on Your Website by Describing Changes

Most website builders make changes the hard way. You want the heading bigger, so you hunt for the right menu, find the font-size setting, guess at a value, and repeat. Multiply that across every tweak and building a site becomes an exercise in menu archaeology. SnapBlock takes a fundamentally different approach: you describe the change you want in plain language, and it makes it. That shift is what turns editing from a chore into a conversation.

But describing changes well is a small skill worth learning, because the clearer you are, the better the results. This article explains how the describe-to-change approach works and how to get the most from it, with practical tips on phrasing your requests. None of this is technical, it's just about communicating what you want clearly, the same way you'd brief any collaborator.

Why Describing Beats Clicking

The core advantage of describing changes is that it removes the translation step. Normally, you have an outcome in mind, then you have to translate it into a series of clicks and settings to make it happen, and that translation is where non-technical people get stuck. When you can just state the outcome, the tool handles the translation for you. You think in terms of what you want, not how to do it.

This is especially powerful for people who know what looks right but don't know the technical words for it. You don't need to know that you want to adjust "line-height" or "padding", you can say the text feels cramped or the spacing looks off, and the builder understands. Describing changes lets you work at the level of your actual intent, which is exactly where a non-developer's instincts are strongest.

Tip 1: Be Specific About What and Where

The single most useful habit is being clear about what you want changed and where. "Make the top section's background darker" gives the builder much more to work with than "make it darker", because it names both the element and the change. You don't need technical precision, just enough clarity that there's no ambiguity about which part of the page you mean and what you want to happen to it.

Think of it like giving directions to a helpful assistant. The more clearly you point at the thing and describe the outcome, the more likely you get exactly what you pictured on the first try. Vague requests still work, but they may take an extra round to land. A little specificity up front usually saves a step, and it quickly becomes second nature.

Tip 2: One Change at a Time (Usually)

When you're refining something specific, making changes in focused steps tends to work better than requesting a dozen unrelated tweaks in a single breath. Adjusting one thing, seeing the result, then moving to the next keeps the process clear and makes it easy to tell whether each change did what you wanted. It also makes it simple to steer, since you're always reacting to the most recent version.

This isn't a rigid rule, broad requests like "make the whole site feel more modern" are completely valid and useful for big-picture direction. But when you're dialing in details, smaller focused steps give you more control. A good rhythm is to use broad requests to set overall direction and focused ones to perfect the specifics, alternating between the two as your site takes shape.

Describing Changes: What Works

Instead of	Try	Why It Helps
"Make it better"	"Make the hero section feel more welcoming"	Names the area and the feeling you're after.
"Fix the spacing"	"The text under the title feels cramped"	Describes the problem in your own plain words.
Ten changes at once	One focused change, then the next	Keeps it easy to see and steer each result.

Tip 3: Use the Suggestions

One underused part of the iteration process is that SnapBlock can suggest improvements as you go. When you're not sure how to make something better, or you've run out of your own ideas, these suggestions are a genuine asset. They can point you toward refinements you wouldn't have thought to ask for, which is especially valuable for beginners who know when something feels off but not how to fix it.

The smart way to use this is as a collaboration rather than a menu. You bring the vision and the reactions; the tool brings options and ideas. When a suggestion resonates, take it; when it doesn't, steer in your own direction. Treating the process as a genuine back-and-forth, where both you and the builder contribute, tends to produce better results than trying to dictate every detail alone.

Tip 4: Don't Be Afraid to Experiment

Because changes are so easy to make and describe, iteration is the perfect environment to experiment. If you're curious whether a different color scheme, layout, or tone would work better, just try it, you can always describe your way back. This freedom to explore without penalty is one of the quiet joys of building this way, and it often leads to a better site than sticking rigidly to your first plan.

Experimentation is how good design happens, and the low cost of trying things here removes the usual fear of "breaking" something or wasting effort. You're encouraged to play. Try the bold version, see how it feels, and refine from there. Some of the best outcomes come from a willingness to describe an experiment and see what happens, precisely because doing so costs you almost nothing.

The Takeaway

Iterating on your website by describing changes is what makes SnapBlock feel less like software and more like collaboration. To get the most from it: be specific about what you want and where, make focused changes when you're perfecting details, lean on the tool's suggestions when you're stuck, and experiment freely since trying things costs almost nothing. You work at the level of your intent, not technical settings, which is exactly where your instincts are strongest. The best way to feel it is to build something and start describing your way to better.