한국어
← All categories
07

Visual & style

This is how you turn "make it a bit nicer" into numbers. Knowing padding from margin alone cuts your conversations with developers in half.

17 terms17 live demos
Numbers, not impressions

"Add some space" does not tell a developer anything. You have to say whether it is padding or margin, and how many pixels. This category is practice at translating a feeling into a value.

01

Whitespace

여백 · 화이트스페이스 / 네거티브 스페이스

When this comes up

"This looks empty — can you put something here?" — the most frequent request, and the one that needs an argument.

Space left deliberately empty. It does not have to be white; it means an area with nothing in it.

See it Try clicking
✗ Not enough space
This is a heading
A description follows
And another line
✓ Plenty of space
This is a heading
A description follows
And another line
Easy to get wrong

"The empty space is a waste, fill it with something" is the most common request and the most dangerous. Whitespace is not leftover room — it is the tool that makes the important thing stand out. Screens short on it look cheap.

Using it on the job

When making the case, do not say "it looks nicer" — say what it does: "this space is what makes the CTA button stand out".

Ask for it like this

This space is deliberate. The area above and below is kept clear so the CTA button below stands out, and filling it will reduce attention on the button. If content must be added, I would suggest another section.

02

Padding vs Margin

패딩 vs 마진

When this comes up

"Add some spacing" — the moment a developer stops because they do not know which one.

Padding is space inside the box (between the border and the content); margin is space outside it (the distance to other boxes).

See it Try clicking
Content

Yellow area = margin (outside the box) · blue area = padding (inside the box) · white = the actual content

Easy to get wrong

The first pair that trips up people without a design background. Remember it as "the box gets bigger → padding; the boxes move apart → margin". Say only "add some spacing" and the developer guesses wrong.

Ask for it like this

Set the space inside the card (padding) to 20px and the space between cards (margin/gap) to 16px. The cards should move apart, not grow.

03

Typography

타이포그래피

When this comes up

"Change the font" — the conversation about web font size and load time follows.

The system for handling typeface, size, weight and spacing. Over 90% of a web screen is text, which makes this the most important design element.

See it Try clicking
Light 300 — light body text
Medium 500 — default body text
Bold 700 — emphasis
Black 900 — large headings

Every extra weight is another font file.

Easy to get wrong

Web fonts affect file size and loading speed. Include five weights and it weighs five times as much. Pick only the weights actually used and pass those to development. Korean fonts are far larger files than Latin ones.

Ask for it like this

Use Pretendard as the web font with only two weights, 400 and 700. Korean fonts are large, so drop any weight not in use. Make sure text is visible before the font loads (font-display: swap).

04

Hierarchy

위계 · 시각적 위계

When this comes up

"Everything looks important and I do not know where to look"

Giving elements emphasis through size, weight and colour according to importance. It tells people what to read first.

See it Try clicking
✗ No hierarchy
Summer sale
Up to 50% off
Until 30 July
✓ With hierarchy
Summer sale
Up to 50% off
Until 30 July
Easy to get wrong

Make everything big because everything is important and nothing is. The rule is to pick "the single most important thing" per screen and make everything else weaker than it.

Ask for it like this

Please pick the single most important thing in this section. I will make only that large and bold and step everything else down. As it stands they are all the same size, so there is nothing directing the eye.

05

Type Scale

타입 스케일

When this comes up

"The font sizes differ between mockups" — when 15, 16 and 17px all show up.

A table of predefined text sizes from headings down to body. You use only the values on it.

See it Try clicking
H1 · 24px
H2 · 19px
H3 · 16px
Body · 14px
Caption · 12px
Easy to get wrong

Without a scale, mockups come in with 15px, 16px and 17px mixed together, and the developer has to reproduce all of it. Limit it to six to eight steps and both design and development get much faster.

Ask for it like this

Set a six-step type scale — H1 32 / H2 24 / H3 19 / Body 15 / Small 13 / Caption 11. Do not use sizes outside it.

06

Line Height

행간 · 라인 하이트 · 줄 간격

When this comes up

"The text feels cramped" — especially in Korean body copy.

The space between lines. Specified as a multiple of the font size.

See it Try clicking
1.15 — cramped
User experience design is the work of designing everything a person feels while using a product.
1.7 — comfortable to read
User experience design is the work of designing everything a person feels while using a product.
Easy to get wrong

Korean body text reads comfortably at 1.5 to 1.7 times the font size, slightly looser than Latin text. Too tight feels cramped; too loose and lines scatter. Headings go the other way — tighter, 1.2 to 1.3.

Ask for it like this

Raise the body line height to 1.7 — Korean reads better with more line spacing than Latin text. Tighten headings to 1.25 instead.

07

Letter Spacing

자간 · 레터 스페이싱

When this comes up

"The heading looks a bit spread out" — on large Korean headings.

The space between individual characters.

See it Try clicking
Tracking 0 — default heading
Tracking −3.5% — a tidier heading
SMALL CAPS · looser tracking
Easy to get wrong

The larger a Korean heading, the more slightly tighter tracking (about −2%) tidies it up. Conversely, very small text and Latin capitals need looser tracking to stay readable. Leave body tracking alone.

Ask for it like this

Apply −2% letter spacing to headings (24px and above). Leave body text at the default, and give Latin uppercase labels +10%.

08

Color Palette

컬러 팔레트

When this comes up

"This is our brand colour" — when you are handed one colour and have to say it is not enough.

The set of colours agreed in advance for a project.

See it Try clicking
50200400600900
Easy to get wrong

Colour has to be prepared in steps. Define only one primary and there is nothing for hover, disabled or backgrounds, so the developer invents brightness values. The norm is nine or ten steps per colour.

Ask for it like this

One brand colour is not enough on its own. We need colours for hover, disabled, backgrounds and borders, so please build a nine-step brightness palette (50–900) from the primary.

09

Primary · Semantic Color

프라이머리 · 시맨틱 컬러

When this comes up

"Our brand colour is red, so make the success message red too" — a request to push back on.

Primary is the colour that represents the brand; semantic colours have fixed meanings (success = green, warning = yellow, error = red).

See it Try clicking
Success — saved
Warning — expiring soon
Error — could not save
Easy to get wrong

Semantic colours have to follow what people have learned to expect. Make a "success" message red because the brand is red and people will read it as a failure.

Ask for it like this

Please define semantic colours separately from the brand colour — success = green, warning = yellow, error = red. Even with a red brand colour, success has to be green or people will misread it.

10

Contrast Ratio

명도 대비

When this comes up

"That grey is very light" — and on public sector projects, a legal review item.

The brightness difference between text and background, expressed as a ratio from 1:1 (identical) to 21:1 (black on white).

See it Try clicking
16.1:1 — comfortably enough ✓
5.0:1 — above the threshold ✓
1.7:1 — below the threshold ✗

That third line is hard to read, is it not? That is insufficient contrast.

Easy to get wrong

4.5:1 for body text, 3:1 for large text is the accessibility minimum (WCAG AA). Grey text may look refined, but too light and it is invisible outdoors in daylight. On public sector work this is a legal review item.

Ask for it like this

Bring all text up to WCAG AA contrast (4.5:1 body, 3:1 large text). The light grey supporting text currently falls short.

11

Dark Mode

다크 모드

When this comes up

"Support dark mode too" — this means building a second palette.

A theme built on a dark background. Reduces glare and saves battery.

See it Try clicking
Light
Card area
Dark
Card area

This site follows your device setting too.

Easy to get wrong

Never just invert the colours. Dark mode uses a slightly lifted grey rather than pure black (#000), and expresses layers through brightness differences rather than shadow. It amounts to a second palette, so put it in the schedule and the quote.

Ask for it like this

Please support dark mode. This needs a separate palette, not inverted colours. Use something in the #14141b range rather than pure black for the background, and separate layers with borders and brightness rather than shadow. Follow the OS setting but include a manual toggle.

12

Elevation · Shadow

엘리베이션 · 그림자

When this comes up

"Add a shadow" — without defined steps this ends up inconsistent.

Expressing how far an element floats through shadow. Used with a defined set of height steps.

See it Try clicking
0
1
2
3
Easy to get wrong

Shadows applied at random make a screen look messy. Define steps like 0/1/2/3 and manage them by rule — "cards are 1, modals are 3". In dark mode shadows barely register, so substitute borders or brightness.

Ask for it like this

Define four elevation steps — 0 (flat) / 1 (card) / 2 (dropdown) / 3 (modal). Document which step each component uses. Substitute borders in dark mode.

Related terms
13

Border Radius

보더 레디우스 · 모서리 둥글기

When this comes up

"Round the corners a bit more" — a value that easily ends up inconsistent.

The value that decides how rounded a box's corners are.

See it Try clicking
0
5
12
999
Easy to get wrong

Inconsistent values look sloppy. Set steps such as 4, 8, 12 and 999px (fully round). And when a box sits inside a box, the inner radius should be smaller than the outer one to look right.

Ask for it like this

Standardise border radius into four steps — sm 6px / md 10px / lg 16px / full 999px. Make nested boxes 4px smaller on the inside than the outside.

14

Opacity

오퍼시티 · 투명도

When this comes up

"Make the text a bit lighter" — doing it with opacity breaks the contrast.

How see-through an element is. 0 is fully transparent, 1 is opaque.

See it Try clicking
1.00.60.30.1
Easy to get wrong

Using opacity to lighten text breaks the contrast ratio. If you need grey text, do not lower the opacity — specify the grey as a colour. Save opacity for things like dimming over a background image.

Ask for it like this

Do not lighten supporting text with opacity — set the grey value directly. With opacity, the contrast changes depending on the background, which makes the accessibility threshold hard to hold.

15

Icon Set

아이콘 세트

When this comes up

"Just add a few more icons" — pull them from another set and it shows.

A collection of icons drawn in one style, consistent in stroke weight, corner treatment and grid size.

See it Try clicking

Only icons whose meaning is unmistakable can go without a label. Label the rest.

Easy to get wrong

Mixing sets is immediately visible. Icons with different stroke weights sitting side by side look sloppy. Pick one set at the start of the project and draw any missing icon to match it.

Ask for it like this

Standardise on one icon set (Lucide, for example). For icons the set does not have, do not pull from elsewhere — draw them to the same stroke weight (1.5px) on a 24px grid.

Related terms
16

SVG vs Bitmap (PNG/JPG)

SVG vs 비트맵

When this comes up

"The logo looks blurry" — after handing the logo over as a PNG.

SVG is a vector described mathematically, so it never breaks up however far you enlarge it. PNG and JPG are pixel images and fall apart when scaled up.

See it Try clicking
SVG (vector)

Stays sharp when enlarged

PNG (bitmap)

Goes blurry when enlarged

Easy to get wrong

Always hand over logos and icons as SVG. Photos go as JPG, and images needing transparency as PNG. WebP is much smaller and now widely used for photos.

Ask for it like this

I will supply the logo and icons as SVG. Use WebP for photographs, with JPG as a fallback for browsers that do not support it.

17

Image Scale Factor

@2x · @3x · 해상도 배수

When this comes up

"The images look blurry" — on high-resolution screens.

Preparing images at two and three times the size for high-resolution (retina) screens.

See it Try clicking
@1x
100×100
@2x
200×200
@3x
300×300

They all appear the same size on screen, but the files themselves are larger.

Easy to get wrong

Without multiplied exports from the designer, a developer cannot do anything. An image displayed at 100×100 must be exported at 200×200 (@2x) to look sharp on a high-resolution screen. Put it on the handoff checklist.

Ask for it like this

I will export image assets at @1x, @2x and @3x. Filenames will follow the format imagename@2x.png throughout.

Related terms