feat(arch-linux): init

[ninetailedtori]

Closes #1870, closes #1381.

🎉 Theme for Arch Linux 🎉

Honestly, this is a major refactor of the existing arch-wiki theme into an umbrella "Arch Linux" userstyle, including:

• arch-wiki existing theme
  • migrated to mediawiki variables?
• an additional one started by someone else for aur.archlinux.org: feat(arch-user-repository): init #1870
  • merged with this PR yet?
  • finished?
• and all the others I'll be actively doing for Arch Linux!
  • archlinux (home)?
  • archlinux/download?
  • man.archlinux?
  • archlinux/packages?
  • security.archlinux?
  • bbs.archlinux?

💬 Additional Comments 💬

This is based off of the old PR that died, #1381, but will be moving the wiki to use MediaWiki variables in the library module e.g. #1895, once we can confirm it working as it should on arch's wiki (no leftover overriding on their end). All other sites will be done by me, aside from the AUR one which was done by someone else (though it'll be edited by me as well, to fall in line with the new style of formatting).

Requires: #1866

🗒 Checklist 🗒

• I have read and followed Catppuccin's submission guidelines.
• I have made a new directory underneath /styles/archlinux containing the contents of the /template directory.
  • I have ensured that the new directory is in lower-kebab-case.
  • I have followed the template and kept the preprocessor as LESS.
• I have made sure to update the userstyles.yml file with information about the new userstyle.
• I have included the following files:
  • catppuccin.user.less - all the CSS for the userstyle, based on the template.

[ninetailedtori]

PR is now up to every page aside from:

• Download DONE!
• Wiki (needs mediawiki lib, will set up my own localhost tomorrow)
  Feel free to test it for me! Security and BBS were the last ones I just did, and rework of AUR as well as expansion of it to include Packages (official) was done earlier as well! :]

[uncenter]

Looks like there is still a bunch of duplicated input styles?

[ninetailedtori]

Looks like there is still a bunch of duplicated input styles?

If you spot any duplicated styles that aren't being annoyingly overwritten by something on the page (like the .pun #brdX regions), do lemme know o7
I'm not sure how to get them to overwrite including on top of the other css used on the page without specificity unfortunately.

[ninetailedtori]

This is a reminder for me to change the mediawiki location once that's published, because I'm going to forget :P

[WalkQuackBack]

This may have rebased this onto the wrong branch. Could you try rebasing onto origin/main again?

[uncenter]

There's a lot of duplication between the first @-moz-document and for bbs.archlinux.com. Can we avoid that? Does the regex for the first one not include bbs?

[uncenter]

I might actually define all of these commons in a modular way, then just call the function within the required scopes at this point.

This is what I would recommend doing.

Not sure why they had something overwrite it though, very annoying. I'll see what I can do though, through specificity tinkering.

You could do a &, .pun wrapper for everything in the first moz-document and that would do the trick I think, a little ugly though.

[ninetailedtori]

I might actually define all of these commons in a modular way, then just call the function within the required scopes at this point.

This is what I would recommend doing.

Not sure why they had something overwrite it though, very annoying. I'll see what I can do though, through specificity tinkering.

You could do a &, .pun wrapper for everything in the first moz-document and that would do the trick I think, a little ugly though.

I'm going to do the wrapper, tragically there's no solution. I tried refactoring to remove dupes outright and it broke as like last time I tested. I'll wrap the whole thing I think.

[uncenter]

I'm going to do the wrapper, tragically there's no solution. I tried refactoring to remove dupes outright and it broke as like last time I tested. I'll wrap the whole thing I think.

Did you try making mixins and then just applying those in the right places? I see no reason why that wouldn't work if done correctly.

[uncenter]

Generally we should avoid regex if possible. Hard to read, hard to maintain, often there are better solutions :)

[uncenter]

Fwiw here is a good playground that I like to use: https://regex101.com/r/wrKYCM/1

[ninetailedtori]

Fwiw here is a good playground that I like to use: https://regex101.com/r/wrKYCM/1

That's what I've been using, have been for years! xD
Unfortunately it seems that \w is broken in stylus, which means we DO have to use .

[ninetailedtori]

Generally we should avoid regex if possible. Hard to read, hard to maintain, often there are better solutions :)

Also slower, so you're completely right on that. It's just in my regex mania I've completely forgotten to see if I could make it easier with just prefixing xD

[ninetailedtori]

I'm going to do the wrapper, tragically there's no solution. I tried refactoring to remove dupes outright and it broke as like last time I tested. I'll wrap the whole thing I think.

Did you try making mixins and then just applying those in the right places? I see no reason why that wouldn't work if done correctly.

Actually, this was my entire plan xD

[uncenter]

Unfortunately it seems that \w is broken in stylus, which means we DO have to use .

Yeah there isn't any reason we need to use \w over .. We aren't parsing or validating much here.

[uncenter]

That's what I've been using, have been for years! xD

Just saying I put the test strings for each of the URLs in there so it's easier.

[ninetailedtori]

That's what I've been using, have been for years! xD

Just saying I put the test strings for each of the URLs in there so it's easier.

Ya, that's what I've been doing! :3 it is annoying though, I have to then test it twice, because stylus regex isn't fully with the same accepted tokens as it is in that tester, so I have to check every time what sites are recognised. xD anyway rn I'm doing mixins, so will be big update soon!