Bilingual site · Interaction · Delivery system
Make one project
make sense.
A complete service website I designed and developed for my own practice. It turns a broad offer into three understandable paths, then helps a visitor write a useful project brief before getting in touch.
Explore the live English preview
01 / The design question
Can a service page feel considered?
Small engineering services often read like a list of promises. I wanted the site to show how I work: clarify the input, define a bounded outcome, make the work visible and leave the final decision with a person. The three paths—Build, Coach and Review—use an indexed editorial layout instead of a wall of generic cards.
The interface shares one visual system across Chinese and English. Dense type, deliberate whitespace, fine rules and one electric-blue accent give it a distinct voice without relying on stock photography or invented testimonials.
02 / Responsive and bilingual
The same idea,
two rhythms.
The mobile version changes the composition rather than shrinking the desktop layout. Navigation, the offer and the main action remain readable in a narrow viewport. Both languages have their own complete copy and working routes.

03 / Useful interaction
A brief before
the email.
Instead of pretending to be a full booking or payment system, the site helps a visitor articulate one goal, current materials, timeframe and scope. JavaScript creates a copyable summary locally and enables an email handoff only after the brief is generated. Nothing is silently uploaded or auto-sent.

One system, two routes.
Separate Chinese and English pages share the same hierarchy and responsive visual language.
User-controlled handoff.
Service selection and form inputs produce a summary; the visitor chooses whether to copy or open email.
Evidence in the browser.
Node tests, build checks and recorded mobile, tablet, desktop, keyboard and form checks support the implementation.
04 / What shipped
A working site,
with honest scope.
The bilingual site and its interactive brief builder run in a Cloudflare Pages preview. The preview is intentionally excluded from search indexing while the service offer is being validated. This is my own product and front-end project—not a paid client commission, a customer testimonial or proof of revenue.
It demonstrates the ability to design a clear service journey, build it with dependency-light code, verify it across screen sizes and explain what the software does and does not do.