Short looping studio video of Lian Li coding.

Restructuring
L by Lian’s website

To present web design and photography as one practice.


My role in this project

I led the project end-to-end: defining the structure, designing the interface, building the front-end, and validating the experience with usability testing.

  • UX: information architecture and navigation structure
  • UI: layout, typography, colour system, and components
  • Build: HTML, Tailwind CSS, JavaScript, and GitHub Pages deployment
  • Validation: usability testing with five participants
  • SEO: technical SEO, metadata, and AI-search optimisation

The What

This self-initiated case study looks at the redesign of my own portfolio website. The challenge was to present two related areas of work — web design and photography — without making the site feel split or unclear.

The redesign gives web design a clearer lead role, while keeping photography as part of the overall practice rather than a separate experience.

Project Summary

Project
L by Lian — website redesign
Focus
Presenting web design first, with photography as a supporting discipline
Role
UX, UI, information architecture, visual direction and front-end build
Tools
Figma, HTML, Tailwind CSS
Outcome
A more coherent structure where web design leads and photography supports the overall identity of the practice.

The Why

Adobe Portfolio is built for photography, which made it difficult to present my web design work in a clear and intentional way. To show website projects properly, I had to create a separate site, and the templates limited how the work could be structured and experienced.

The result felt fragmented and harder to understand than it should be.

The How

I designed and built a custom static site so I could control layout, navigation, and pacing properly. I organised the work around case studies rather than loose pages, which makes the site easier to scan and easier to grow over time.

Before

The previous site was built on Adobe Portfolio when photography was still my main focus. As my work shifted towards UI/UX and web design, the platform’s template structure made it harder to show both areas of work in a way that felt clear and intentional.

As the amount of work grew, it also became harder to shape proper case studies. Navigation, pacing, and emphasis were limited by the platform, so the site often needed extra explanation instead of letting visitors understand it for themselves.

Screenshot of the previous photography portfolio built with Adobe Portfolio.
Old photography portfolio
Screenshot of the previous mobile-first web design portfolio built with Adobe Portfolio.
Old mobile-first web design portfolio
Showing both web design and photography meant maintaining two separate websites, which made the overall practice harder to present as one coherent offering.

Structure & navigation decisions

The strongest decision in this project was separating two disciplines while keeping the experience cohesive.

Figma sitemap diagram showing the site navigation hierarchy and user paths across Home, UI/UX Web Design, Photography, Shop, About, and Contact.

Outcome: primary web-design route, separate photography section, simplified mobile navigation.

This sitemap shows how the site is organised so visitors can find things fast.

Style guide

A single style board to keep type, colour, and components consistent.

Figma style guide board showing typography, colour palette, iconography, and button styles.

Screens

Screens that prove hierarchy: primary path, secondary exploration, optional depth.

Let’s work together

Make it obvious. Make it beautiful.

I design and refine websites so people can understand what you do.

Designed + built by me • validated with 5 users

Build & QA

How I planned, built, and checked the site.

Design and build process

I began with hand-drawn wireframes to work through layout and navigation, then moved into Figma for the moodboard, low-fidelity wireframes, and site map. From there, I built the site in code and refined it as the structure became clearer.

I also use Copilot to help spot errors and speed up troubleshooting while I work. The design decisions and final edits are still mine, and I check the site myself across different screen sizes before publishing.

Tools: Figma, HTML/CSS, Tailwind, JavaScript, GitHub Pages.

In short: wireframes → Figma → build in code → refine → test.

What I checked

  • • Mobile and desktop layout behaviour.
  • • Menu open and close states, including keyboard access.
  • • Links, image loading, and console errors.
  • • Lightbox open and close behaviour, including Esc and overlay click.
  • • Accessibility basics such as contrast, focus visibility, and reduced motion.

Accessibility

  • • Keyboard access for the menu and lightbox, with visible focus states.
  • • Contrast checks and clear labels.
  • • Interactions that remain comfortable with reduced motion enabled.

Results

Early signals from usability testing and direct feedback (no analytics baseline yet).

Clear first impression

Most people understood what I do within the first few seconds.

Self-navigation

People were able to find web design work and contact details without needing help.

Mobile clarity

Simpler labels and clearer cues reduced hesitation on mobile.

Summary: The new structure makes the offer easier to understand and removes the need for explanation.

Validation

I tested the site with 5 people (ages 35–60) to see how easily they could understand and move through it, especially on mobile.

What I tested

  • • Can people understand what I do within a few seconds?
  • • Can they find web design work quickly?
  • • Can they locate photography without confusion?
  • • Can they reach Contact easily?
  • • Does the navigation feel straightforward on mobile?

Sample: 5 participants, ages 35–60.

What changed after testing

  • • Replaced some navigation dots with arrows for clearer direction.
  • • Simplified labels to reduce hesitation.
  • • Reduced competing calls to action.
  • • Adjusted spacing on mobile to improve scanning.

Result

Testers described the site as easy to use and were able to move through it without guidance.

Constraints

These constraints shaped the decisions and explain why the structure works the way it does.

Project constraints

  • • One-person project (strategy, design, build, QA).
  • • Needed full layout control beyond template platforms.
  • • Photography needed to remain part of the work, not only illustrative.
  • • Tone needed to feel relevant.

Design constraints

  • • People scan quickly, so structure needs to be obvious.
  • • Two disciplines need to coexist without competing.
  • • Mobile-first: reduce effort and avoid dense layouts.
  • • Labels need to feel familiar and easy to follow.

About the author

Lian Li is a UX/UI designer and garden photographer working under the name L by Lian. She designs mobile-first websites with clear structure, thoughtful visual hierarchy, and strong image direction.

hello@lbylian.com

Web design for garden designers, artists and visually led studios.

L by Lian is a Sheffield-based web design studio focused on made-to-measure websites for creatives, with selected garden photography.

Web design projects available year-round.

© L by Lian · Sheffield, UK
By using this website you agree to the Terms & Conditions.
Design & photography by L by Lian.