Development Docs, Guides & Best Practices

Guides & Best Practices

• WordPress Development Best Practices
  • WordPress Coding Standards (PHP Code sniffer rules)
  • Inline Documentation Standards
  • Browser Support
• Plugin Handbook
  • Internationalization
  • Security
  • Privacy
• Plugin Directory Guidelines
• Core APIs
  • WordPress
  • WooCommerce
  • REST API
  • Developing using WooCommerce CRUD Objects
• WooCommerce Developer WIKI
• WooCommerce Developer Portal
  • Extension Developer Guide
  • Testing Extensions And Maintaining Code Quality
• Components
  • WordPress
  • WooCommerce
• WooCommerce Admin
  • Docs
  • Activity Panel / Inbox Notifications
  • Remote Inbox Notifications
  • Wiki
• WooCommerce Blocks
  • Handbook / Docs
• Action Scheduler
  • Documentation
• Platform Authentication
  • Jetpack Connection Package
• Usage Tracking
  • External facing information
  • WooCommerce Tracker
  • WooCommerce Tracks
  • woocommerce/tracks package
• GMC Request Review Feature
  • Technical overview

Use The Core APIs

Using the core APIs when developing for WordPress and WooCommerce is strongly encouraged because:

• Core APIs make building things easier by providing hooks, actions, filters, helper functions.
• WordPress does the “heavy lifting” for you (database calls, input validation, security, form building) so you don’t have to.
• Using core APIs helps ensure your code will be both backward-compatible and future-proof.
• The APIs allow seamless integration into wp-admin for plugin/theme options pages, inline help documentation, etc.

Minimum Requirements / Compatibility

Aim for L-2 unless there are specific requirements needed.

As long as it’s clearly marked, and ideally handled properly (we don’t crash sites on older versions) setting the minimum level of support to newer versions is acceptable.