What working on real client websites taught me about content, feedback, responsive design and why a design the client dislikes isn't always a bad one.
Working on a client website is quite different from building one for practice or personal use. In a personal project, most design decisions come down to our own preferences. In a client project, the website has to represent the client's business, present content clearly, look professional, and match what the client has in mind.
I have worked on several client websites, mostly static, content-driven ones. Along the way I learned that a good website takes more than code. Understanding the client, the content and the overall visual experience matters just as much.
Decide what matters before you decide how it looks.
How content is presented changes how it is understood.
Fit for the client matters more than personal taste.
Understand the "why" before implementing the "what".
Feedback is part of the process, not the final step.
Design with realistic content from the beginning.
Judge every section against the full page.
Components and responsiveness aren’t afterthoughts.
Spacing and alignment decide if a page feels finished.
A content document gives you headings, paragraphs, images and other information, but it doesn't tell you how the page should look. Before designing, we need to decide what deserves more visual importance, which pieces of content belong together, where visuals will help, and how the information can be presented clearly.
Content structure and visual design have to work together.
The same content can be presented in many ways. Layout, typography, spacing, images, colours and visual hierarchy all change how information is understood.
A long paragraph may fit on a webpage, but when it is broken into smaller sections with clear headings, visuals and enough spacing, it becomes much easier to read. So I now think about how content should be presented, not only what goes on the page.
Design is subjective. Something that looks good in one situation may feel different when the content or the surrounding sections change. The same goes for clients. A design one client loves may not suit another, even in the same industry with similar content.
Preferences, expectations, brand identity and personal perception all play a part. A design may not be “bad” just because someone doesn't like it. It may simply not be the right fit for that client or context.
Because design is subjective, understanding the client matters a great deal. Sometimes a client knows something doesn't feel right but can't say what should change. Sometimes they point to a website they like without explaining what attracted them to it.
In those moments, it helps to look past the instruction and ask a few questions:
What should the website communicate?
What impression should visitors leave with?
What did the client like about the other site: its layout, colours, typography, imagery, spacing or overall feel?
Clients don't always share everything at the start. Many only realise what they want once they see an actual design. Regular reviews catch misunderstandings early and bring out expectations that were missing from the original requirements.
Feedback isn't just a final approval step. It is part of the design process itself.
Placeholder text makes a design look balanced because its length is predictable. Real client content is often longer or shorter than expected. Headings wrap, cards end up with different heights, images need repositioning, and sections become visually uneven.
A layout that looks perfect with sample text may need changes once the actual content goes in. Designing with realistic content from the beginning saves a lot of rework later.
A section can't always be judged by itself. Spacing, image size, text length and neighbouring sections all affect the balance of the page, so design decisions need to be checked against the complete page, not one section at a time.
Reusable components such as headers, footers, buttons, cards and hero sections keep a website consistent and make future changes easier.
Responsive design deserves the same attention from the start. A desktop layout often needs significant changes for tablets and mobiles. Text wraps differently, images need different proportions, and sections may need to be rearranged. Treating this as something to fix at the end usually costs more time.
Spacing, alignment, typography, line height, image cropping, button positioning and white space have a big effect on how polished a website feels. A page can contain all the required content and still look unfinished if these details are ignored.
I no longer see website design as just creating attractive pages. For me it is a process: understand the client's business, understand the content, explore design options, take regular feedback, and refine the result against the full page and real content.
There may not be one perfect design. The right one fits the particular client, their content, their brand and the message they want to share.
So the question isn't only “Can we build this page?” It is also “What does the client want to communicate, how do they want it to look, and why?”