SELECTED WORK
Websites, workflows, and the work between.
A closer look at Umbric's own website and publishing process, plus a fictional product-content demo.
Justin RecklingIndependent developer · UmbricTwo first-party examples.
One fictional concept.
One website with distinct paths for services and experience. Responsive layouts, purposeful navigation, and direct ways to get in touch.
Pages & approved assets
Export & contact links
Build-specific headers
One complete release
The small scripts behind this website: prepare the pages, preserve contact links, and keep every build paired with its headers.
A hypothetical catalog workflow, made tangible. Follow supplied facts through product copy, specifications, image notes, and review.
A PRACTICAL STARTING POINT
A useful first conversation starts with the material you have and the change you need.
Share the page links, approved copy and assets, and a short list of changes. We can scope a coherent update batch.
Show a repeatable task, a sample input, and the output you need. Include API documentation if another system is involved.
Bring supplied product facts, approved images, and a target page or format. We can define a preparation and review checklist.
START WITH ONE USEFUL CHANGE
Send the page, the task, or a sample of the files. We can agree on a clear scope and a reviewable first delivery.
Email Justin justin@umbric.com