Merge pull request wp-cli#206 from wp-cli/3323-distribution-earlier

danielbachhuber · web-flow · commit 63dfa06516d0 · 2016-08-24T06:22:37.000-07:00
Mention distribution methods earlier in the commands cookbook
diff --git a/docs/commands-cookbook/index.md b/docs/commands-cookbook/index.md
@@ -17,7 +17,9 @@ Creating your own custom WP-CLI command can be easier than it looks — and you
 
 WP-CLI's goal is to offer a complete alternative to the WordPress admin; for any action you might want to perform in the WordPress admin, there should be an equivalent WP-CLI command. A **command** is an atomic unit of WP-CLI functionality. `wp plugin install` ([doc](/commands/plugin/install/)) is one such command, as is `wp plugin activate` ([doc](/commands/plugin/activate/)). Commands are useful to WordPress users because they can offer simple, precise interfaces for performing complex tasks.
 
-_But_, the WordPress admin is a Swiss Army knife of infinite complexity. There's no way just this project could handle every use case. This is why WP-CLI includes a set of [common internal commands](/commands/), while also offering a rich API for third-parties to register and [distribute their own commands](/package-index/). There are also a [variety of internal APIs](/docs/internal-api/) you can use in your custom WP-CLI command.
+_But_, the WordPress admin is a Swiss Army knife of infinite complexity. There's no way just this project could handle every use case. This is why WP-CLI includes a set of [common internal commands](/commands/), while also offering a [rich internal API](/docs/internal-api/) for third-parties to write and register their own commands.
+
+WP-CLI commands can be [distributed as standalone packages](/package-index/), or bundled with WordPress plugins or themes. For the former, you can use `wp scaffold package` ([repo](https://github.com/wp-cli/scaffold-package-command)) to dynamically generate everything but the command itself.
 
 #### Command types
 
