Seller Project Requirements

Seller → Seller Project Requirements

To maintain quality and ensure a smooth experience for buyers, all projects submitted by sellers must meet the following requirements:

1. Project Name in English
   The project must have a clear and descriptive name in English. This helps buyers easily understand the purpose and functionality of your project.

2. Minimum Price
   The price of the project must be at least $1. Setting a fair price ensures value for both the seller and the buyer.

3. Demo Link
   Every project should include a working demo link. If the project is still in development or cannot have a public demo, use a placeholder link such as https://sidecrate.com/ or https://example.com/.

4. Documentation File
   A documentation file (Markdown .md or HTML .html) must be included in the project. It should clearly explain:

   • How to set up and run the project

   • Any dependencies or system requirements

   • How to use the project’s main features

5. Database Files
   If the project uses a database, include the necessary files (such as .sql or similar) so that buyers can set it up easily without errors.

6. Code Quality and Organization
   The project code should be clean, organized, and properly structured. Well-written code improves readability and reduces setup issues for buyers.

7. License and Ownership
   Ensure that you have the right to sell the project. Any third-party libraries or assets should comply with their respective licenses.

8. Responsive Design / Cross-Browser Compatibility
   Projects intended for web should work correctly on all major browsers and devices. A responsive design ensures a good user experience on mobile, tablet, and desktop.

9. Error Handling / Stability
   Projects should be stable and free from major bugs. Basic error handling should be implemented to prevent crashes or broken functionality.

10. Security Considerations
    Any user data handling (login forms, database interactions) should follow basic security practices. Avoid including sensitive keys or passwords in the project files.

11. Dependencies and Package Management
    If the project relies on external libraries or frameworks, include clear instructions for installing dependencies (e.g., package.json for Node.js, requirements.txt for Python).

12. Clear File Structure
    Organize your files logically (e.g., separate folders for frontend, backend, assets, database) to make it easier for the buyer to navigate and modify the project.

13. Optional Assets
    Including screenshots, diagrams, or additional resources is highly encouraged. These materials help buyers better understand your project.

14. Optional: Version History / Changelog
    If the project has undergone updates, including a changelog can help buyers understand what has been fixed or improved over time.

Note: Projects on Sidecrate can be either complete or in development ("raw"). For raw projects, a demo may not be available—use a placeholder link as mentioned above.