e28b0aa9ea
* Filter product collection variations by 'block' scope This commit updates the product collection feature to only show variations with the 'block' scope in the collection chooser. To achieve this: 1. Added 'block' to the scope array for various product collection variations (best-sellers, featured, hand-picked, new arrivals, on-sale, related, top-rated, and upsells). 2. Modified the collection chooser logic to filter variations based on the 'block' scope. * Product Collection: Hide collection chooser toolbar for non-block scoped collections This commit modifies the ToolbarControls component in the Product Collection block to conditionally render the CollectionChooserToolbar. The toolbar is now only displayed for collections with a scope that includes 'block'. * Add scope property to product collections in E2E tests This commit adds the 'scope' property to all registered product collections in the E2E test plugin. The 'scope' is set to ['block'] for each collection. * Add changefile(s) from automation for the following project(s): woocommerce-blocks * Rename isShowCollectionChooserToolbar to showCollectionChooserToolbar for better readability. * Add documentation and refactor for product collection scope This commit introduces the following changes: 1. Update documentation to explain the `scope` argument for product collections 2. Refactor Collection Chooser and toolbar controls to handle default scope 3. Remove explicit `scope` from test collections to align with default behavior * Add E2E tests for Product Collection scope argument This commit adds E2E tests to verify the behavior of Product Collections registered with different scopes. It includes: - Tests for collections with 'inserter' and 'block' scopes - Verification of visibility in Collection Chooser - Checks for 'Choose collection' button visibility * Generate manifest file * Generate manifest file * docs: Remove unsupported emojis from product collection documentation --------- Co-authored-by: github-actions <github-actions@github.com> |
||
---|---|---|
.. | ||
block-theme-development | ||
building-a-woo-store | ||
cart-and-checkout-blocks | ||
code-snippets | ||
contributing | ||
contributing-docs | ||
data-management | ||
extensibility-in-blocks | ||
extension-development | ||
getting-started | ||
high-performance-order-storage | ||
localization-translation | ||
payments | ||
performance | ||
product-collection-block | ||
product-editor-development | ||
quality-and-best-practices | ||
reporting | ||
rest-api | ||
security | ||
shipping | ||
testing | ||
theme-development | ||
ux-guidelines-extensions | ||
ux-guidelines-payments | ||
ux-guidelines-product-editor | ||
ux-guidelines-themes | ||
wc-cli | ||
.manifestignore | ||
.markdownlint.json | ||
README.md | ||
docs-manifest.json |
README.md
post_title |
---|
WooCommerce developer documentation |
⚠️ Notice: This documentation is currently a work in progress. While it's open to the public for transparency and collaboration, please be aware that some sections might be incomplete or subject to change. We appreciate your patience and welcome any contributions!
This is your go-to place to find everything you need to know to get started with WooCommerce development, including implementation details for specific parts of the WooCommerce code base.
Getting started
WooCommerce is a customizable, open-source eCommerce platform built on WordPress. It empowers businesses worldwide to sell anything from physical products and digital downloads to subscriptions, content, and even appointments.
Get familiar with WordPress Plugin Development.
Take a moment to familiarize yourself with our Developer Resources.
Once you're ready to move forward, consider one of the following:
Contributions
The WooCommerce ecosystem thrives on community contributions. Whether it's improving documentation, reporting bugs, or contributing code, we greatly appreciate every contribution from our community.
- To contribute to the core WooCommerce project, check out our Contributing guide.
- To contribute to documentation please refer to the documentation style guide.
Support
- To request a new document, correction, or improvement, create an issue.
- For development help, start with the WooCommerce Community Forum, to see if someone else has already asked the same question. You can also pose your question in the
#developers
channel of our Community Slack. If you're not sure where to ask your question, you can always contact us, and our Happiness Engineers will be glad to point you in the right direction. - For additional support with customizations, you might consider hiring from WooExperts or Codeable.
Additional Resources
Other documentation
Some directories contain documentation about their own contents, in the form of README file. The available files are listed below, if you create a new README file please add it to the corresponding list.
Available READMe files for the WooCommerce plugin:
Root README
i18n/languages
includes
lib
packages
src
src/Admin/RemoteInboxNotifications
src/Admin/RemoteInboxNotifications/Transformers
src/Blocks
src/Internal
src/Internal/Admin/ProductForm
src/TransientFiles
tests
tests/api-core-tests
tests/e2e
tests/e2e-pw
tests/performance
tests/Tools/CodeHacking
Available READMe files for the WooCommerce Admin plugin:
Root README
client/activity-panel
client/activity-panel/activity-card
client/activity-panel/activity-header
client/analytics/report
client/analytics/settings
client/dashboard
client/header
client/marketing
client/marketing/components/button
client/marketing/coupons/card
client/marketing/components/product-icon
client/utils
client/wp-admin-scripts
docs
docs/examples
docs/examples/extensions
docs/features
docs/woocommerce.com
Available READMe files for the WooCommerce Beta Tested plugin: