20180629 Status Update

I’ve just started developing a site using WPRig.io, it’s pretty neat – and it’s really a terrific starter theme that allows modern tooling. It saves a lot of the time with small annoying tasks that typically come with starter-theme development.

The Good:

  • easy browser sync
  • progressive and conditional CSS loading
  • auto compile, auto image compress
  • drag-n-drop in template files (ie: site needs comments.php, just include ins
  • built in support for cssnext

The Bad

  • There should be a less repetitive way to combine preloading wprig_add_body_style(), registering, and printing stylesheets. Currently you need to add a stylesheet in three different locations to load it properly
  • Version numbers for register/enqueue are hard coded, and repeated – should be put into a constant so dev’s can hard refresh their visitors resources if needed

The Ugly

  • lacks BEM naming

I’ve just started using it, so perhaps I’m being to quick to criticize, so take that with a grain of salt. I will probably submit a pull request for the things I find to help the project grow.

So, if everything continues goes well, I’m considering condensing my starter theme into components for wp-rig’s /dev/pluggable/ folder, and re-creating my personal starter theme with this logic. These will basically serve as helper functions that I expect and need.

%d bloggers like this: