Bundle Publish Requirements
Bundle Requirements#
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:The bundle must contain at least 1 component and at most 15 components.
Bundles do not support global components such as Header or Footer.
Each component type must be unique within the same bundle; duplicates are not allowed.
All components in the bundle must be compatible with the theme structure.
Components must follow Salla’s standard component guidelines.
The bundle must not negatively impact the theme’s performance.
Each component in the bundle must be usable independently.
Components must be responsive and work properly on all screen sizes.
Bundles should support future updates without affecting existing themes.
Technical Review#
The Technical review covers seven areas explained below:1.
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.
2.
Bundles should not negatively impact theme loading speed or network requests.
3.
All bundle components must display correctly on all screen sizes and devices.
4.
Cross-Browser CompatibilityBundle components must function correctly across popular web browsers (Chrome, Firefox, Safari, Edge).
5.
No custom HTML or elements that may compromise security are allowed.
6.
Test all components to ensure they work as intended and are bug-free.
7.
Track future updates for bundle components to ensure compatibility with themes.
In this review, the team will check and validate descriptive information(metadata) associated with the bundle to ensure it is accurate, complete, consistent, and compliant with standards1.
Bundle name should be short, clear, and no more than 3 words.
2.
Support information must be provided, including contact details.
3.
Public pricing: minimum 100 per component
Private pricing: minimum 250 per component
4.
Active Story – Bundle PreviewNo direct preview; Active Story can be viewed.
5.
All components must be compatible with theme structure.
6.
Any updates or changes to the bundle must be documented in a ChangeLog.
Pre-Launch Review#
Last step before your bundle is on the market, the team will have a full review of the following:1.
Ensure pricing strategy for bundles is correct and compliant.
2.
Review any financial agreements or revenue share related to bundle distribution.
3.
Confirm completion of prior reviews and readiness for publication
Modified at 2026-02-05 07:56:15