Talk:List of JavaScript enhancements

Scope
I've noticed some of the headers suggest certain types of script are limited to personal. For example, Interface Personalisation states: "These scripts alter the way Wikis look or behave so that it's more to your liking. Only use these in your personal JavaScript/CSS files, do not add them to the Wiki itself." I know this is not true for at least one script in that list. Similarly, Site enhancement suggests most of the scripts are only suited to site-wide installation, which again isn't true. My overall point is that grouping them under headers might make them a little confusing at times.

With that in mind, I'd like to template the entries to look something like this: HeaderLinks [s] [p] - . The usage would look something like this:

Thoughts?


 * That would make it a lot clearer. I second this notion. --  sqm talk 11:24, 05.19.2014
 * You mean remove the headers completely and list all the available scripts in plain list form?
 * I am also worried about the size bloat by using the template considering the amount of scripts and the rate at which they continue to increase. Though it would be neat; but huge
 * I seriously feel that there is a dire need for another method to organise all the scripts in a way which would be easier to navigate and find for users
 * Seperating them into different pages (and tabview) or dynamically generating lists using dpl might work.~Ultimate Supreme  16:13, May 19, 2014 (UTC)


 * Dpl is another option, but that would require some reworking of the infobox to add a type parameter and a relevant category for dpl to hook onto. Maybe we can make use of dpl's url variables to show a more specific list or some sort of js form to allow us to search for certain names, types, scope, etc? I'll get dpl enabled here so we can explore if it's suitable for what we need.