Retool the introduction

Author: danielbachhuber

_posts/2016-11-29-version-1.0.0.md

@@ -6,11 +6,15 @@ title: Version 1.0.0 released
 
 Woohoo!
 
+Over the course of 5+ years, hundreds of contributors have worked to bring you WP-CLI v1.0.0, which I'm proud to announce today.
 
+This release represents a level of maturity few open source projects achieve. It also marks a transition point, where the WP-CLI project shifts focus to enabling innovation through the WP-CLI package ecosystem. Building new features as standalone packages promotes faster iteration, more creativity, and distributes the maintenance burden more sustainably. As these community packages find success, we'll bring their learnings back into WP-CLI, alongside bug fixes and minor enhancements.
+
+Now that the issue backlog is [down to zero](https://twitter.com/danielbachhuber/status/802951083354009600), I'm personally looking forward to getting more ideas cooking for [runcommand](https://runcommand.io/), my own WP-CLI innovation studio.
 
 ### Introducing `WP_CLI::runcommand()`
 
-`WP_CLI::runcommand()` ([doc](/docs/internal-api/wp-cli-runcommand/)) is the new best way to run WP-CLI commands from within your WP-CLI command. It's as though `WP_CLI::run_command()` and `WP_CLI::launch_self()` grew up, married, and had a perfect child.
+`WP_CLI::runcommand()` ([doc](/docs/internal-api/wp-cli-runcommand/)) is the new best way to run WP-CLI commands from within your WP-CLI command. It's as though `WP_CLI::run_command()` and `WP_CLI::launch_self()` grew up, married, and had the perfect child.
 
 With `WP_CLI::runcommand()`, you can:
 
@@ -19,9 +23,11 @@ With `WP_CLI::runcommand()`, you can:
 * Return STDOUT generated by the command, or all command execution details (STDOUT, STDERR, return_code) as an object.
 * Optionally parse captured STDOUT as JSON.
 
+Relevant pull requests include: [#3605](https://github.com/wp-cli/wp-cli/pull/3605), [#3619](https://github.com/wp-cli/wp-cli/pull/3619), [#3621](https://github.com/wp-cli/wp-cli/pull/3621)
+
 ### Breaking changes: Uses return code 1 when batch operation partially fails.
 
-Some commands support performing the same operation against multiple resources (e.g. updating two or more plugins wit `wp plugin update akismet hello`). Previously, if one of the operations failed (e.g. a plugin update failed to be downloaded), WP-CLI would display a warning, continue on, and exit with return code 0. Beginning in v1.0.0, WP-CLI uses return code 1 when one or more operations fails.
+Some commands support performing the same operation against multiple resources (e.g. updating two or more plugins with `wp plugin update akismet hello`). Previously, if one of the operations failed (e.g. a plugin update failed to be downloaded), WP-CLI would display a warning, continue on, and exit with return code 0. Beginning in v1.0.0, WP-CLI uses return code 1 when one or more operations fails.
 
 Affected commands include: