Skip to content

feat(ui): add abyss theme (Web/App)#13555

Open
burgercrisis wants to merge 21 commits intoanomalyco:devfrom
burgercrisis:abyss
Open

feat(ui): add abyss theme (Web/App)#13555
burgercrisis wants to merge 21 commits intoanomalyco:devfrom
burgercrisis:abyss

Conversation

@burgercrisis
Copy link
Copy Markdown

Closes #13554

Summary

Add Abyss theme for Desktop/Web based on the existing CLI palette w/ full WCAG compliance
Register the theme in the default theme list

Screenshots

dark

image

light

image

How I tested

Switched theme to abyss in both light and dark modes

Checked visually and adjusted with WCAG compliance app, reiterated, aligned light mode stylistically

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All the current themes contain ~130 lines of code. Your suggested theme contains 750. Do you know why is that?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, I was wrong - OC-1 theme contains ~540 LOC. I'm wondering why, does not seem to be the standard

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And Tokyo night has ~150 LOC. It is clear that these themes have more color keys than most of the others. Probably should be refactored, i think all themes should have the same number of color keys

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did an inspection just now; I will refactor it;
Basically, I was ensuring full WCAG compliance + classic abyss main colors; in my WCAG checking process, I was checking every apparent UI pair, but missed something that led to an expansion of tokens;

on inspection it seems like some past existing mappings were actually deleted from the actual UI at some point; so thats why OC-1 has 540 and mine has even more, but some mappings for OC-1 actually don't go anywhere (at minimum text-on-interactive-base, text-on-interactive-weak, still need to actually confirm the rest of the suspects), and I didn't catch things like that when I built my WCAG compliance checking system so I inherited a lot of extra WCAG checks. Since I'll be fixing my Abyss theme, I could try fixing the unmapped items from OC-1 as well for a separate pr since it wouldn't add much work doing both

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alexyaroshuk I've carefully looked over the theme system, cleaned up placeholder/dead tokens, and removed overrides that could be generated from seeds and reduced line count to 105 while maintaining style. I may have a push later to remove deadcode tokens as well and/or reduce token count in other themes. Cleaned commit here

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@burgercrisis looks good, i checked out your pr - but it seems you hadn't merged latest upstream. make sure you do that, and resolve existing conflicts

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alexyaroshuk Woops, just merged the latest origin/dev

Copy link
Copy Markdown
Author

@burgercrisis burgercrisis Feb 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the only "conflict" was that oc-2 and abyss were added in the same spot in default-themes, I have to assume the failed checks are from the workflow updates that were just done in the dev branch

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alexyaroshuk merged the stable merge in, no more conflicts or failed tests

@alexyaroshuk
Copy link
Copy Markdown
Contributor

Could this get a look? @adamdotdevin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEATURE]: abyss desktop theme

2 participants