42a90a317f
* Rework UX guidelines to be in distinct folders and files * Rename general guidelines to extensions guidelines * Move contents of user-experience-guidelines.md into readme * Rename "user experience guidelines" to "extension guidelines" * Moved payments blurb from onboarding to readme * Move product editor guidelines into a ux-guidelines folder * Remove extra quote on payment guidelines image * Add notice at top of theme customization page * Fix linting issues |
||
|---|---|---|
| .. | ||
| README.md | ||
| product-editor-examples.md | ||
| product-editor-form-custom-product-types.md | ||
| product-editor-form-dialogue-extensions.md | ||
| product-editor-form-fields.md | ||
| product-editor-form-groups.md | ||
| product-editor-form-sections.md | ||
| product-editor-form-subsections.md | ||
| product-editor-form-top-bar.md | ||
README.md
Our research shows that merchants think in terms of tasks and goals while creating new products in Woo. For example, adding or editing a product price is a separate task from uploading images or managing inventory.
For this reason, the new product form features groups (tabs) that correspond with these tasks. Simply speaking, they are separate views where different form features live. As a developer, you can extend any of these views and offer merchants the information and tools they need to create better, more successful products.
There are several ways to extend the new product form: from a single field to a whole group or section containing multiple fields and tables. These extension points are linked to the form structure, giving you plenty of freedom to create a great user experience.