Webflow Marketplace / 02 of 08
Make template requirements actionable in Designer
I worked on the Webflow Way Validator to help creators inspect template quality while they are working, then carry the validation result into submission.
Selected professional work by Micah Johnson for Webflow, presented as individual portfolio work. Webflow did not commission this work through CREATE SOMETHING. Individual contributions are described within a wider team and platform context.
Contribution focus: Designer extension, published-site checks, persisted results, and intake integration
Live Designer inspection on an owned test site. Setup and scope only; no validation run or site changes.
Silent recording · Select captions for visual guidance. Open the MP4 ↗
The problem
Validator App
A written guideline tells a creator what good work should satisfy. It does not show which element or page needs attention in the template they are building. Leaving those checks until review pushes avoidable correction work into a later stage.
The contribution
The work behind the interface.
The Validator combines Designer checks with checks on the published site. Its interface groups findings across Designer structure, assets and images, and content and accessibility. Partial runs support iteration; the submission path asks for the full set of checks and pages.
The result also has to travel. The worker can persist a sanitized artifact and expose the latest submission status. The template form checks that result alongside the published setup, then gives a specific recovery path when the expected evidence is missing. This connects a creator’s validation run to the intake system without treating a pasted claim as proof.
The key decision
What needed to stay clear.
Use validation as concrete preparation evidence. The latest persisted result can satisfy a submission contract, while visual quality and final Marketplace approval remain separate judgments.
The documented result
What the evidence shows.
Current extension and worker source implement categorized checks, computed pass results, and a latest-result endpoint. The template intake code integrates that evidence. This study establishes the implementation; it does not claim a measured reduction in rejection or review time.
The new authenticated Designer capture shows setup requirements and check-scope controls. The test site lacks the published Validator script. No script was installed, site published, token rotated, validation run completed, or result persisted.
Portfolio evidence captured October 2026. Historical implementation and recordings do not establish the current state of every production system.