Cookies

This website uses cookies to ensure you get the best experience on our website.

Building Templates Guide

This guide explains how templates can be built, managed, and sold using a Developer Account. It also outlines the workflow for template approval and revenue sharing when templates are used by other users.


1. Purpose of Templates

Templates define the structure, layout, and design of your storefront pages. They include:

  • Sections
  • Blocks
  • Layouts
  • Pre-configured content

With templates, developers can create reusable designs for pages such as home, product, collection, or custom pages.


2. Developer Account & Template Creation

Only a Developer Account can create templates. This ensures:

  • Safe development environment separate from live stores
  • Testing of templates without affecting existing storefronts
  • Ability to assign templates for review and approval

Steps to Create a Template:

  1. Log in to your Developer Account.
  2. Go to the Templates section.
  3. Click Create New Template.
  4. Enter the Template Name and select Template Type.
  5. Assign Sections and Blocks to define layout and functionality.
  6. Save the template for testing or submission.

3. Template Submission for Selling

Templates created by developers can be submitted for selling after approval:

  1. Developer submits template for review.
  2. Admin or platform team reviews the template for quality and compatibility.
  3. Once approved, the template is available for other users to purchase or use.

4. Revenue Sharing

When an approved template is used by other users:

  • A percentage of revenue is transferred to the developer account.
  • The platform tracks the number of users who purchase or use the template.
  • Revenue is calculated based on predefined commission rules and transferred periodically to the developer account.

Developers can earn by creating high-quality templates that attract multiple users.


5. Managing Templates

  • Templates can be edited in the Developer Account before approval.
  • Versioning ensures changes are tracked and previous versions can be restored.
  • Approved templates are read-only for developers to maintain consistency for buyers.

6. Best Practices

  • Create modular and reusable sections within templates for easier customization.
  • Test templates across multiple layouts and devices before submission.
  • Use descriptive names for templates to help users identify their purpose.
  • Document your template’s features and requirements clearly for end users.

Building templates through a Developer Account allows developers to contribute to the platform, offer premium designs, and earn revenue through template usage while maintaining quality and consistency.