50b58e54ff
* updated instances in docs * Fix beta testing title + regen manifest --------- Co-authored-by: Jacklyn Biggin <hi@jacklyn.dev> |
||
|---|---|---|
| .. | ||
| CSS-SASS-coding-guidelines-and-naming-conventions.md | ||
| README.md | ||
| api-critical-flows.md | ||
| common-issues.md | ||
| deciding-pr-high-impact.md | ||
| deprecation-in-core.md | ||
| minification-of-SCSS-and-JS.md | ||
| naming-conventions.md | ||
| reporting-security-issues.md | ||
| string-localisation-guidelines.md | ||
| woocommerce-git-flow.md | ||
README.md
| category_title | category_slug | post_title |
|---|---|---|
| Contribute to Woo | contributing | Contribute to Woo |
Interested in joining the Woo contributor community? The links in this doc summarize and direct you to the order of operations you will need to make your first contribution. If you are a seasoned WooCommerce developer, feel free to skip ahead and utilize the template links, or the reference docs and guides below.
Contributing to WooCommerce Core
The WooCommerce core plugin code can be found in our monorepo. Here you can contribute to:
Code of Conduct
Contributing to an open source project requires cooperation amongst individuals and organziations all working to make our project a stable and safe place to build and ask questions. Please thoroughly read our Code of Conduct to get familiar with our standards and processes.
Contributor Guidelines
Our contributor guidelines layout the first steps to contributing.
- Prerequisites and developer tools to get started
- PNPM commands, plugin development environment packages, and troubleshooting
- Coding standards, E2E testing links
Templates, Bug Reports, and Feature Requests
Security
Security and safety for data management are incredibly important to us at Woo. Please check out the Automattic security policy to learn about our foundational requirements.
Please report any vulnerabilities or security issues by reading through Woo's security policy here.