Help talk:Including additional CSS and JS

importScriptURI vs. $.getScript
Hi Kangaroo! I'm going to revert the edit where you replaced  with. returns  when the script is already loaded. So to play it safe, you would have to write:

Other scripts might load  as well, so simply assigning a value to   is risky:

covers all of the above:

-- peco e s 05:09, August 24, 2012 (UTC)

ImportArticles misleadingly generic function name
ImportArticles sounds pretty generic for something that really only supports CSS and JS. Why use that name? Wouldn't something like ImportCSSorJS have been better? -- Fandyllic  (talk &middot; contr) 24 Aug 2012 6:53 AM Pacific


 * Hi Fandyllic! Haven't heard from you in ages! How are you?


 * Anyway: You should probably post that question in the Blog that introduced : w:User_blog:DaNASCAT/Update_Your_CSS_and_JavaScript_To_Speed_Up_Your_Wiki. My guess is - and I haven't really studied the ResourceLoader yet - that   is used for a lot more than loading scripts and stylesheets... That's just a guess though. -- peco e s 15:44, August 24, 2012 (UTC)


 * From a user perspective, it can be a little confusing since it is mainly a way to add scripts or styles to a wiki. However, at a deeper level, these scripts and styles are actually articles, so in essence you are importing articles that contain scripts or styles. Kyle Florence (talk) 17:41, August 24, 2012 (UTC)

Using importArticles in MediaWiki 1.16.5
If you would like to use the cleaner  syntax in a MediaWiki 1.16.5 Wiki then you can place the following code at the top of your   page. Note that this code will not give you the speed improvements that the real  does, it just lets you use the newer syntax until your Wiki is upgraded. This helps you prepare your wiki for the upgrade in advance so that the benefits of  will kick in immediately after the upgrade happens.