The global JavaScript method importArticles() provides a common interface for including articles that contain scripts or styles on a community.

The functionality is similar to the existing methods importScriptPage and importStylesheetPage. However, importArticles() can import articles from external communities, bundle several articles into one, minify them and serve them as a single request. This reduces both file size and web traffic, effectively making a community with a large number of additional files load a lot faster.


The importArticles() method relies on module definitions to load articles. Modules are essentially a JavaScript object with key/value properties. The following properties are required in every module:

  • type - This property denotes the type of articles this module will contain. The supported types are:
  • articles - The articles you wish to import. See the locating articles section below for more information on what to put here.

Any number of modules can be passed into importArticles(). However, all of the articles within a module must be of the same type.



Links generated by importArticles() (and the advanced techniques described below) are cached for a maximum of 10 minutes. So whenever you make a change you can assume that after 10 minutes all the users coming to your community will be served the updated version of JS and CSS files if importArticles() is used.

Locating articles

Simple syntax is used to locate the articles you're trying to import. It is very similar to, and compatible with, interwiki links:


Anything in parentheses above is optional, and anything in brackets above denotes user input. The colon character is used to separate the string into different segments for parsing. Prefixes tell us how you want to look up the article and are generally followed by a community name, except in the case of a local community.

Local articles

Articles on the local community can be located by title in the same way that you would link to them normally. They do not require a prefix or community name. For example, if you wanted to import the article MediaWiki:Common.js, the following would work inside an importArticles statement:


External articles

Articles from external communities can also be located the same way that you would link to them normally. However, unlike local articles, external articles require the use of a prefix and community name to determine which community you will be importing them from and how you will identify that community. FANDOM supports looking up communities by their URL. URL lookups are performed for the u prefix. For example, if you wanted to import the article Highlight/code.css from the Dev Wiki, the following would work inside an importArticles statement:


This syntax will also work for wikis in other languages. For example, if you wanted to import the article MediaWiki:Common.js from the Italian version of One Piece Wiki:


Advanced usage

Behind the scenes, the importArticles() method performs three necessary tasks:

  1. Generating a properly formatted URL for use with ResourceLoader,
  2. Performing sanity checks on the modules provided to assure they are properly formatted
  3. Providing the user feedback in the case of an error.

However, use of the method is not strictly required to gain the benefits of combining and minifying multiple articles into one request. If you'd like, you can generate the URL manually and load the assets using other means, such as @import statements in CSS or jQuery.getScript in JavaScript.

While there are many parameters you can include in the URL, the following are probably the most useful:

Parameter Parameter Description
mode Tells ResourceLoader that we will be loading articles. Should be set to "articles."
articles The list of articles. If multiple articles are provided, they should be separated by a pipe "|" character.
only The type of articles to import. Should be set to either "scripts" or "styles."
debug This parameter is not necessary by default but can be set to "true" to disable minification to allow for easier debugging of problems within the imported articles.

In the end, you should end up with a URL that looks something like this:


Which can be used in conjunction with @import, like so:

@import url("/load.php?mode=articles&articles=One.css|Two.css&only=styles");

If the css is hosted on another community or websites outside of FANDOM such as Dropbox, the url should have the http:// or https:// like this asset file for example:

@import url("");

It will use the CSS file from the source website to import to whatever CSS page it's been put on. If the style sheet file is edited outside of FANDOM and an import syntax with the raw file is in use, an immediate change will occur. CSS pages that have been edited with the import used will have the waiting state before taking effect. They should have the codes that customize the FANDOM interface in-order to take effect if the imported css comes from another internet source not hosted on FANDOM.

For Javascript, using external third party sites may open up a security risk and should only be imported from a site inside FANDOM.


Importing multiple script articles, one from the local community and one from an external:

    type: "script",
    articles: [

Importing multiple style articles, one from the local community and one from an external:

    type: "style",
    articles: [

Importing multiple modules in a single method call:

    type: "script",
    articles: [
}, {
    type: "style",
    article: "MediaWiki:Common.css"

Alternate Syntax Examples

The importArticles() method also supports a simplified, alternate syntax for common use cases. For convenience, the method importArticle() is also defined.

Including a single file from the local community using a module definition:

    type: "style",
    article: "MediaWiki:Common.css"

See also

Further help and feedback