# Review requirements (https://docs.salla.dev/twilight/react/local-development/review-requirements)



Read this before you send a theme for publication. Salla's team reviews every theme against these rules, and rejects a theme that misses one. You then fix it and send a new request.

The review runs in four stages:

1. **Main requirements**: the theme has a clear purpose and is truly your own.
2. **Listing**: the name, support details, price, screenshots, description and preview stores.
3. **Technical and design**: code quality, speed, and what each page must show. The design rules are on [Design requirements](https://docs.salla.dev/twilight/react/local-development/design-requirements).
4. **Pre-launch**: the team checks the pricing and revenue terms, then the theme goes live.

Salla may change these rules, and tells partners before it does.

## 1. Main requirements [#1-main-requirements]

**A clear industry.** Pick the industries your theme suits best with little setup, such as Fashion, Food and drink, or Electronics. The marketplace groups and recommends themes by these choices.

**Rich blocks.** Each home block gives the merchant enough fields to change its content and its look.

**Your own work.** A theme built from the starter theme, [Raed](https://github.com/SallaApp/theme-raed-react), must be clearly different from it:

* The code differs in a meaningful way from Raed and from other themes.
* The design has its own art direction, and one look across all pages: home, product, category, blog, search and cart.
* It offers settings or features other themes do not.
* A merchant cannot buy your theme and another one, then set them up to look almost the same.

**Size.** A public theme may be at most 1 MB, a private one 2 MB.

## 2. Listing [#2-listing]

**Name**

* One word, under 14 characters, with no spaces, emojis or special characters. "Elegance" passes; "The Majestic" and "Day\&Night" do not.
* Not a Salla product, event or brand, not a partner's name, and not an industry or marketing word such as Fashion, Sales or Mobile.
* Easy to say, it hints at what the theme is for, and it does not mean something unwanted in other dialects. Do not reuse it on other platforms.

**Support.** Merchants contact you, not Salla. Fill in all of: a support email, a website, a phone number, a live-chat link (such as WhatsApp or Telegram) and a documentation link that explains how the theme works. Answer within two business days.

**Price.** A one-time price, at least 250 SAR for a public theme and 1,000 SAR for a private one. Count the design, the catalog size the theme suits, and the support you will give.

**Screenshots**

* At least four, as images or YouTube videos of at most two minutes.
* Each has its own title and description, in Arabic and English. The title names a feature, such as "Smooth animations".
* Together they show every feature, in desktop and mobile views, with no text or logos on the images.

**Description.** A short summary of the main features, a link to a setup video or tutorial, and no prices or discounts.

**Change log.** Each publication request carries a note of what changed, in Arabic and English. Keep it to what merchants need to know.

**Preview stores**

* At least one and at most four, with one set as the default. Do not use one store for several themes, and use one per theme category.
* Real text on every page: no "Lorem ipsum" or "test". No text or buttons inside images, except on products, infographics and badges.
* Your own images, and permission for any brand you show.
* Show the theme at its best with Salla features: offers with countdowns, loyalty, a blog, a product on sale, a sold-out product and one with several options.
* The store looks like a real store: nothing about the theme itself, no store icon, and thumbnails without text or logos.

**Active stores** (optional, for a theme already live in several stores): screenshots of those stores, at most 800×450 pixels and 200 KB each, without added text or logos.

## 3. Technical review [#3-technical-review]

* **Translations.** Every text a customer reads comes from your locale files, not from strings in the code. See [Languages and RTL](https://docs.salla.dev/twilight/react/guide/languages-and-rtl).
* **Requests.** No request per product or per item in a list. Load data in route loaders and lists, as [Loading data](https://docs.salla.dev/twilight/react/guide/loading-data) shows.
* **Speed and access.** On the default preview store, the home, category and product pages average a Lighthouse score of at least **60** for performance and **90** for accessibility, on desktop and mobile.
* **Every screen and browser.** The theme works on phones, tablets and desktops, and in Chrome, Firefox, Safari and Edge.
* **Safety.** No setting or block lets a merchant add their own HTML, and the theme does not render setting text as HTML (`dangerouslySetInnerHTML`).
* **Everything works.** Menus, forms, buttons, sliders and every block behave as intended.
* **Up to date.** Follow the engine's releases in the [Changelog](https://docs.salla.dev/twilight/react/changelog) and the changes to Raed, and bring their fixes and features into your theme.

## Gotchas [#gotchas]

* The speed and access scores are measured on your default preview store, so fill it with real content before you send the theme.
* A rejected request lists what to fix. Fix all of it before you send the theme again.

## See also [#see-also]

* [Design requirements](https://docs.salla.dev/twilight/react/local-development/design-requirements)
* [Partners Portal](https://docs.salla.dev/twilight/react/local-development/partners-portal)
* [Publish](https://docs.salla.dev/twilight/react/local-development/publish)
