• I really love this plugin but there are two things holding me off from buying it right now and both would seemingly be pretty easy to implement (splitting into two separate topics so they could be addressed individually)

    Having the possibility of grouping resources by what they are. Ex. my wordpress theme has a “testimonials rotator” built in, which actually is facilitated by 2 different .js files and a .css file. So when deciding if I want to activate or deactivate these on a page, imagine if these 3 items could be grouped into a custom label of “Testimonial Rotator” (I set the name not programatically determined).

    That way if I’m determining enabling/disabling resources each post, I can quickly determine yes or no to multiple things without having to look at the small print on the “handle” line to see what the script actually is.

    Also, (not sure if it’s worth separate functionality or just using the above grouping one for it) but a lot of asset names are kind of convoluted and take some digging to figure out what they actually are, so the ability to have an alias for the individual files would probably be helpful. Ex. using the above example it may be “testimonial css”, “testimonial lazy loading js”, and “testimonial animation js”. This is very similar to the current “notes” function, but I mean for it to be up high and large font for quick decision making.

  • The topic ‘Grouping / Aliasing of CSS / JS’ is closed to new replies.