> For the complete documentation index, see [llms.txt](https://docs.ecwid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecwid.com/site-themes/develop-site-themes/getting-started.md). # Getting started Thank you for your decision to contribute to Ecwid Theme market! To help you with the task, we prepared a series of articles covering all of the major steps in building your first public theme. ### Define your design system The first step in your journey is not the development itself! It is to find your verticals, design rules, palettes, and overall vision for the theme you want to create. Our experience shows that most successful themes are developed when a design system is ready before any code line is written. While it is not a "coding guide", we highly recommend checking out the [Design Site Themes](/site-themes/design-site-themes/introduction-to-designing-themes.md) guides. These are tailored by our own design team to help you with finding and refining your design system for the theme. ### Develop a working theme Now that you have an established design system, it is time to start coding. Creating themes for Ecwid requires the use of the **Crane framework**, which includes tools and methods for building your themes locally, importing additional libs and features, fast previews, and pushing themes to Ecwid. All of the following articles in this section will guide you from the theory and the initial setup to a working theme: * [Crane overview](/site-themes/develop-site-themes/getting-started/crane-overview.md) * [Install Crane to your system](/site-themes/develop-site-themes/getting-started/install-crane-to-your-system.md) * [Start with Crane app](/site-themes/develop-site-themes/getting-started/start-with-crane-app.md) * [Make your first section](/site-themes/develop-site-themes/getting-started/make-your-first-section.md) * [Make your first template](/site-themes/develop-site-themes/getting-started/make-your-first-template.md) {% hint style="success" %} **LLM-ready docs** This documentation is fully LLM-ready! Go to and use the #Getting started tag as the entry point for LLM use of Crane docs. {% endhint %} The goal here is to get a working theme and a basic understanding of its functions. Once you set it up, jump into the docs to unlock the full potential of Crane: * [Templates](/site-themes/develop-site-themes/templates.md) * [Sections](/site-themes/develop-site-themes/sections.md) {% hint style="info" icon="comments-question-check" %} **Got any questions along the way?** [Contact Ecwid API support team](/contact-ecwid-api-support-team.md) {% endhint %} ### Launch theme to Theme Market Congratulations on getting a working theme worthy of its price! About the price... It's time to launch your theme in Market. Jump into the [Launch Site themes](/site-themes/launch-site-themes/themes-design-requirements.md) section to: * Ensure that the theme meets all the design, technical, and accessibility requirements * Learn about your pricing options * Submit theme to Market and start getting revenue --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ecwid.com/site-themes/develop-site-themes/getting-started.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.