Version 0.1.1 of this plugin was rushed to release because I wanted to get it out before WP 5.5.0 was released in the hopes that it would help developers of externally hosted plugins/themes ensure their code would work with the new Auto-updates UI in 5.5.0.
In that rush, I cut a lot of corners about how I normally structure my plugins because there just wasn't time to figure out the optimal structure for this plugin.
So, while PRs are always welcome, for the near term it is best for contributors to not spend time/effort on PRs that are solely related to how the code is structured, e.g.
- "you should put the CSS in it's own file and enqueue that file"
- "the render_tools_page() method is a mess, refactor it"
- etc
When the dust settles and WP 5.5.0 is out the door, I'll whip the structure of the code into shape and address some of the most glaring problems with the current structure (as I see it), including:
- better management of the strings, by for example, using a lookup so that all the ones that are identical except for the words
core, plugins and themes are right next to each other...so that it's easier to make changes to them and ensure that the same change gets made to the corresponding other strings
- make the main
plugin.php file into a simple "driver" that loads other classes that do all the real work
- etc
That said, PRs are more than welcome at this time for things like:
Please submit your PRs against the develop branch.
Issues for enhancements are also welcome at this time, but please wait until I get the base code in better shape before doing PRs for enhancements.
In time, I'll also get a proper CONTRIBUTING.md document written as well issue and PR templates added.
thanx everyone!
Version 0.1.1 of this plugin was rushed to release because I wanted to get it out before WP 5.5.0 was released in the hopes that it would help developers of externally hosted plugins/themes ensure their code would work with the new Auto-updates UI in 5.5.0.
In that rush, I cut a lot of corners about how I normally structure my plugins because there just wasn't time to figure out the optimal structure for this plugin.
So, while PRs are always welcome, for the near term it is best for contributors to not spend time/effort on PRs that are solely related to how the code is structured, e.g.
When the dust settles and WP 5.5.0 is out the door, I'll whip the structure of the code into shape and address some of the most glaring problems with the current structure (as I see it), including:
core,pluginsandthemesare right next to each other...so that it's easier to make changes to them and ensure that the same change gets made to the corresponding other stringsplugin.phpfile into a simple "driver" that loads other classes that do all the real workThat said, PRs are more than welcome at this time for things like:
Please submit your PRs against the develop branch.
Issues for enhancements are also welcome at this time, but please wait until I get the base code in better shape before doing PRs for enhancements.
In time, I'll also get a proper
CONTRIBUTING.mddocument written as well issue and PR templates added.thanx everyone!