Webflow Marketplace / 01 of 08
A workspace for the work after submission
I worked on the Asset Dashboard to bring asset management, submission progress, validation, and Marketplace insights into a creator workspace.
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: Creator dashboard, asset workflows, and the Webflow Cloud migration
Historical authenticated test-portfolio recording. Asset context, journey, editor entry and insights; no changes saved.
Silent recording · Select captions for visual guidance. Open the MP4 ↗
The problem
Asset Dashboard
Submitting an asset is one step in a continuing relationship with the Marketplace. Creators also need to see what happened to their submission, inspect feedback, update information, and understand the context in which their work is being sold.
The contribution
The work behind the interface.
The Dashboard brings those tasks together around the asset. A creator can browse a portfolio, open an individual asset, follow its submission journey, and enter the editor. Marketplace insights provide a separate view of category performance and the freshness of the underlying information.
My work also covered the Webflow Cloud port and shared domain layer. The migration scope includes authentication, protected routes, asset detail and editing, image uploads, profile management, submission tracking, and analytics. Keeping that scope explicit matters: a migrated screen is useful only if the surrounding creator workflow remains intact.
The key decision
What needed to stay clear.
Organize the workspace around assets and their progress, with source freshness visible where creators interpret Marketplace data.
The documented result
What the evidence shows.
An existing authenticated recording demonstrates a test portfolio, a submission timeline, the editor opening, and Marketplace insights. It establishes those visible interactions. No fields were changed or saved during the recording.
The recording demonstrates the Asset Dashboard, not every route in the Cloud port or the later native Creator Hub migration. Adoption and time savings have not been established for this study.
Portfolio evidence captured October 2026. Historical implementation and recordings do not establish the current state of every production system.