WPBay Submission Guidelines

  • Home
  • WPBay Submission Guidelines

Welcome to WPBay! We’re excited to have you onboard as a seller. To maintain a high-quality marketplace that WordPress users can trust, all submissions (themes and plugins) must meet the following guidelines. Please read these guidelines carefully before submitting your product for review.

1. General Requirements

1.1 Product Types Allowed

  • WordPress Themes: Must be compatible with the latest major version of WordPress.
  • WordPress Plugins: Must add or enhance functionality within a WordPress site.
  • Supporting Materials: Optional documentation files, demo content, PSD files for theme design, and license information.

1.2 Licensing and Ownership

  • GPL Compatibility: Products that are GPL or GPL-compatible are encouraged, though proprietary licenses are allowed unless stated otherwise by WPBay.
  • No Copyright Infringement: You must own or have the right to use all code, images, and other assets included in your product.
  • Third-Party Libraries: Ensure you have the rights to redistribute any included third-party libraries or frameworks. Provide proper attribution or licensing documentation if required.

1.3 Language and Localization

  • English Language: All product descriptions, documentation, and support communication must be in English (at minimum).
  • Text-Domain: For themes and plugins, include a text-domain to support translations (using WordPress localization methods).

1.4 Code Quality

  • WordPress Coding Standards: Adhere to WordPress Coding Standards for clean, maintainable, and secure code.
  • Security Best Practices: Validate and sanitize all user inputs, escape outputs, and avoid exposing sensitive information.
  • No Malicious Code: Submissions containing backdoors, spyware, adware, or hidden affiliate links will be rejected and may lead to account termination.

2. Technical Guidelines

2.1 Compatibility

  • WordPress Version: The product must be tested with the latest stable release of WordPress.
  • PHP Version: Ensure compatibility with a range of PHP versions, typically PHP 7.2 and above (or as defined by WordPress guidelines).
  • Other Dependencies: Clearly outline any required plugins (for instance, WooCommerce) or server extensions. Provide graceful handling if dependencies are missing.

2.2 Performance

  • Efficient Code: Avoid excessive resource usage (CPU, memory) and reduce the number of HTTP requests.
  • Minimal Bloat: Only include the files and libraries necessary for your product’s core functionality.
  • Optimized Assets: Compress images, minify CSS/JS files, and load assets conditionally to improve page speed.

2.3 Security

  • Nonces for Forms: Use nonces and other WordPress security functions to protect forms from CSRF (Cross-Site Request Forgery).
  • Input Validation & Output Escaping: Use esc_html(), esc_attr(), and similar functions to sanitize and escape data.
  • No Hardcoded Credentials: Do not store API keys, passwords, or other credentials in your source files in plain text.
  • Safe File Operations: Validate file uploads and never allow arbitrary file execution or directory traversal.

3. Design & UI Requirements (Themes)

3.1 Responsiveness

  • Mobile-Friendly: Themes must be responsive or at least display properly on various devices and screen sizes.
  • Fallbacks: Handle older browsers gracefully (e.g., IE11 or as specified in your product’s compatibility list).

3.2 Code Organization

  • Template Files: Follow standard WordPress template hierarchy (e.g., index.php, page.php, single.php, etc.).
  • Theme Customizer: If you allow theme customization, use the WordPress Theme Customizer (/wp-admin/customize.php).
  • Child Theme Support: Ensure your theme can be used as a parent theme. Provide documentation on how to create and use child themes if relevant.

3.3 Visual Quality

  • Consistent Styling: Typography, spacing, and color usage should be well-structured and consistent throughout the theme.
  • No Offensive Content: Avoid using images or content that is controversial, offensive, or violates copyright.

4. Functionality Requirements (Plugins)

4.1 Core WordPress Integration

  • Plugin Headers: Make sure your plugin has proper headers in the main PHP file (e.g., Plugin Name, Description, Version, Author).
  • Settings Placement: Place settings pages under the appropriate WordPress menu sections.
  • Hooks & Filters: Use WordPress action and filter hooks responsibly to avoid conflicts.

4.2 Reliability

  • Stable Releases: Submit stable, production-ready versions. Beta or alpha versions must be clearly labeled as such and may be subject to additional scrutiny.
  • Error Handling: Gracefully handle PHP warnings or errors. Avoid triggering fatal errors on plugin activation or deactivation.

4.3 Extensibility

  • Hooks: Provide your own actions and filters where it makes sense, so others can extend your plugin without modifying core files.
  • Modular Architecture: Keep features modular to maintain code clarity and user control.

5. Documentation & Support

5.1 Documentation

  • Setup Instructions: Include clear steps for installation, configuration, and usage.
  • Screenshots / Screencasts: Provide visuals to guide users through basic tasks.
  • Feature Explanations: Describe how each feature works and any relevant technical details (e.g., shortcodes, template tags).

5.2 Support Guidelines

  • Availability: Indicate how and when you will provide support (e.g., support forum, email, help desk).
  • Scope of Support: Outline what is covered (e.g., bug fixes, usage questions) and what is not (e.g., third-party conflicts, custom modifications).
  • Response Time: Acknowledge user inquiries within a reasonable timeframe (e.g., 1–2 business days).

6. Presentation & Listing Standards

6.1 Product Title & Description

  • Clear and Descriptive: Your product title should clearly state its purpose or unique selling point.
  • Grammar & Spelling: Ensure your listing has proper spelling and grammar.
  • Keywords: Use relevant keywords without keyword-stuffing; it helps SEO but keep it natural.

6.2 Screenshots & Demos

  • Quality Images: Screenshots should be clear and high-resolution. Avoid watermarks that obscure details.
  • Live Demo (for Themes): If applicable, link to a live demo showcasing theme features and customizations.

6.3 Versioning & Changelog

  • Semantic Versioning: Use a versioning system (e.g., 1.0.0, 1.1.0, etc.).
  • Changelog: Maintain a clear changelog for each update, detailing bug fixes, enhancements, and new features.

7. Submission and Review Process

7.1 Preparing Your Submission

  1. Check Compatibility: Test thoroughly on the latest WordPress version.
  2. Include Documentation: Attach or link to your product’s user guide.
  3. Compress Files: Provide a .zip or .rar file that includes all necessary product files.

7.2 Submission Steps

  1. Upload: Use the WPBay Seller Dashboard to upload your product archive.
  2. Listing Details: Provide product name, description, price, and any other relevant metadata.
  3. Submit for Review: Click the “Submit” button. You’ll receive an email confirmation that your item is in the review queue.

7.3 Review Timeline & Outcomes

  • Review Time: Typically 2–5 business days. Complex items may take longer.
  • Approval: If approved, your listing goes live immediately.
  • Rejection: If rejected, you’ll receive an email with reasons and instructions on how to fix issues.
  • Resubmission: Once you address the reviewer’s feedback, you can resubmit for another review.

8. Updates & Maintenance

8.1 Ongoing Product Updates

  • Regular Maintenance: Keep your product up to date with the latest WordPress releases.
  • Bug Fixes: Patch bugs promptly to maintain product reliability and user trust.

8.2 New Features

  • Backward Compatibility: Aim to keep existing features and code functional when adding new capabilities.
  • Detailed Changelog: Update your changelog with each release so users know what changed.

9. Intellectual Property & Legal Compliance

9.1 Trademark & Copyright

  • Trademark Usage: Avoid using trademarks (like “WordPress”) in your product name in a misleading way.
  • Copyright Violation: Do not include copyrighted materials (e.g., images, videos, or code) without permission.

9.2 Privacy & Data Collection

  • Data Collection: Clearly disclose any personal data collection or usage.
  • GDPR / Privacy Laws: Comply with relevant data protection regulations in your region and for your users.

10. Prohibited Content

Products that include the following content will be removed immediately and may lead to account suspension:

  1. Malicious Code: Spyware, viruses, or hidden affiliate links.
  2. Illegal Activities: Promotion of hacking, spamming, or other unlawful behavior.
  3. Hate Speech / Discrimination: Offensive material targeting specific groups or individuals.
  4. Adult / Mature Content: Explicit imagery or services that are not suitable for the general WordPress user base.

11. Violations and Enforcement

Failure to comply with these guidelines can result in:

  • Rejection of Submission
  • Suspension or Termination of Seller Account
  • Removal of Product from WPBay

WPBay reserves the right to update these guidelines at any time. We will inform you of significant changes through email or your seller dashboard.

12. Additional Resources

Thank You for Partnering with WPBay!

We appreciate your commitment to creating high-quality WordPress products. Following these guidelines helps ensure a positive experience for both sellers and buyers. If you have any questions or need clarification, please contact WPBay support at: [email protected].