-
·
Contributing
How can I get started? The AI Team offers lots of ways to participate, and we’d love to have you join us! To start, we recommend that you: Create a WordPress.org user account or log in if you have one already. Sign up for an account on Slack using your WordPress.org user account and join the #core-ai channel. This is where we hold all…
-
·
About
The WordPress AI team is dedicated to exploring and coordinating artificial intelligence projects across the WordPress ecosystem. This is just the beginning. Whether you’re an engineer, designer, researcher, or just curious about AI, we’d love to have you involved as we shape the future of AI in WordPress.
-
·
Meetings
There are currently two types of meetings that make up Core-AI’s cycle of development. Bi- Weekly we have a Slack AI chat , and weekly we have a Core-AI team Webinar. Both are open to everyone to attend but with some difference’s on the purpose and execution of each. Bi-Weekly Slack AI Chat This meeting…
-
·
AI Handbook
Welcome to the AI Team Handbook, the place to learn how to get involved with the WordPress AI community, and start contributing to WordPress AI. Whether you’re an engineer, designer, researcher, or just curious about AI, we’d love to have you involved as we shape the future of AI in WordPress. Here you can learn about…
-
·
Contributions
Bug reports – Help ensure your issue is resolved in a timely manner. Contributing – An introduction to the contributing process. WordCamp Contributor Day – Quick-start guide for WordCamp Contributor Days. Ideas – Up-vote existing ideas or submit your own. Governance – Summary of those behind WP-CLI. Licensing – License requirements for third-party code and…
-
·
Guides
Installing – Recommended and alternative installation mechanisms. Quick start – Where to begin after you’ve installed WP-CLI for the first time. Running commands remotely – Learn how to remotely control multiple servers at once. Commands cookbook – The full 101 how commands work, writing your own, and sharing them with the world. Writing Behat Tests…
-
·
References
Argument Syntax – Explanation of the syntax conventions used in command synopsis. Global parameters – Variables defining how a command is executed, including which WordPress user the command is run as and which WordPress instance the command is run against. Built-in commands – Commands included in every copy of WP-CLI. Internal API – Stable utilities…
-
·
Supporting Quality: How We Handle Repeated Low-Quality Translations
Sometimes, our Global Translation Editors (GTEs) need to address situations where a contributor keeps submitting translations that don’t quite meet our quality standards. This is important because it directly impacts the workload of our dedicated volunteer validators, who generously give their time to keep our project’s translations accurate and reliable. To better support our validators,…
-
·
Then /^the return code should( not)? be (d+)$/
Expect a specific exit code of the previous command. Usage Scenario: My example scenario Given a WP installation When I try `wp plugin install` Then the return code should be 1 Behat steps documentation is generated from the WP-CLI codebase on every release. To suggest improvements, please submit a pull request. Related Then /^(STDOUT|STDERR) should(…
-
·
When /^I launch in the background `([^`]+)`$/
Launch a given command in the background. Usage Scenario: My example scenario Given a WP install And I launch in the background `wp server –host=localhost –port=8181` … Behat steps documentation is generated from the WP-CLI codebase on every release. To suggest improvements, please submit a pull request. Related When /^I (run|try) `([^`]+)`$/ – Run or…