| 5 | | **To be perfectly clear:** I don't think accessibility should be an option in a plugin (even a community plugin) as Matt often suggests. But I believe community plugins are a great way to test things, to demonstrate their feasibility and the robustness, **before eventually implementing them into core**. |
| | 5 | **To be perfectly clear:** I don't think accessibility should be an option in a plugin (even a community plugin) as Matt often suggests. But I believe community plugins are a great way to test things, to demonstrate their feasibility and their robustness, **before eventually implementing them into core**. |
| | 6 | |
| | 7 | For the record, I managed to ship the theme/plugin auto-update system into core via a Feature Plugin and I think this system is pretty good to test a feature in the wide, before merging it into Core: https://wordpress.org/plugins/wp-autoupdates/ |