Skip to content
MROOT

FICTIONAL BUSINESS DEMO / MOBILE INFORMATION DESIGN

Huron
Valley.

Work first.
Contact close.

A fictional landscaping site organized around paired work examples and persistent mobile contact paths.

01 / THE WORK COMES FIRSTHURON
VALLEY.
02 / THE NEXT STEP STAYS CLOSEWork first.
Contact close.

A page to explore.
Two paths within reach.

Schematic page and contact-bar illustration. Not landscaping photographs, testimonials or a product capture.
Fictional demo~3 min read
My contribution
Design, development
& deployment
Context
Demo · Fictional landscaping business
July 2026 account
Built with
React · TypeScript · Vite
Tailwind CSS · Static Worker

01 / THE BUILDShow the work before asking for the enquiry

Huron Valley is a fictional lawn-care, landscaping, and snow-removal business. I designed its site around two things I wanted visitors to find quickly: examples of the work and a way to get in touch.

The gallery leads. Four paired before-and-after examples introduce the services, followed by six service entries, review-style content, and a service-area list. They belong to the demonstration. They are not evidence of real customer transformations, verified reviews, or enquiries won.

That distinction matters for a portfolio: the work here is the page structure and implementation, not a landscaping business I operated.

02 / THE BUILDKeep the next step near the work

On a phone, the original site keeps two actions in a fixed bottom bar. One opens the phone's calling handler; the other scrolls to the quote form. A visitor can keep looking through the page without returning to the header to find those paths.

The miniature below lets you explore that arrangement without calling anyone. Scroll inside the phone, jump between sections, or use the two action buttons. The panels are diagrams of content slots, not photographs or a recreation of the original site.

INTERACTIVE / MOBILE ACTIONS

The page moves. The next step stays.

Scroll inside the phone, then try the two example actions. Nothing calls or submits.

HURON VALLEY / PAGE MODEL
01 / WORK EXAMPLES

Show the work.

Paired-photo positions. No work photographs supplied.

DIAGRAM, NOT A CUSTOMER RESULT
02 / SERVICE CONTEXT

Explain what is offered.

  • Lawn care
  • Landscaping
  • Snow removal

Service families from the source account, not the full six-entry catalog.

03 / THE NEXT STEP

Reach the quote section.

The original form still needs delivery integration. This page has no quote fields or submission endpoint.

No enquiry is sent.
New explanatory miniature. Original quote delivery remains unfinished; the call button here explains the tel: path without opening it.
Reading the figure: Work examples introduce the services. A mobile bar keeps the quote and call paths available. The paths do not prove delivery or a completed call.

The two buttons do different jobs. Reaching a quote form does not deliver an enquiry, and opening a calling handler does not establish that a conversation happened. The documented quote form still needs a delivery backend.

03 / THE BUILDPut repeatable details in one place

The build uses React 19, TypeScript, Vite, and Tailwind CSS v4, with a static deployment on a Cloudflare Worker. Services, gallery pairs, reviews, and contact details are typed records in data.ts.

That gives the layout a shared source for business information. It does not give a business owner an editing dashboard; changes to the records still belong to the code workflow.

My contribution covers the design, development, and deployment of this fictional-business example.

04 / THE BUILDWhat is built, and what is still an idea

The paired gallery and mobile action bar are part of the documented build. Quote delivery and an interactive before-and-after slider are the improvements named in the original article.

The sample on this page explains the action bar. It does not quietly mark either of those improvements as shipped. A real version would also need permitted work photos, genuine business details, and reviewed customer feedback rather than demonstration content.

05 / THE BUILDWhat I would carry into another build

Start with the information a visitor came to see. Then make the next action easy to reach without covering that information.

For this project, that meant a gallery-led layout and a mobile contact bar. The important decision was their relationship—not adding more sections or making the hero larger.

Source, dates, and what this page verifies

This rewrite is based on the supplied fictional-business project and article originally published July 17, 2026. Original dates and source addresses are retained. The original repository and live application were not audited.

The public articles were checked again on September 29, 2026: the unusual Huron shadow class and missing Maple print-CSS numbers remained visible. Both original excerpts are preserved, not silently repaired.

New phone/menu illustrations, sample menu data, category/search controls and print-card composition are labeled teaching examples. No photographs, client results, reviews, delivery or production feature claims are invented. The fixed sample QR points at the published Maple demo; no table ID or analytics are added.

Read docs/batch-5/SOURCE-REVIEW.md for sample CSS choices, retained code, external documentation and publication work. Print-media checks do not replace a physical printer/scan check.

Open the original published source ↗

Ready to build?

Something here sparks an idea?

Start with your goal. We can work out the right shape together.

Quote before you commit · Reply within 1 business day · You own the finished custom code and content after final payment

Start a project