Webflow Marketplace / 05 of 08
Make intake confirm what happened
I developed Marketplace submission workflows that connect creator eligibility, asset information, validation evidence, uploads, and a review-record handoff.
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: Template and app intake, inline guidance, evidence integration, and reliable receipts
Live unsent template-form inspection. No identity check, upload, validation job, or submission.
Silent recording · Select captions for visual guidance. Open the MP4 ↗
Actual App form entry gate. No new Webflow connection or authenticated intake is shown.
Silent recording · Select captions for visual guidance. Open the MP4 ↗
The problem
Submission forms
A form can accept a request without creating a complete record that a review team can use. If the success message skips that distinction, creators can believe their work is in review while the underlying handoff is still processing or incomplete.
The contribution
The work behind the interface.
The template flow checks creator eligibility and the published site, integrates Validator results, handles constrained uploads, and can use analysis to suggest listing information. It is an independent Webflow Cloud application embedded in the public submission page.
The receipt logic looks for a matching asset, version, creator, and review status. Until the confirmation is available, the state remains processing. App intake adds its own listing guidance and artifact requirements. Historical app-form verification describes cross-field checks and URL guidance, with the Preflight receipt optional in production at that checkpoint.
The key decision
What needed to stay clear.
Give each stage a truthful state and a specific recovery action. Template and app validation contracts remain distinct; the template Validator requirement does not establish an equivalent mandatory App Preflight gate.
The documented result
What the evidence shows.
The template source implements validation integration and review-record confirmation. Historical CTX evidence supports app-form improvements in the separate webflow/wf-app-form-cloud repository. The result is a more explicit intake contract; its effect on submission quality has not been measured for this study.
The new template-form recording shows the live validation, listing, and incomplete readiness sections without checking a real identity, uploading, or submitting. The App form separately requires a Webflow connection before entry. No completed intake or review-record creation is claimed.
Portfolio evidence captured October 2026. Historical implementation and recordings do not establish the current state of every production system.