> For the complete documentation index, see [llms.txt](https://docs.cremawork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cremawork.com/overview/crema-vite-overview.md).

# Crema Vite Overview

When you get the Crema template from Themeforest, you will get a zip folder from Themeforest. Upon extracting the content of the zip folder, you will get the following two zip files.

{% hint style="info" %}
We can't include everything in the ThemeForest zip file. You can find out the code from GitHub. You can check out the GitHub repo here by filling out this [form](https://git-access.cremawork.com/)\
\
You can find out the following branches for all Repos of the Crema4.x.x as mentioned below

* **source**: This is the default branch of all the Crema Repos, this is based on the Vite + Context APIs

* **source-cra**: This is the default branch of all the Crema Repos, this is based on the CRA+ Context APIs

* **source-cra-starter-kit**: This is a starter kit built with the CTA+Context APIs

* **redux-toolkit**: This is the default branch of all the Crema Repos, this is based on the Redux Toolkit

* **redux-toolkit-starter-kit**: This is a starter kit built with the Redux Toolkit

* **nx:** This is nx monorepo based branch. you will get all apps based on the context APIs and redux-toolkit and their starter-kits as well.
  {% endhint %}

* <mark style="color:blue;">**Crema 4.x**</mark>&#x20;

  **I. MUI:-**  In this folder, you will get the MUI-based template. Crema supports all three state management lib(redux-toolkit, and Context APIs). You can checkout the demo [here](https://cra.cremawork.com/)

  1. **crema-mui-4.x:** This app is based on the CRA & Vite based built with JavaScript
  2. **crema-mui-next-4.x:** This app is based on Next.js built with JavaScript
  3. **crema-mui-ts-4.x:** This app is based on the CRA & Vite based built with TypeScript.
  4. **crema-mui-next-ts-4.x:** This app is based on Next.js built with JavaScript

  \
  **II. Antd:-** In this folder, you will get the Antd-based template. Crema supports all three state management lib(redux-toolkit, and Context APIs). You can checkout the demo [here](https://ant-cra.cremawork.com/)

  1. **crema-antd-4.x:** This app is based on the CRA & Vite based built with JavaScript
  2. **crema-antd-next-4.x:** This app is based on Next.js built with JavaScript
  3. **crema-antd-ts-4.x:** This app is based on the CRA & Vite based built with TypeScript
  4. **crema-antd-next-ts-4.x:** This app is based on the Next.js built with TypeScript<br>

* **servers:-** In this directory, you will find the following backend servers, These servers have auth APIs .

  1. [**Mongoose**](https://docs.cremawork.com/servers/mongoose)
  2. [**Laravel**](https://docs.cremawork.com/servers/laravel)
  3. [**Python**](https://docs.cremawork.com/servers/python)

{% hint style="info" %}
We have the MUI and Antd Design's default components in the CRA & Vite+JS Apps, in other apps you can refer to the components from their page directly &#x20;
{% endhint %}


---

# 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.cremawork.com/overview/crema-vite-overview.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.