Two weeks ago, Justin Tadlock published a proposal on behalf of the Theme Review Team to create a set of standardized packages that theme authors can drop-into their themes. This week, the team has released two feature packages that illustrate what the project is trying to accomplish.
The first is
“This is a foundational package that will allow you to use any other packages that we create,” Tadlock explained. “You could even use it for autoloading your own theme classes if you choose to do so (assuming they follow the PSR-4 autoloading standard for class and folder names).”
The second package provides a Customizer Section Button that enables theme authors to create a link or button that points to a URL. This feature was originally developed to allow developers a standard way to display a Pro/Upsell link within the
Tadlock also provided feedback on a number of ideas that were proposed. Packages up for consideration include, Breadcrumbs, Sliders and Sections, Mobile Navigation, Color Control with Transparency, Appearance > Theme Name Page, and Standard Template Hooks.
To read his feedback and learn more about the project, including how to get involved, read the feature package update and the initial proposal.
Oh god. He is registering yet another autoloader for count($this->loaders) TIMES count($collections).
https://github.com/WPTRT/autoload/blob/master/src/Loader.php#L102
Can it be any more inefficient? Just shoot me now. Ugh.
-Mike
P.S. Core should have ONE autoloader function — that only runs a tiny amount of code for each attempt to load a class file — for all themes and for plugins) to use, and they should do it via a class map created with a build script just like themes create CSS from SCSS files today.
Every theme and every plugin creating their own autoloaders is just a nightmare.