Submission Requirements

To give users a seamless experience when purchasing Products in the Element Store, you must ensure your Product and Product listing meets the requirements list below.

Products that don’t meet these requirements won’t be approved for the store. We’re always happy to help get things into shape, but final acceptance is entirely at our discretion.

If you are unsure about any details, please post on the forum and we'll help you out.

Product Listing

To list your product on the store you'll need to set the following:

• Product Name

• Description

• Info URL (optional)

• Price (free, paid, subscription)

• Tags (maximum of 5)

• Thumbnail

• Screenshots (2 minimum, 6 maximum)

Product Thumbnail Checklist

A product thumbnail should contain graphics only, ideally an example of the product being sold. See the web store or in-app store for examples. It's worth noting that the thumbnail will also be used as the banner graphic in the product listing window.

• ✅ Thumbnail Size: 3840x2160 pixels

• ✅ Format: PNG or High-quality JPG

• ✅ Show front-end output (not editor UI)

• ⛔ No Elements/App UI

• ⛔ No marketing next

• ⛔ No watermarks or branding overlays

Example Store Thumbnails

Product Screenshots Checklist

Screenshots should show the visual output of the component, but can also contain editor UI from Elements. See the web store or in-app store for examples.

• ✅ Screenshot Size: 3840x2160 pixels

• ✅ Format: PNG or High-quality JPG

• ✅ Up to six screenshots of your product

• ✅ Prioritise front-end output over editor UI

• ✅ Keep styling subtle and modern

• ⛔ Don't include macOS System UI (Dock, Menubar)

Example Store Listing with Thumbnail Header and Product Screenshot

Component Checklist

if you are building and shipping components for Elements, they must meet the following criteria.

• Do no modify the look of the Editor:

  • Do not change the look of other components in the editor.

• Component is WYSIWYG in the Editor:

  • The Editor looks the same (or as close as technically possible) to Preview.

  • Settings and Admin options are not visible in the Editor. Place these in the Inspector, or include a toggle to hide in the Editor.

• Component uses Tailwind CSS:

  • Component styling uses Tailwind classes found in the Theme Studio

  • Takes advantage of the Theme based UI Controls

• Components should not parse @text or @typography data in their hooks.js files