| 7 | | @dd32 I'm excited to see Gutenberg [https://github.com/WordPress/gutenberg/issues/2474#issuecomment-327875802 exploring wp.hooks as a possible api for adding extensibility]. At the same time, I am trying to forward the ongoing effort to make our existing JavaScript more accessible and extendable - especially our single page apps - the media modal, the media grid, the new theme browser, the installed theme browser, the customizer, the editor and the revisions screen (i may have missed some). `wp.hooks` seems like a great fit make these components more extendable, 'modern' JavaScript approaches may not be as good a fit. How would you propose we work on making our existing JavaScript more extendable in core? Wait until the Gutenberg project decides how to approach extendability, then see if we can retroactively apply that approach to our legacy JavaScript? |
| | 7 | @dd32 I'm happy to see Gutenberg [https://github.com/WordPress/gutenberg/issues/2474#issuecomment-327875802 exploring wp.hooks as a possible api for adding extensibility]. At the same time, I am trying to forward the ongoing effort to make our existing JavaScript more accessible and extendable - especially our single page apps - the media modal, the media grid, the new theme browser, the installed theme browser, the customizer, the editor and the revisions screen (i may have missed some). `wp.hooks` seems like a great fit make these components more extendable, 'modern' JavaScript approaches may not be as good a fit. How would you propose we work on making our existing JavaScript more extendable in core? Wait until the Gutenberg project decides how to approach extendability, then see if we can retroactively apply that approach to our legacy JavaScript? |