<p>Just FYI, the CSS I linked to doesn't work on UCP wikis due to a change in the HTML structure of pages. </p>

<p>Well then, we don't know if personal @import is possible on UCP. It's aweful to not have it, though. I think it's possible to just import CSS pages with the personal JS? </p>

I believe so. importArticles seems to work for CSS even though it isn't working for JS at the moment.

<p>What's the difference between @import and <a href>? </p>

<div class="quote"><i> <p>Andrewds1021 wrote: Correct me if I am wrong but I thought: </p>

1. For legacy wikis - Fandom removed the Common.css v. Wikia.css order issue by changing how the files are loaded.
2. For UCP wikis - @import doesn't work because site CSS get's stuck after global CSS.

</i></div>
<p>So this section is out-of-date: Help:Advanced_CSS_and_JS#Load_order? </p>

<p>Yes and no. The importance of load order for the purposes of @import in site CSS is no more (at least on legacy wikis). However, it is still applicable to personal CSS. Either way, it has always been the case (on legacy wikis) that global CSS does not prevent imports in site CSS and site CSS does not prevent imports in personal CSS. However, the styles are applied in that order which is critical when it comes to resolving conflicting styles with identical specificities. I hope that made sense. </p> <hr><p>Edit: </p><p>Well, I guess strictly speaking the answer is "yes". However, most of it is not out-dated. </p>

<p>I guess I was actually thinking about this section: Help:Community_CSS_and_JS#CSS_pages </p>

<p>The part about which is loaded first is indeed irrelevant now. However, it is still true that some wikis don't have Common.css load at all. So that portion of the section is still very much relevant. </p>

<div class="quote"><i> <p>AtoneTheMage wrote: What's the difference between @import and <a href>? </p> </i></div>
<p>a is a HTML element that makes links, @import is a CSS sentence to import one stylesheet into another. I'm not sure why you see a relation between them. </p>

<p>Given this previous thread, I am thinking AtoneTheMage might be getting confused by ambiguous wording. If I say, "a link element", I could mean one of two things. First, I could mean an a-tag that is used to creating a link on the page that users can click to go to a different page. Second, I could mean a link-tag that is used to "import" a script or stylesheet onto the page. </p>