Hannah Color Analysis

The business problem

A local service business needs more than an attractive landing page. Visitors need to understand an unfamiliar service, see a credible expert, compare options, and reach booking with confidence, especially on mobile, where much of that discovery happens.

Build the journey, not isolated pages

I organized the product around Home, Services, and About routes with shared navigation and reusable content patterns. Calls to action lead into the same booking system used to manage availability and payment.

• Responsive hero assets are tailored for desktop and mobile rather than forcing one oversized image everywhere.
• Typography, imagery, and spacing create a premium but approachable service brand.
• Lead capture provides a lower-commitment path alongside direct booking.
• Feature flags allow incomplete capabilities to ship safely without invasive code changes.

Make discoverability part of the build

SEO is implemented as an engineering concern, not a launch-day checklist. Per-route metadata is paired with robots and sitemap assets, and a post-build step produces crawlable output for the client-rendered application.

• Route-specific titles and descriptions create useful search and sharing context.
• Build automation keeps generated SEO artifacts aligned with releases.
• WebP assets reduce payload while preserving visual quality.
• Production analytics closes the loop between launch and future iteration.

Connect marketing to operations

The site links into a client-branded WhatNow booking experience with payment integration. That end-to-end ownership removes a common handoff: the public site and the operational workflow were designed as one product journey.

Make deliberate delivery tradeoffs

A content-led acquisition site did not need the operational complexity of the scheduling platform. React and Vite kept the build lightweight and made the branded experience easy to iterate, while React Router preserved distinct customer journeys and route-level metadata. The tradeoff of client rendering was addressed with generated crawlable output instead of moving the entire product to a heavier server-rendered architecture.

What I learned

A service website works best when the brand, site performance, and booking handoff feel like one journey. Focusing only on the landing page would have made the most important step, moving into booking, feel disconnected. This project reinforced a practical lesson for me: automate the work that tends to break, reuse the booking platform, and skip infrastructure that does not help the customer.

Senior engineering signal

This project demonstrates pragmatic scope control. I chose a lightweight stack for a content-led site, automated the pieces most likely to regress, optimized the assets that drive perceived quality, and integrated the site with the deeper platform only where it created business leverage.