All workEsc

Buzzvil mediums.One brand, builtto stay current.

As Buzzvil prepared for a stock-market listing, its online presence needed to feel like one company. I connected its key websites through a shared brand system and an agent-driven way to keep them current.

Buzzvil / HomepagePreview
The Buzzvil homepage landing: Your brand is unique. So is every person you reach, beside a colored particle sphere on a light canvas.

The new homepage, in its final content review.

One company shouldfeel like one company.

Customers, developers and future colleagues met Buzzvil through different websites. I brought their typography, color, layout and interaction into a shared system, so each touchpoint could build the same sense of trust.

Design

Live
Buzzvil Design’s live homepage with its Design ships here statement, purple-to-pink typography and a wireframe sphere.

Designers update the site with AI assistants.

Visit Design

Docs

Live
The live Korean developer documentation homepage, with Android and iOS integration guides.

Technical writers update the documentation with AI assistants.

Visit Docs

Tech blog

Live
The live tech blog with a purple-to-pink title, geometric illustration, search, topic filters and recent engineering articles.

Anyone at Buzzvil who wants to post can contribute with AI assistants.

Visit Tech blog

AI assistants prepare the changes. People review what gets published.

Describe the change.Review the page. Ship it.

I built the repository around agent-driven contribution: app instructions, content conventions and shared UI. The interface for an update became a request and a preview, with people responsible for what ships.

Start with the person who knows.

The content owner supplies the intent and facts. The agent reads the app instructions, uses the shared components and prepares the edit in the repository. No CMS entry or manual page assembly.

A change to prepare

Update the SDK release notes.

ContextRelease facts
InstructionsAGENTS.md
MaterialShared UI + content rules
An example contribution
Used beyond Design

A colleague, Eden, tested the workflow with a real update to the developer release notes. To make previews accessible to contributors, I proposed a shared deployment path; Edward, an engineer, implemented it.

Zoom in · Publishing safeguards

Opening updates to more contributors also made mistakes easier to repeat. The repository needed to enforce the rules, including keeping translations in sync.

Try the release check Illustration of the repository check
Edition check passed

The edition was prepared from the current source. People still review meaning and claims.

Simplified SHA-256 checkedition.sourceHash === sha256(sourceBytes)
Korean / Source가

하나의 브랜드,
일관된 경험.

모든 웹사이트는 같은 디자인 규칙에 따라 운영됩니다.

Source · v1Original Markdown
English / CounterpartAa

One brand.
A consistent experience.

Every website follows the same design rules.

Translated from v1Prepared before build
Code and link destinations stay intact. Prepared by an agent. Reviewed by a person. Served as static pages.
Design in codeShared design values + reusable React elements
One repositoryNext.js · TypeScript · Turborepo
Review and deliveryGitHub Actions + Vercel previews
Zoom in · The redesign’s loading cost

A considered brandshould feel fast, too.

The first redesign waited for JavaScript before showing its content. I moved reading back to server-rendered HTML, removed duplicate motion code and limited animation work to where it was needed.

Code downloaded to make the homepage interactive68% less to download.
Before the overhaul
1,008 KB
After
322 KB
Before and after the redesign, measured in local production builds. This compares downloaded code, not page speed.
201

legacy URLs checked
Still working after the migration

Keep the history intact.

The migration also preserved how readers arrived: old links, search results and feeds. A faster, newer page still had to respect the reader who bookmarked the old one.

A small bug with a real consequence

Uppercase filenames worked locally on my Mac but returned 404s on Linux. Normalizing the paths fixed the deployed pages. An RSS identifier change also made an old article appear new in Feedly. Those failures made redirects, filenames and feed identity part of the design work.

Back to the brand experience

Product stories becameexperiences people could try.

Consistency should leave room for expression. The corporate site explains Buzzvil through experiences people can try: discover an offer, participate and see the reward. Product demonstrations turn an unfamiliar B2B platform into something tangible.

A moment in the homepage story pairs the fictional Lumière skincare brand with its goal: more purchases.
01 / Begin with the advertiser. Brand context and the campaign goal give the story a starting point.
The homepage turns the same skincare brand into three phone-sized experiences: a discovery ritual, a skin-needs selector and a returning-customer refill choice.
02 / Make the idea tangible. Different customer moments become experiences to explore, using a fictional brand.
15

bilingual phone demos
reported October 16

  1. Enter
  2. Make progress
  3. Return to rewards

Rich when opened. Light while browsing. The landing loads WebP previews first. A sandboxed demo loads when someone opens it, using a shared runtime across the experiences.

Interactive demonstrations of the advertising experience. The product work behind Game UA

The foundation is live.The corporate site comes next.

Design, Docs and the tech blog are live, with their contributors already using AI assistants to keep them current. The homepage is in its final phase of content revisions, with launch expected late in 2026.

Already in use
  • DesignDesigners + AI assistants
  • DocsTechnical writers + AI assistants
  • Tech blogContributors across Buzzvil + AI assistants
Homepage / Final content revisionsLate 2026Expected launch

Most teams will be able to contribute through AI assistants. The homepage will use a more involved review process, giving teams a way to contribute while keeping the company’s public messaging consistent.

What I learned.

A brand has to survive the next edit.

The redesign was only the first release. Shared components, agent instructions and publishing checks carry those decisions into the changes other people make.

Automation moves the work to judgment.

Agents handle implementation, formatting and repeatable checks. People still own the facts, the message and the decision to publish. That is where the contribution process needs to be clearest.

Technical quality is brand quality.

A slow page, a stale translation or a broken bookmark changes how the company feels. The invisible parts of the system deserve the same design attention as the hero.

Image detail

Loading full-size image…