What does a great template look like?

We review every template before it is live on the site. New templates will always go through a full review before they're allowed on MUI Store whereas updated templates will go through an abbreviated review. We've broken down each step of the process below in order to make it as clear and predictable as possible. If you need help with the actual upload you can see a step-by-step in the following article. 

Overarching requirements

MUI Store focuses on curating templates that hit the following points: 

1. Great design execution. A clean, well-considered design execution, is the main selling factor
2. High-quality code. One that mimics the open-source library style
3. Targeted purpose. Meaning templates that aim to solve a specific category of problem.
4. Support. The contributor has shown a history of excellent customer support.
5. Complementarity. Are different than other existing templates on our site.

With all the above in mind, your templates will be in good company! Our goal is to bring together a diverse set of templates that offer clear differences and advantages rather than a massive sea of mediocrity. We want to offer our customers a hand-picked collection of the best templates possible and a focused revenue stream for our contributors. 

1. Great design execution

This is about end-user experience. The template must be clean and have a well-considered design. The UX/UI execution must be strong. This is the single most important reason why customers purchase templates.

2. High-quality code

This is about developer experience. We are also looking at the overall quality of your code to ensure it's well-documented and well-laid out. While it's hard to come up with a list of everything we look at from a code perspective we'll continue to add examples here as we see common issues crop up!

• Must include documentation for new components, extended MUI components, and to install or get started with the template. If there’s compiling involved, that also must be documented.
• Any dependencies should be reasonably up to date. Essentially just be sure you're not using a wildly outdated dependency that would cause buyers to second guess. As a good rule of thumb: all the dependency less than 3 months old is considered great.
• The product needs to attach a single zip file. Attaching any other file type will result in a rejection. We want to keep the deliverables accessible to everyone and zips work the best.