feat(tangled): init

[NekoDrone]

🎉 Theme for tangled.sh 🎉

tangled.sh is a git collaboration platform (like GitHub) on the ATProto!

💬 Additional Comments 💬

tangled uses Tailwind for styling, so a lot of the components that are styled in this userstyle are based off the application of certain Tailwind utility classes. This means that it is likely to break and be a rather large maintenance burden on me.

I am intending to write PRs to upstream to give components aria-labels, ids, roles, or other forms of identifiers to hopefully reduce said burden.

🗒 Checklist 🗒

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

[uncenter]

Some unthemed areas in prose: bold text in https://tangled.sh/@tangled.sh/core/blob/master/readme.md, headings and non-highlighted code blocks in https://tangled.sh/@tangled.sh/core/blob/master/docs/knot-hosting.md.

[NekoDrone]

why is a direct markdown doc view rendered differently from the repo readme 😭

[uncenter]

why is a direct markdown doc view rendered differently from the repo readme 😭

It's also unthemed when the main repo readme is rendered though? https://tangled.sh/@tangled.sh/core#tangled

[uncenter]

Text in comment/presumably other input boxes is unthemed.

[uncenter]

Text in list items is unthemed (we love Tailwind prose....): https://tangled.sh/@tangled.sh/core/issues/130#706201.

[NekoDrone]

i was talking about codeblocks on a readme but i'm realising that the style is getting applied because of chroma.

if a language is unspecified in the markdown, it doesn't get chroma applied to it, and so it doesn't get styled

also my god tailwind prose is a mess.

[NekoDrone]

let me just do one final check through myself

[NekoDrone]

for code blocks, i'm deliberately putting the background at base even though the chroma import puts the background at surface0, preserves tangled's choice

[NekoDrone]

okay, I think that's everything

i cannot wait to add aria labels and ids to upstream my god

[WalkQuackBack]

Aria-label's aren't great for theming as they are localisation based, adding proper accessibility roles and such would achieve the similar thing without being dependent on a specific language

[uncenter]

Inline code blocks blend in with the issue comment background, e.g. | markdown on https://tangled.sh/@tangled.sh/core/issues/143.

[NekoDrone]

missed it when i lightened everything by a shade :P

[NekoDrone]

🥴 https://tangled.sh/@icyphox.sh/legit

non-markdown readmes are rendered differently 💀

[NekoDrone]

is there anything else we need to add here? or are we waiting on upstream to update to using CSS variables? @uncenter

[uncenter]

is there anything else we need to add here? or are we waiting on upstream to update to using CSS variables? @uncenter

Would quite prefer it but I'll consider this.

Things with .dark\:text-gray-400 are unthemed - see <time> elements like "two hours ago" in issue listings, hashes or something under keys in settings.

[NekoDrone]

I'll take a look soon! thanks