Dentista: when a visual idea has to become a website.

Dentista started with a visual idea.

I wanted to explore what a dental website could feel like if it borrowed more from editorial design than the usual healthcare patterns.

Large typography. Art-directed photography. Restrained color. Asymmetry. Space.

That was the spark.

But a visual direction and a working website are two different things.

Once I started turning the idea into an actual site, the question changed from:

How should this look?

to:

How should this work for someone looking for dental care?

That changed the project.

The reference gave me a feeling, not an architecture

It is easy to find a design you like and start borrowing the visible ingredients.

The type scale.

The image treatment.

The grid.

The whitespace.

The problem is that none of those things explain why a section should exist.

They don't tell me what a patient needs to understand before considering treatment. They don't tell me what belongs on a treatment page, when proof becomes useful, or when asking someone to book actually makes sense.

So I treated the visual direction as a constraint rather than a blueprint.

It could influence how Dentista communicated.

It couldn't decide what Dentista needed to communicate.

Then I worked backward from the patient

Someone looking into cosmetic dentistry isn't necessarily ready to schedule an appointment.

They might still be trying to understand what's possible.

They might be comparing treatments.

They might care about how natural the result will look.

They might want to see the dentist's work before they care about anything else.

Or they may already know exactly what treatment they want and simply need enough confidence to take the next step.

Thinking through those situations started giving the pages a reason to exist.

Instead of:

Hero → Services → About → Testimonials → CTA

The question became:

What does this person need to understand next?

That is a much harder question.

It is also much more useful.

The architecture started pushing back on the design

This was probably my favorite part of the experiment.

Once the patient journey became clearer, some of the visual ideas stopped working.

A composition might look great but put important information too far down the page.

An oversized heading might create the right editorial feeling on desktop but consume most of a mobile screen.

An intentionally sparse section could become confusing if the patient needed more context there.

So the design had to adapt.

Not because the original direction was wrong.

Because it now had a job.

The patient journey established the sequence.

The content established what needed emphasis.

The visual system decided how to express it.

Mobile exposed the rules underneath the composition

Desktop gave me room to experiment.

Mobile forced me to understand what I had actually designed.

Overlapping imagery, unusual proportions, oversized typography, and large areas of whitespace can't simply be scaled down.

Something has to change.

The useful question became:

What makes this feel like Dentista even when the composition changes?

That led to thinking less about individual layouts and more about relationships:

Typography rather than isolated font sizes.

Spacing rhythm rather than one-off gaps.

Image behavior rather than fixed crops.

Hierarchy rather than coordinates.

The mobile version didn't need to reproduce desktop.

It needed to preserve the same design language.

Then I had to make it buildable

The next challenge was translating all of this into WordPress.

A static concept can get away with a lot.

A real website can't.

Content changes. Headlines get longer. New treatments get added. Images aren't always the perfect dimensions. Pages need to work across screen sizes.

And eventually someone other than the person who designed it may need to edit it.

That means the design can't depend on manually recreating a composition every time.

I started looking for the system underneath it:

Reusable components.

Global typography.

Spacing rules.

Image treatments.

Responsive behavior.

Repeatable page patterns.

The goal wasn't to reproduce a screenshot inside a builder.

It was to figure out which rules would allow the design to keep working after the original page was gone.

The tool came last

I have been experimenting with bringing Dentista into WordPress using modern builder workflows and AI-assisted development.

That part is interesting.

But it also reinforced something I've been thinking about lately.

The tool doesn't know why a section exists.

It doesn't know what the patient needs next.

And it doesn't know which parts of a visual reference are important enough to preserve.

Those decisions have to happen somewhere else.

Once they do, the implementation becomes much clearer.

What Dentista taught me

Dentista didn't follow a perfectly linear process.

The visual idea came first.

Then the patient journey challenged it.

The architecture gave it structure.

The responsive work exposed its rules.

And the implementation forced those rules to become reusable.

There was a lot of movement back and forth between those layers.

I think that was the useful part.

A visual reference can be a great place to start an experiment.

It just shouldn't be allowed to make every decision that comes after it.