Visit site×
Website Redesign · 2026

Yeosu Saegomak Redesign

I redesigned the website of an export-driven seafood company around one path: an overseas buyer getting from the first page to an inquiry.

Role
Design · Frontend
Period
2026.06
Scope
Web · Mobile · KO/EN
Tools
Codex · Claude Code · GSAP
Overview

An export company whose website made it hard for buyers to get in touch.

Yeosu Saegomak processes cockles from Yeoja Bay in Yeosu and exports them overseas. On its old website, the path from seeing a product to sending an inquiry was hard to find. I defined that problem and proposed it before our first meeting, then took the work through information architecture and a design system to page design and frontend build.

34old screens audited
4core problems
28pages rebuilt
2languages (KO / EN)
Problem Definition

I started by defining the problem

I audited 34 screens of the old site, grouped what I found into four problems, and paired each with a direction. What follows is that proposal, rebuilt for this page.

The old site

Old home page, full length
Home
Old menu, full length
Menu
Old recipes page, full length
Recipes
Old production page, full length
R&D · Production
01

Visual and technical decay

  • No HTTPS, so browsers showed security warnings
  • Built on an eight-year-old web framework (Bootstrap 4)
  • Pinch-zoom blocked on mobile (an accessibility violation)
  • Unoptimized JPGs everywhere, slowing every page
02

Misleading information architecture

  • Four "Business" cards on the home page all led to the same page
  • Desktop, mobile and footer menus were defined separately
  • Bulletin-board structure leaked into URLs, confusing users and maintainers
03

No path to conversion

  • No purchase or inquiry button on the home page
  • No search and no category filters
  • Products, recipes and social were disconnected, so B2B and B2C leads went nowhere
04

No brand consistency

  • A generic Gnuboard template with no brand identity
  • No brand color or type system
  • Clean waters and fishermen shareholders, the brand’s real assets, never came across
UX Solution

Cut, reduce,
rebuild.

01

User-first design

Drop the supplier-centered menu and rebuild navigation around the tasks visitors look for first.

02

Mobile first

Mobile is 70% of traffic, so design for it first and deliver a fully responsive view.

03

Data-driven IA

Base the structure on GA4 data and heatmaps, not hunches.

04

A design system the team can run

Go beyond one-off pages and hand over a component library the in-house team can combine and extend.

Target

Who comes in, what they check, where they go

Visitors fell into three groups: overseas buyers, domestic partners and consumers. Each wanted to check something different and go somewhere different. The goal was to get every one of them through the information they need and straight to their next step.

WHOCHECKSGOES TO
Overseas buyerProductsCertificationsExport capacityTrade inquiry
Domestic partnerProductsSupply termsSupply inquiry
ConsumerBrandsProductsOnline store ↗
Design Concept

Solid, expert,
and global.

I set three impressions as the design criteria, so an overseas buyer seeing the company for the first time could judge whether it was worth doing business with.

Solid.

Deep navy, a blue gradient and heavy headlines for a trustworthy first impression.

Expert.

The HACCP facility and 13-step production process, shown in real photos.

Global.

An export catalog, markets and certifications that answer a buyer’s questions first.

Information Architecture

Rebuilt around brands, products and inquiries

Rather than taking the client's requests as they were, I made the case for the structure from the buyer's point of view.

Three principles

Brand page
01

Brands tell a story

Brands became a top-level menu

Product page with type tabs
02

Products are found by type

Meal kit · Ingredient · Raw tabs

Inquiry page
03

Inquiries are one step away

An inquiry button in the GNB on every page

Before · Old menu

  1. CompanyCEO message · About
  2. R&DQC · Production
  3. BusinessFour cards, one page
  4. ProductsTwo detail pages per product, no filters
  5. RecipesNot linked to products
  6. CommunityNotices · Press · Video · Brochure

After · New sitemap

  1. About UsOverview · Production · Quality · Track record
  2. BrandsUmjine Pocha · Chilsan · Yeosu Olim
  3. ProductsTabs by type (meal kit · ingredient · raw …)
  4. ExportExport catalog · Markets · Certifications · OEM/ODM
  5. News & IRNotices and press in one place
  6. ContactBuyer · Domestic · OEM/ODM inquiries
User Flow

From brand to inquiry, a buyer’s four steps

These are the live pages a buyer moves through: see the brand, pick products, check export terms, and send an inquiry.

1

Brands

See each export brand on its own page

2

Products

Filter products by type with tabs

3

Export catalog

See products, markets, certifications and OEM in one place

4

Buyer inquiry

Ask straight from the GNB

Umjine Pocha brand page, full length
Products page, full length
Export catalog page, full length
Buyer inquiry page, full length
Drafts

First draft and second draft

In the first meeting the client asked for a site as dynamic as a big corporation's. I built the first draft to that brief, with a video hero, and the feedback came back that it felt cramped, with far too much scrolling. I reworked the second draft around that feedback.

  1. Proposal
  2. First meeting
  3. First draft
  4. Feedback
  5. Second draft · Live
First draftHeavy on video and motion
Second draft · LivePared back
What I learned

When the client asked for a site as dynamic as a big corporation's, what they really wanted was less the motion itself than to look like a company buyers could trust. I learned to confirm the goal behind a request before acting on its wording.

Design System

Design System

To give overseas buyers a solid, trustworthy impression, I built the color and type rules around blue and navy. As a global site made under an export voucher program, it uses Noto Sans KR, which covers many languages evenly. And since this is a food brand, inquiry buttons and active tabs get an appetizing orange.

Color
Blue#2450C9Base · Emphasis · CTA
Navy#172A5CHeadings · GNB
Point#DE5427Active tab · Inquiry button
Export Gradient#2A5BE6 → #173BBDLanding · Export backgrounds
Navy 900#0F1A47Footer · Dark backgrounds
Ink#16181DBody text
Blue Bright#3D6FD8Hover · Secondary emphasis
Point 700#C1461FPoint hover
Typography · Noto Sans KR
Page titleExport76 / 800 / −1.9
Section세계 식탁을 향한 수출 제품 카탈로그40 / 800 / −0.4
Intro청정 바다에서 시작한 수산식품을 글로벌 식탁까지20 / 400
Card title본사18 / 700
Body산지 원물의 품질과 제품별 선별 기준을 우선합니다.16 / 400 / 1.8
LabelEXPORT PRODUCT CATALOG13 / 400 / +0.18em

Sub-menu Tab

수출 카탈로그수출국인증·규격

Section Label

EXPORT PRODUCT CATALOG세계 식탁을 향한
수출 제품 카탈로그

Buttons

문의하기💬 문의하기Contact Us

Product Card

Product cards: NEW badge, brand, name, spec chips

Badge · Brand · Name · Description · Spec chips (160g · 300g · export-ready)

Inquiry Form

Buyer inquiry form

Type · Company · Name · Phone · Email · Message

UI

The production page, old and new

On the left, the old page. On the right, the full new page. As you scroll, the old page stays put while the new one runs to the end.

Old
Old production page, full length
New
New production page, full length

Full pages

Quality page, full length
About · Quality
Export markets page, full length
Export · Markets
English product detail page, full length
Product Detail · English
Mobile First

70% of traffic is mobile, so I designed for mobile first

Mobile home
Home
Mobile brand page
Brand · Umjine Pojangmacha
Mobile export catalog
Export catalog
Mobile buyer inquiry
Buyer inquiry
Mobile export catalog in English
Export catalog · English

Hover over a phone to scroll its screen

KO / EN

One language button, the same page in English

To meet the export-support program’s requirements, I added an English site with the same structure through i18n.

Export catalog in KoreanExport catalog in English
Buyer inquiry in KoreanBuyer inquiry in English
How I Worked

AI was the design tool. I set the direction and the standards

Instead of Figma mockups, I designed directly in code with Codex and Claude Code. I set the design rules first and kept the AI inside them.

01 · AI Agents

From research to QA, split by role and run at once

I ran separate AI agents for research, planning, design, frontend and QA in parallel, so work that would take a long time in sequence moved forward together.

02 · DESIGN.md

I wrote documents before code

Before building, I wrote specs such as DESIGN SITEMAP COPY TONE MOTION, plus an audit of the old site’s structure. Every later change was measured against them.

03 · Human in the Loop

Anything outside the spec, the AI had to stop and ask

So the AI wouldn’t fill gaps on its own, it stopped and asked whenever a decision was needed. We talked briefly, I set the direction, and then it built.

04 · Variations

AI made the options. I made the call

Even for a single production banner, I had four versions built (floating cards, diagonal split, timeline and accordion), put them side by side and picked one.