Clifford
Clifford
https://github.com/julien731/WP-Review-Me exists for .org but optionally link elsewhere
https://flintci.io/docs#composernormalize to help keep Composer sane
Inspiration: https://matthewhorne.me/defer-async-wordpress-scripts/ Would be best if WordPress implements this itself, though: https://core.trac.wordpress.org/ticket/12009 Same goes for SRIs: * https://core.trac.wordpress.org/ticket/33948 * https://github.com/meitar/wp-sri
If `SCRIPT_DEBUG`, set a JS/CSS file's version to `time()` instead of the plugin version number for cache busting's sake
* https://torquemag.io/2018/06/advanced-oop-for-wordpress-part-6-continuous-integration-for-wordpress-plugins/ * https://www.branchci.com/
To test front-end https://docs.cypress.io/guides/getting-started/writing-your-first-test.html
* https://github.com/10up/plugin-scaffold/blob/master/composer.json * https://github.com/10up/phpcs-composer * https://github.com/PHPCompatibility/PHPCompatibilityWP
Idea is to be able to parse the plugin's `readme.txt` so we could get things like the long description or the changelog. Just a nice-to-have. https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/#markdown > The readmes use...