A site is only useful if it helps a business operate better. I focus on the parts people actually need: clear pages, simple navigation, working forms, and the systems behind them.
The case study below shows the kind of work I build and maintain, with a focus on practical field-based businesses.
E-commerce nursery site with a structured product catalog, shipping logic, and ongoing operational updates.
Registry-driven Japanese maple guidance tool with in-stock browsing, deterministic fit checks, and a Shopify-ready frontend path.
Clean layout, direct copy, and the practical backend pieces needed to keep the site functioning after launch.
Simple pages that stay organized and connected to the business. One example is the custom Shopify shipping app I built for Essence of the Tree.
For Essence of the Tree, I built a custom Shopify shipping app that estimates checkout rates from cart contents and destination instead of relying on a flat rule.
The app reads tree size counts, expands bundle products into their underlying size mix, applies zone rules, and returns carrier-service rates that Shopify can use at checkout.
The shipping app is more than a rates endpoint. It also includes the tooling around it: carrier-service registration, order metafield writeback, and retraining exports.
That is the kind of digital systems work I do: build the thing behind the storefront, then keep it tied to real operations.
The Planting Wizard helps customers check whether a Japanese maple fits their USDA zone, available space, exposure, and site conditions.
The current version is driven by a normalized operational catalog, separated reference cultivars, inventory availability, and conservative rule data.
This project turns EoT's cultivar registry, inventory data, partial rules, and reference records into a client-side decision tool that can be embedded without a server dependency.
The goal is simple: turn nursery data into a practical decision path while keeping data coverage and horticultural limits visible.
Keep inventory accurate with quantity-only updates for existing variants and a separate exception path for missing items.
Keep large catalogs readable and consistent with live title, meta description, and image alt-text updates.
Keep content pages clear to both people and machines with guarded schema deployment and reviewable markup changes.
This article is the source material for both infographic versions below. The point is to show how one educational article can be translated into a visual asset with different levels of structure.
The live article is here:
Open the article →
I’m keeping both versions visible because they show the editorial process clearly: one article, two visual treatments, same source, different structure.