> For the complete documentation index, see [llms.txt](https://docs.mydukaan.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mydukaan.io/testing-and-deploying-your-theme.md).

# Testing and Deploying Your Theme

For every change you make in the code editor, there are 2 steps involved.

1. Previewing how your change would look like & testing it. 
2. Deploying the changes to your site 

## 👀 Previewing your changes

1. Once you make your changes in the code editor click on the **"Save & preview"** button on the top right corner of the code editor

<figure><img src="/files/X2dNQbsfj7pvrU9PHC9k" alt=""><figcaption></figcaption></figure>

This deploys your changes to an **intermediate url which is not your actual site**, i.e. your customers won't be able to see the changes, so its a perfect place to experiment

The intermediate url ends with a domain **".sh"** instead of the original Dukaan domain **".io"**\
So, if your store url was **"general-store",** \
It's preview url would be - **"mydukaan.sh/general-store"** \
whereas the original store link would be - **"mydukaan.io/general-store"**

On successful deployment you'd see a message something like this

<figure><img src="/files/sW7SRSyo3ZWPYIXmSgeT" alt=""><figcaption></figcaption></figure>

Your changes would be visible in your preview url, and you can do all the testing you want here before you make the changes live for your customers.&#x20;

Mobile screen preview is directly visible from the code editor itself, its on the right side of the code editor

<figure><img src="/files/4fPZDV3ox5IYFJzLEe1b" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Note - You can deploy to your preview url as many times as you want, so feel free to experiment your ideas.
{% endhint %}

## 🚀 Deploying your changes

Now when you're sure that your customers must see the changes you've made you can deploy it with a single click by simply clicking on the **"Publish"** button

<div align="center"><figure><img src="/files/BlLcqpgQEmnfFM3THA2T" alt=""><figcaption></figcaption></figure></div>

This makes all your changes live for your customers instantly on your original store url.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mydukaan.io/testing-and-deploying-your-theme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.