Release evidence and remaining gates

Review stage

Use this checklist to record evidence for the release candidate. Run native validation in an isolated development account and review the finished preview before publication. Record approval for the actual website or Marketplace publication separately from development, testing and account setup.

Source package

• [x] All JSON files parse and local template/module/asset paths resolve.
• [ ] The theme manifest contains valid file paths and accurate provider data.
• [ ] There are no credentials, competitor assets, copied components or unlicensed dependencies.
• [ ] Every shipped module has meaningful editable fields and a rendered example.
• [ ] Section presets have unique matching screenshots.
• [ ] Template, module and section totals comply with current Marketplace limits.
• [ ] Theme fields control the relevant styles, including h1-h6, body, links, buttons, forms, header and footer.
• [ ] Every image has appropriate alt/loading attributes.
• [x] Each packaged image is below 1 MB.

Native HubSpot checks

Current review evidence: all 42 available native template views passed the final desktop, tablet and phone regression, 126 observations at effective widths 1420, 768 and 391. Visible accessible H1 counts exclude HubSpot's hidden empty confirmation heading. Native 5/7 columns, absolute offsets and phone stacking passed. A genuine internal QA form passed validation, submission, thank-you and normal CRM linkage after preview-domain quarantine release. The test is not a customer enquiry or sale. Email notifications remain unverified.

• [x] All available native template layouts pass the recorded desktop/tablet/phone visual checks.
• [x] A headline edit saves and persists after reload in the native editor.
• [x] A sampled global theme style change saves, reloads and restores.
• [x] A reusable native section can be inserted and a native form can be selected.
• [x] The native phone menu opens and closes with Escape.
• [x] Intended multiline headline restoration persists after the editor-field metadata update.
• [x] A newly configured real native form renders and enforces required-field validation.
• [x] Native V4 form button styling and three-width overflow checks pass.
• [x] An internal test submission displays the thank-you confirmation and links to the expected normal CRM contact after known QA quarantine release.
• [ ] Form email notifications are received and verified.
• [x] Native 5/7 columns, absolute offsets and mobile full-width stacking render correctly.

• [ ] The official compiler/linter reports no errors for the complete package.
• [x] A draft in the correct isolated account opens in the native page editor.
• [ ] Drag/drop, module styles, global header/footer and theme fields edit and persist.
• [ ] Account navigation and language variations work with the mobile menu.
• [x] All available website, landing, native blog listing/post and seven system templates pass native visual rendering checks.
• [ ] Production blog context and search/password/subscription account journeys pass end-to-end checks.
• [ ] Password protection, preference update/unsubscribe, search results/no results, CRM form submission and notifications succeed in the actual account.
• [ ] A child-theme/update workflow preserves customer content.

Browser and performance checks

• [x] Recorded native desktop, tablet and phone widths show no clipped headings or accidental horizontal scrolling.
• [x] Recorded native interaction smoke checks pass for tabs keyboard selection, hotspots open/Escape close, comparison range, accordion, calculator and guide quiz.
• [ ] Comprehensive keyboard and assistive-technology coverage across every module is complete.
• [ ] Reduced motion is respected. Content and main navigation remain accessible without animation.
• [ ] Images and decorative graphics do not cover headings, labels or actions.
• [ ] No browser console errors or insecure mixed content occur on the HTTPS account demo.
• [ ] Current supported browsers and physical mobile behaviour are checked.
• [ ] Real HubSpot-hosted Lighthouse reports meet current Marketplace thresholds.

Publication preparation, after preview approval

• [ ] Own-domain live demo and public documentation URLs exist and resolve.
• [ ] The final theme manifest points to the real public demo/documentation.
• [ ] Provider profile, support contact, purchase price, licence and refund handling are agreed and accurate.
• [ ] Native purchase/install/refund delivery is verified as appropriate to the Marketplace flow.
• [ ] HubSpot Marketplace automated validation succeeds in the intended account.
• [ ] Listing screenshots, feature counts and plan requirements match the delivered package.
• [ ] Explicit approval for the actual submission/publication action is recorded.

The local package integrity check passes with zero errors and warnings. Native testing used published isolated theme files; website pages, public demo/documentation and Marketplace remain unpublished. Marketing-email opt-out is awaiting HubSpot processing.

An unchecked item is not evidence of a failure. It is an item that still needs the corresponding evidence. Do not mark native or public checks complete based only on a static preview or a local integrity report.

Official technical requirements: https://developers.hubspot.com/docs/cms/marketplace/theme-requirements

Official Marketplace policies: https://developers.hubspot.com/docs/cms/marketplace/template-policies