feat(codeberg): accessible header, themed landing page.

[ninetailedtori]

🗒 Checklist 🗒

• I have read and followed Catppuccin's userstyle contributing guidelines.

• I used AI (or AI-assistance) for this change.
  • NEVERRRRRRRRRRRRRRRRRRRRRRRRRRR [angry anti-ai noises]

🔧 What does this fix? 🔧

• Makes the navbar mantle, with hover buttons as accent, it's cleaner and more accessible to read imo (less violently bright on accents like rosewater).
• Adds the codeberg landing page theming. Codeberg | About
• Adds isWarning class for isSigned shasums which aren't verified.

Troubles with this PR?

Yes, actually! Here's a list of pages I haven't themed, and WHY:

• so, docs.codeberg.org, relies a ton on halfmoon, which is a theme loaded through bootstrap. that's honestly gonna be quite painful to theme, without a dedicated library, which is gonna require a lot of work, because there's about 500 variables here that are all bound and tangled, and a lot are just duplicates that navigate to other vars, etc. See halfmoon.css on that site. This is writable, but we'll have to write a lib, which will then define the 500 or so variables.
  • As a secondary, uses PrismJS for syntax-highlighting.
• blogs.codeberg.org uses...scoped halfmoon, scoped to its own codeberg-design module, which...umm, somehow defines a whole new 1500 variables. That's just not gonna be fun. See codeberg.css on that site. This just isn't feasible, so either we just sloppily define what we can see, and patch as we go along, or we just ignore the website entirely. It's not a major subdomain that people want afaik?
  • As a secondary, uses Pygments for syntax-highlighting.
• donate.codeberg.org is the lightest, and uses pico, which you can see, lies in pico.min.css which you can see on the site. It's not hard to theme, but the correct thing to do in accordance with our own userstyle/lib modularisations, is to write a lib for pico, then import it. This one does have a very light solution but not something we should care about until we get a pico library, because it's not worth doing yet, and not something major, just like blogs.

[uncenter]

As I've stated before, I'm not quite sure theming the donation and blog pages are the best use of our time and maintenance especially given their length and complexity. Can we remove those changes and just focus on the "accessible header"?

[ninetailedtori]

As I've stated before, I'm not quite sure theming the donation and blog pages are the best use of our time and maintenance especially given their length and complexity. Can we remove those changes and just focus on the "accessible header"?

I did remove them. Just the barebones rn, please check. Accessible header, and landing page (which was very cheap to maintain.)

[ninetailedtori]

There are a couple single-line imports, because the docs and blogs each use a library, one pygments, one prism, and it's quite lightweight for us not to care about that and to just have a one-line import for each domain.