Document storefront forms and their task workflows

[mattsodomsky]

Introduces Storefront forms as a way for customers to start Mechanic workflows: build questions visually, place the form in a theme, and connect ordinary Mechanic webhooks to tasks. Includes quote-request and warranty walkthroughs, plus wholesale and service examples using email, Google Sheets/Drive, and Shopify metaobject tasks.

The guide covers templates and layouts, webhook connections, publishing and the native form picker, placement lookup and its standard theme-read permission, previews versus real submissions, the 3 MB total upload limit, file storage and attachments, duplication, portable JSON, and stopping a form. Task-author payload details remain in the webhook reference. Cross-links connect the guide with the introduction, Settings, Permissions, Events, the webhook tutorial, and the theme FAQ. Staff-facing Run task forms are distinguished from storefront forms.

Current setup and screenshots

Six fresh screenshots show the current staging UI: starter templates, the visual builder, Submission settings with a copyable Form ID, Shopify's native form picker without the old code input, the Theme tab with a saved Home page placement, and the saved-changes publication reminder. They use native app-content crops, matching the existing Settings, task editor, and webhook documentation. Account navigation and developer overlays are excluded; alt text and captions describe each image.

The final review corrects form-name privacy (published names are publicly readable), documents the storefrontform task option, and puts publishing before task selection in the walkthroughs. It also makes preview behavior and email/Drive/metaobject file handling explicit. Publishing a form does not install tasks automatically.

Validation

• Checked the guide against the implementation, task definitions, and current staging screens.
• Visually inspected all six refreshed screenshots and compared their framing with existing documentation.
• Checked all 28 relative links and anchors across the three pages edited in the final pass; all six PNG paths and image formats validate.
• Whitespace checks pass. Merchant guidance lives in mechanic-docs; https://github.com/lightward/mechanic-ui/pull/2098 removes the duplicate UI-repository guide.
• No production configuration changed. The publication reminder was smoke-tested on staging using a temporary text edit, then the original text was restored and republished. No submissions were sent, webhook connections changed, or themes saved.

Release gates — keep draft

• Complete the remaining launch acceptance checks and release the matching API, UI, and extension features to the intended merchants.
• Publish the three linked library tasks in Process form submissions with email, Sheets, and metaobjects mechanic-tasks#578 before publishing this guide.
• Confirm the released screens still match the guide at launch.

This is a reviewed documentation draft, not a production-release sign-off.