kevinwoo.com No paid content found

UI design is the discipline of designing the screens, controls, and visual states people interact with directly — buttons, forms, navigation, typography, color, spacing, and feedback. Its core goal is to make an interface usable and clear: a person should be able to tell what something is, what it does, and what happened after they acted. It sits inside a broader product process alongside UX design (how the flow and logic work) and branding (how the product looks and feels as a recognizable identity). If you are hiring for it, the practical question is not "do we need UI design?" but "which of these layers is missing right now?"

UI design vs. UX design vs. product design vs. visual design

These terms overlap in job postings, so it helps to separate them by the question each one answers.

In practice, one person often covers several of these. On a small team, a product designer may run research, flows, and UI. On a larger team, UI design is a defined role that takes flows from UX and turns them into production-ready screens. The distinction matters mainly for hiring and handoff: if your flows are solid but the screens look inconsistent and unfinished, that is a UI gap, not a UX one.

What UI design actually includes

A UI designer's work is more than "making it pretty." The recurring deliverables are:

• Screens and layouts — every view a user sees, at the sizes and breakpoints that matter (web, mobile, tablet).
• Components — reusable pieces such as buttons, inputs, cards, modals, and navigation, each with defined states: default, hover, focus, active, disabled, loading, error, empty.
• Design systems — the shared library of components, tokens (color, spacing, type scale), and usage rules that keep a product consistent as it grows. Kevin Woo Designs lists design systems as a distinct service alongside product UI/UX design, which reflects how often the two are scoped together.
• Prototypes — clickable or interactive versions used to test a flow or demonstrate intent before engineering builds it.
• Specs and handoff — measurements, behavior notes, and edge cases that let developers implement without guessing.

The states list is where most amateur UI work falls apart. A button that only exists in its "normal" state will break the moment a form fails validation or a list is empty.

Where UI design fits in the product process

A common sequence looks like this:

1. Discovery — understand the user, the business goal, and the constraints.
2. UX and structure — map flows, decide what screens are needed, wireframe the logic.
3. UI design — apply visual language and build out components and states.
4. Prototype and test — validate with real users or stakeholders before build.
5. Handoff and build — specs, assets, and design-system components go to engineering.
6. Iterate — refine based on analytics, feedback, and QA.

UI design is not a one-time phase. Once a design system exists, UI work becomes ongoing: new features reuse existing components, and inconsistencies get caught in review.

How branding and visual identity inform UI decisions

Brand identity sets the raw material — logo, color palette, typography, tone — and UI design translates it into an interactive context. A brand color that works on a business card may fail contrast requirements on a button. A display typeface that looks striking in a headline may be unreadable at 14px in a form label. Kevin Woo Designs describes its work as delivering "impactful designs with strategic vision, delivering measurable results across every touchpoint," and lists brand identity, visual identity guidelines, and product UI/UX as separate but connected services — a useful reminder that brand guidelines and UI systems are related documents with different jobs. Brand guidelines govern how the identity appears; UI systems govern how the product behaves.

Signs a UI needs improvement

You do not need a formal audit to spot common problems:

• Users ask "what do I click next?" or miss primary actions entirely.
• The same element (a button, a link, a heading) looks different on different screens.
• Error, loading, and empty states are missing or unhelpful.
• Text is hard to read — low contrast, cramped line height, or inconsistent sizing.
• Mobile layouts feel like shrunken desktop screens rather than designed for touch.
• Developers regularly ask for missing states or measurements during build.

If several of these are true, the fix is usually a design-system pass rather than a full redesign: define the components and tokens, then apply them screen by screen.

Choosing what to hire for

If your flows are unclear and users get lost, start with UX. If the flows work but the interface looks inconsistent, unfinished, or hard to use, that is UI design work. If you are launching something new and need the identity, the product, and the marketing to tell one story, you likely need a partner covering branding and product design together. Kevin Woo Designs positions itself in that combined space — branding, product UI/UX, design systems, and growth — which suits teams that need strategy and execution from one source rather than a single-discipline contractor.

A designer plans how a space will look, feel, and function—selecting layouts, finishes, fixtures, and furnishings—while an architect is a licensed professional who designs buildings and, in most U.S. states, must stamp drawings for permits, structural changes, and life-safety code compliance. If your project involves moving walls, changing a building's structure, or obtaining a construction permit, you generally need an architect (or another licensed design professional). If you're refreshing finishes, reconfiguring furniture, or planning decor, a designer is usually the right hire. AIA Delaware, the state chapter of the American Institute of Architects, describes the AIA as "the voice of the architectural profession and a resource for its members in service to society"—a useful starting point when you need to verify whether someone is a licensed architect.

What a Designer Actually Does

A designer's work centers on the interior and experiential side of a project. Typical tasks include:

• Space planning — deciding how furniture, traffic flow, and zones fit within existing walls.
• Material and finish selection — flooring, paint, tile, countertops, cabinetry hardware.
• Lighting and fixture specification — choosing and positioning fixtures within existing electrical layouts.
• Furnishing and styling — sourcing furniture, textiles, and accessories.
• Concept and mood development — translating a client's taste into a coherent visual direction.

Designers may hold credentials such as NCIDQ certification or state interior design registration, but these are separate from architectural licensure. Not every designer is certified, and certification requirements vary by state.

How a Designer Differs from an Architect

The core difference is licensure and legal authority, not creativity. Both roles design, but only a licensed architect can legally sign and seal construction documents in most jurisdictions.

A useful rule of thumb: if the work touches the building's structure, envelope, or means of egress, it belongs to an architect. If it touches what's inside the shell, a designer can often handle it.

When a Project Legally Requires an Architect

Requirements are set by state and local building codes, so they vary. In general, an architect (or another licensed design professional) is needed when:

• You are constructing a new building.
• You are adding square footage or altering the structural system.
• You are changing occupancy or use in a way that affects life-safety requirements.
• You need a building permit that requires sealed drawings.

For a Delaware-specific project, confirm the requirement with the local building department or permit office before hiring, since thresholds can differ by municipality and project type.

Choosing Between a Designer and an Architect

Work through these steps:

1. Define the scope. List exactly what will change—finishes only, or walls and structure?
2. Check permit requirements. Call your local building department and ask whether your scope needs sealed drawings.
3. Match the professional to the scope. Finishes and furnishing → designer. Structure, additions, permits → architect.
4. Verify credentials. For an architect, confirm licensure through the state licensing board or a professional body such as AIA Delaware.
5. Consider collaboration. On larger interior projects, an architect and designer often work together—the architect handles the shell and code, the designer handles the interior experience.

If you're unsure which side of the line your project falls on, start with the permit question. The answer usually determines who you need to hire.

Web design is the planning of a website's layout, navigation, content structure, and visual style before and alongside development. It answers what goes where, how people move through it, and how it looks and feels — not just how it is coded. It applies whether you are commissioning a site, building one yourself, or hiring a studio such as Fuel180 Creative, a New Jersey multimedia development facility whose in-house services include design, internet site development, e-marketing, social media, interactive development, video production, animation, and presentation design.

Where web design sits among related disciplines

Web design overlaps with several fields but is not identical to any of them.

A designer may handle UX and branding tasks, and a developer may make design decisions during implementation. The distinction matters mainly for scoping: if you hire for "web design" only, confirm whether research, copywriting, and coding are included.

The core phases of a web design project

1. Discovery and goals

Define who the site serves, what visitors should do, and how success is measured. Outputs often include a written brief, competitor review, and success metrics such as inquiries, signups, or time on page.

2. Information architecture

Organize content into a hierarchy. The deliverable is usually a sitemap showing pages and their relationships, plus navigation labels. This is where you decide whether services, products, or resources get top-level placement.

3. Wireframes

Low-fidelity layouts that show structure without final visuals — where the headline, call to action, and supporting content sit on each page type. Wireframes are cheap to change, so review them carefully before visual design begins.

4. Visual design

Typography, color, imagery, spacing, and component styling are applied to the approved structure. A style guide or design system documents the rules so future pages stay consistent.

5. Handoff to development

The designer delivers mockups, assets, specifications, and interaction notes. Development then builds the site, and design review continues during implementation to catch issues that only appear in a browser.

Key decisions you will be asked to make

• Responsive layout — how the design adapts across phone, tablet, and desktop. Designing only for desktop is a common and costly pitfall.
• Typography and color — how many typefaces and colors, and whether they meet contrast requirements for readability.
• Accessibility — whether the design works for keyboard users, screen readers, and people with low vision. Retrofitting accessibility later is harder than designing for it.
• Performance trade-offs — large hero images, video backgrounds, and web fonts look impressive but add load time. Decide what is worth the cost.
• Content and conversion goals — the design should serve the content you actually have, not placeholder text that never gets replaced.

Typical deliverables and how to evaluate them

Common pitfalls

• Designing for desktop first and treating mobile as an afterthought.
• Skipping discovery, so the site reflects internal preferences rather than visitor needs.
• Ignoring content: a beautiful layout collapses when real headlines and product descriptions are longer than the mockup.
• Losing conversion focus — every page should make the next step clear.
• Treating design as finished at handoff, when many issues surface only during development.

If you are commissioning work, ask which phases are included, what deliverables you will receive, and who owns the files afterward. Those three answers prevent most misunderstandings before a project starts.

The South China Morning Post (scmp.com) covers China through several distinct desks — China, Economy, Tech, and Opinion — and the most efficient way to follow it is to pick two or three of those sections rather than reading the homepage top to bottom. This works if your goal is staying current on geopolitics, diplomacy, business, or technology without spending an hour a day on it. It assumes you can reach scmp.com and are willing to scan headlines before committing to full articles.

What SCMP actually covers on China

The site describes its China coverage as spanning geopolitics, diplomacy, the economy, technology, and lifestyle. In practice that means the China desk handles mainland politics and society, while Economy and Tech carry the business and industry angles, and Opinion runs columns and commentary. Hong Kong, Asia, the US, and World sections sit alongside these, so China stories also surface outside the China section when the angle is regional or global.

That overlap matters: a story about US–China trade could appear under China, Economy, or World depending on how the editors frame it. If you only watch one section, you will miss related coverage filed elsewhere.

Telling reporting apart from opinion

This is the single most useful habit for reading any news site, including SCMP. News reporting aims to relay what happened and attribute it to sources. Opinion pieces argue a position, and they are usually labeled as such — look for "Opinion," a columnist byline, or a first-person framing. Analysis sits in between: it explains why something happened and often carries more interpretation than a straight news report.

Practical check before you read:

• Headline voice — a claim stated as a conclusion ("X is losing the tech race") usually signals opinion or analysis; a factual frame ("X announced Y") signals reporting.
• Section tag — if it sits in Opinion, treat it as an argument, not a record.
• Byline type — staff correspondents vs. named columnists vs. contributors.

Mixing these up is the most common way readers come away with a distorted picture of a fast-moving story like China–US relations.

Building a scanning routine

You do not need to read everything. A workable routine:

1. Pick your lanes. Choose two or three sections that match your interest — for example China + Economy, or China + Tech.
2. Scan headlines first. Read only the headline and standfirst (the line under it) to decide if a story is worth opening.
3. Check the section and label. Confirm whether you are about to read reporting, analysis, or opinion.
4. Open selectively. Two or three full reads a day beats skimming twenty.
5. Use topic and region filters. SCMP groups content by topic and region, so you can track a specific thread — say, semiconductor policy or Hong Kong politics — instead of re-scanning the whole site.

If you want a lighter load, follow the China section headline feed only and dip into Economy or Tech when a headline signals a development you already track.

Free vs. paywalled content

SCMP operates a subscription model, so some articles sit behind a paywall while others are readable without one. The site does not publish a simple free/paid split you can rely on in advance, so the practical approach is:

• Judge before you click. Paywalled pieces often show a preview or a subscription prompt; if you hit a wall, decide whether the topic is important enough to you to subscribe.
• Do not assume access. A headline being visible does not mean the full article is free.
• Check current terms on the site. Pricing and what is included change, so verify on scmp.com rather than relying on secondhand descriptions.

Common pitfalls

• Treating opinion as news. The biggest one. A column arguing a position is not the same as a report of events.
• Watching one section only. China stories are filed across China, Economy, Tech, World, and Opinion — a single-section habit creates blind spots.
• Reading volume instead of relevance. Following China news efficiently means filtering hard, not reading more.
• Assuming all content is free. Budget for a subscription if you want consistent full access.

The short version

Use the China section as your base, add Economy or Tech depending on your interest, always check whether you are reading reporting or opinion, scan headlines before opening articles, and confirm current access terms on the site itself. That combination lets you follow China coverage on SCMP in a few minutes a day without losing the thread.

Getting a business website designed involves more than picking colours and fonts. A typical project runs through five phases: planning and content gathering, structure and wireframing, visual design, build and technical setup (domain, hosting, email), and launch with ongoing maintenance. The design work itself is only one part of the process — and the decisions you make early on, especially about structure and platform, directly determine how straightforward your domain, hosting, and connectivity setup will be later.

This guide walks through the whole sequence so you can plan realistically before you contact a designer or developer.

Phase 1: Planning and Content Gathering

Most delays in website projects come from content, not code. Before any design starts, you need to answer some basic questions and assemble raw material.

Questions to settle first

• What is the site for? A brochure site that generates enquiries, an online shop, a booking system, or a portfolio all lead to very different builds.
• Who is it for? The audience shapes tone, structure, and how much explanation each page needs.
• What does success look like? Enquiry form submissions, phone calls, online sales, or simply credibility when someone searches your business name.
• Who maintains it afterwards? If you want to edit text and images yourself, that pushes the project toward a content management system (CMS) rather than hand-coded pages.

Content to prepare before design begins

A designer can work with placeholder text, but the site will be better and faster to finish if you supply:

• Your logo in a vector format (SVG, AI, or EPS) if you have one
• Company description in short, medium, and long versions
• Service or product list with a sentence or two on each
• Contact details, opening hours, and location information
• Photographs — ideally original, high-resolution images of your team, premises, or products
• Any legal text you are required to display, such as a privacy policy

If you do not have photography, say so early. It affects both the design approach and the timeline.

Phase 2: Structure and Wireframing

Before visual design, the pages and their relationships need to be mapped out. This is usually called the sitemap and wireframe stage.

• Sitemap: a list of every page and how they nest. A typical small business site might have Home, About, Services (with sub-pages), Case Studies, and Contact.
• Wireframes: simple, unstyled layouts showing where headings, text, images, and buttons sit on each page type. No colours or fonts yet.

This stage is where you catch problems cheaply. If a page has no clear purpose, or if the navigation is confusing on paper, it will be worse once designed. Approving wireframes before visual design saves significant rework.

A note on mobile

Design should be planned mobile-first or at least mobile-aware from this stage. Most small business traffic now arrives on phones, and a layout that only works on a wide desktop screen will need to be redesigned, not just resized.

Phase 3: Visual Design

With structure agreed, the designer applies branding: typography, colour, imagery style, and spacing. You will typically see one or two key page designs first — usually the homepage and an inner page — before the rest are produced.

Things worth deciding at this point:

• Brand consistency: does the site match your existing signage, stationery, and social profiles?
• Accessibility: sufficient colour contrast and readable text sizes are not optional extras; they affect how many people can actually use the site.
• Calls to action: every page should make the next step obvious, whether that is calling, enquiring, or buying.

Expect at least one round of revisions. Two rounds is common; unlimited revisions usually signal a project that will drift.

Phase 4: Build and Technical Setup

This is where design meets infrastructure, and where choices start to have long-term consequences.

Domain names

Your domain is your address on the web. Points to settle:

• Do you already own it? If so, confirm you have login access to the registrar — not just the designer.
• Who should own it? The business should. A domain registered in a developer's name is a common and avoidable problem.
• Which extension? .co.uk and .com are the usual choices for UK businesses. Registering both and redirecting one to the other is a reasonable precaution.

Hosting

Hosting is the server space where the site lives. The right choice depends on the build:

Ask specifically about backups, uptime expectations, SSL certificates (the padlock in the browser), and what happens if you want to move the site later.

Email and connectivity

Your domain usually carries your business email, so email setup should be planned alongside the website, not after it. If staff work from an office, the broadband connection at that location affects how comfortably you can upload content, use cloud tools, and take video calls. Fibre availability varies by premises, so it is worth checking what is actually available at your address rather than assuming.

Build and testing

Before launch, the site should be tested on real devices, checked for broken links, and reviewed for spelling and grammar. Forms need to be submitted and confirmed as arriving in the right inbox. This stage is unglamorous but it is where most launch-day surprises are prevented.

Phase 5: Launch and Aftercare

Launch itself is usually quick: the site is moved to live hosting, the domain is pointed at it, and SSL is confirmed. The work that follows matters more.

• Backups: confirm they run automatically and that you know how to restore one.
• Updates: if the site uses a CMS, software and plugins need updating to stay secure.
• Analytics: some form of traffic measurement helps you judge whether the site is doing its job.
• Content ownership: make sure you have admin access to the CMS, the domain registrar, and the hosting account.

Roles and Responsibilities: Who Does What

Clear division of labour prevents most disputes. A typical split looks like this:

The most important principle: you should own your domain, hosting, and content, even if the provider manages them day to day.

Common Pitfalls That Delay Projects

• Content arriving late, especially photography and legal text
• Feedback coming from too many people with no single decision-maker
• Changing the scope midway — adding a shop or a booking system after design has started
• Domain or hosting registered in the provider's name
• No plan for who updates the site after launch
• Choosing a platform that cannot grow with the business

A Practical Pre-Project Checklist

Before you approach a designer or developer, have these ready:

1. A one-paragraph description of your business and what the site must achieve
2. A list of pages you think you need
3. Your logo files and any brand guidelines
4. At least some original photography, or a budget decision about sourcing it
5. Confirmation of who owns your current domain, if you have one
6. A named decision-maker on your side
7. A rough timeline and a realistic view of when you can supply content

Working through these phases in order — plan, structure, design, build, launch — keeps a website project predictable. The design is the visible part, but the planning and the technical setup underneath are what determine whether the site launches on time and remains useful afterwards.