05PERSONAL SITE / DESIGN & BUILD

KENLIN.CC

A readable site bringing technology, photography and thought together, refined through AI-assisted design reviews.

Role
PERSONAL PORTFOLIO / EDITORIAL WEB · Self-directed build

2026

DESIGN PUBLICATION

01

The website itself is part of my work.

Bring the eye I developed through photography into my website.

I wanted one place for my photographs, technical projects and personal introduction. The site is more than a place to put projects; it is a project I want to make well.

I wanted more than a template with different text and images. I made the decisions about planning, structure, visuals, implementation and publishing, and worked with AI to build them.

Bring the eye I developed through photography into my website.

  1. Photography

  2. Technology

  3. Introduction

The website itself is part of my work.

02

Organize the content before choosing the structure.

One navigation structure for JP, Chinese and EN.

I first sorted the work, journal, photography, about and contact content, then gave each a clear entry. Japanese uses /, Chinese /zh and English /en, while language switching keeps the reader on the same page.

While deciding the structure, AI suggested separate Spring Boot and Vue applications. After understanding how Next.js works with Vercel, I chose Next.js for this content-focused site. I checked the reasons before accepting any suggestion.

ROUTE SYSTEM

JP / · 中文 /zh · EN /en
  1. Home

  2. Work

  3. Journal

  4. Photography

  5. About

  6. Contact

THREE LANGUAGESJP / · 中文 /zh · EN /en

JP /, Chinese /zh and EN /en: three languages, six site sections.

03

Find my visual direction through photos, type and fine rules.

A magazine-like feel that remains easy to read.

The initial AI cover had an industrial feel I did not like. I brought in my own ideas and photographs, rendered previews and refined them. The direction moved toward photographs, paper texture and space.

Mincho headlines set the tone while body text stays legible. Vermilion marks key points and green rules connect flows. Wide screens use columns; phones keep the same reading sequence vertically.

VISUAL LEDGER

What we wanted / What we chose
  1. 01

    Photography and paper

    Bring photography and technology together with a calm reading surface.

  2. 02

    Type and emphasis

    Mincho headlines, legible prose and meaningful color.

  3. 03

    Reading on phones

    Keep images and paragraphs in order, with keyboard navigation.

04

It took four versions to get closer to what I wanted.

Too ordinary, too much like a photo album, too much like a template.

Version one was too ordinary, version two felt like a photo album, and version three looked too much like a template. Version four brought photography, technical work and my introduction into better balance.

VERSION LINE

V1 / V2 / V3 / V4
  1. 01

    V1

    Ordinary

    The first site felt too ordinary.

  2. 02

    V2

    Photo album

    The photo-album direction overshadowed technical work.

  3. 03

    V3

    Template

    The template-like direction lacked my own character.

  4. 04

    V4

    Current direction

    Balance photography, technical work and my introduction.

My review of each direction; the images below are retained design previews.

PHOTOGRAPHYA retained photography-page design preview showing the photo and category layout.
A KENLIN.CC photography-page visual study with a large cherry-blossom photograph and four photo categories
HOMEA retained homepage design preview led by photography.
A KENLIN.CC home-page visual study featuring Mount Fuji and star trails
JOURNALA retained Journal design preview: Lab for technical notes and Stories for photo essays.
A KENLIN.CC Journal-page image with Lab and Stories arranged side by side

05

Build with AI; decide the direction myself.

Discuss, preview and check the real page.

Much of the frontend was built with AI. I explain what I want, choose tools suited to each task and check whether the actual page matches that direction.

Rendered previews help, but I still need to inspect the website itself. Requirements, technology choices and design decisions remain mine. The detailed collaboration process is covered in the AI workflow case.

SITE LOG

DISCUSS / PREVIEW / CHECK
  1. 01DISCUSS

    Discuss

    Explain the requirements and reference direction.

  2. 02PREVIEW

    Preview

    Review rendered previews, then refine design and implementation.

  3. 03CHECK

    Check

    Check reading and interaction on the real page.

Use previews to discuss the direction and the real site to check the result.

06

Turn the site I imagined into a site people can use.

Current

  1. 01

    One entry for photography, technical work and my introduction.

    I will keep refining the site. Each change should make projects easier to understand and articles easier to read, rather than simply adding layouts.

Current

KENLIN / 06

One entry for photography, technical work and my introduction.

KENLIN.CC — LIN CHIACHENG