To help standardize component bundle development and streamline reviews, please follow the requirements below when submitting your component for publishing in Salla Themes Marketplace.UI / UX Review #
To fulfill the UI/UX review follow the below requirements list:| # | Category | Requirement |
|---|
| 1 | Structure | The bundle must contain at least 1 component and at most 15 components. |
| 2 | Restrictions | Bundles do not support global components such as Header or Footer. |
| 3 | Validation | Each component type must be unique within the same bundle; duplicates are not allowed. |
| 4 | Compatibility | All components in the bundle must be compatible with the theme structure. |
| 5 | Standards | Components must follow Salla’s standard component guidelines. |
| 6 | Performance | The bundle must not negatively impact the theme’s performance. |
| 7 | Usability | Each component in the bundle must be usable independently. |
| 8 | Responsiveness | Components must be responsive and work properly on all screen sizes. |
| 9 | Maintainability | Bundles should support future updates without affecting existing themes. |
UX/UI Review for Landing Page Template #
| Category | Requirement |
|---|
| Conversion Goal | The landing page must have one clear conversion goal, such as purchase, signup, or lead generation. It should not promote multiple primary actions. |
| Hero Section | The first screen must clearly communicate the value proposition, a supporting description, and a primary Call-to-Action (CTA). |
| Conversion Flow | The page should follow a logical conversion flow that guides users from introduction to action. |
| Recommended Sections | 1. Hero
2. Problem / Pain Point
3. Solution / Features
4. Benefits
5. Social Proof (Testimonials, Reviews, or Customer Logos)
6. FAQ (optional) |
| Primary CTA | Every landing page must contain at least one prominent primary CTA. |
| CTA Consistency | The primary CTA should remain visually consistent throughout the page and may be repeated in strategic sections. |
| Storytelling | Components must be arranged in a logical sequence that progressively builds trust and encourages conversion. |
| Distractions | Minimize distractions by avoiding unrelated sections or competing primary actions. |
| Section Relevance | Each section should contribute directly to the landing page's conversion objective. |
| Visual Hierarchy | The visual hierarchy should prioritize the headline, supporting content, and CTA. |
Technical Review #
The Technical review covers seven areas explained below:
Theme Design Quality
Bundles should follow Salla coding standards; code must be well-structured and readable.
Bundle size should be optimized and not affect performance.
Use localization instead of static strings.
Ensure all components are compatible with the current bundle version.
Performance
Bundles should not negatively impact theme loading speed or network requests.
Responsiveness
All bundle components must display correctly on all screen sizes and devices.
Cross-Browser Compatibility
Bundle components must function correctly across popular web browsers (Chrome, Firefox, Safari, Edge).
Security
No custom HTML or elements that may compromise security are allowed.
Functionality Testing
Test all components to ensure they work as intended and are bug-free.
Bundle Updates
Track future updates for bundle components to ensure compatibility with themes.Salla advises to only share relevant information and abstain from sharing inappropriate information.
Follow these name style guidelines:
| No. | Requirement |
|---|
| 1.1 | Bundle and style names should stand apart from Salla Products, Events, or Branded content. |
| 1.2 | They should also differ from Partner names. |
| 1.3 | Avoid overlap with website, e-commerce, or SEO-related terms; for instance, steer clear of names like Performance, Mobile, or Sales for your Bundle. |
| 1.4 | Ensure unique names not resembling industry or collection names from the Theme Store, such as Fashion, Electronics, or Jewelry. |
| 1.5 | Keep names clear and hint at the purpose of the Bundle. |
| 1.6 | Communicate what merchants can expect from the Bundle , encompassing core concepts and the intended audience. |
| 1.7 | Opt for noun-based or adjective-based names. |
| 1.8 | Choose easily pronounceable names to aid in recall and searching for merchants. |
| 1.9 | Consider different dialects and regional meanings; consult an idiom dictionary if needed. |
| 1.10 | Avoid using the same name on other platforms. |
| 1.11 | Name should be short, and not more than 3 words without emojis, spaces, or special characters in the Bundle or style name. |
