Skip to content

Themes/Tweaks browser, sharing/import, custom themes/tweaks, and repo#633

Merged
7w1 merged 37 commits intodevfrom
feat/theme-edits-v2
May 5, 2026
Merged

Themes/Tweaks browser, sharing/import, custom themes/tweaks, and repo#633
7w1 merged 37 commits intodevfrom
feat/theme-edits-v2

Conversation

@7w1
Copy link
Copy Markdown
Member

@7w1 7w1 commented Apr 2, 2026

Description

Pulls themes and tweaks from https://github.com/SableClient/themes and allows basic searching and filtering in the themes settings.
Migration modal should work fine, prompts the user to either enable fetching from github or disable it and be limited to the built-in light/dark themes.
Theme links that end in *.preview.sable.css from the official repo will generate embeds, optional setting to allow generating embeds for any *.preview.sable.css file.
In chat previews are generated with extracted css values and are safe from injection. Full theme files will load the entire file, and are vulnerable to injection, hence the official safe repo. Third party themes sent in chat show a prominent banner making the risks clear.

Todo:

  • More clarity in settings menu when github fetching themes are disabled (right now it just has a browse button that immediately enables it, no confirmation or explanation) updated labels and added confirmation
  • Improve UI ? consolidated card styling

Maybe worth adding in the future but out of scope for the time being:

  • Info icon or some way to link to theme sources.

Mitigates #492 ?
Fixes #71
Fixes #617 (via tweak in theme repo)

image image

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change - disables themes, but there's a migration modal that prompts the user with 1 click to redownload and enable their existing theme(s).
  • This change requires a documentation update

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings

AI disclosure:

  • Partially AI assisted (clarify which code was AI assisted and briefly explain what it does).
  • Fully AI generated (explain what all the generated code does in moderate detail).

AI was used to write the code for parsing and extracting data from the raw css files/links and dynamically populate the lists as well as develop the migration system for current themes. Tests were AI generated.
All code has (or will be) thoroughly reviewed by me by the time this PR is ready.

Comment thread src/app/theme/previewCss.ts Fixed
@Septicity
Copy link
Copy Markdown
Contributor

I figure that proper custom CSS theming will require more thorough CSS-visible class names for each component; is that part of the plans for this, or would that be better accomplished with a tracking issue for another time?

@7w1
Copy link
Copy Markdown
Member Author

7w1 commented Apr 3, 2026

I figure that proper custom CSS theming will require more thorough CSS-visible class names for each component; is that part of the plans for this, or would that be better accomplished with a tracking issue for another time?

I think that's better as a separate issue.

@7w1 7w1 changed the title Themes browser, sharing/import/export, custom themes, and repo Themes/Tweaks browser, sharing/import, custom themes/tweaks, and repo Apr 4, 2026
@7w1 7w1 marked this pull request as ready for review May 5, 2026 02:43
@7w1 7w1 requested a review from hazre as a code owner May 5, 2026 02:43
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

Deploying with  Cloudflare Workers  Cloudflare Workers

Status Preview URL Commit Alias Updated (UTC)
✅ Deployment successful! https://pr-633-sable.raspy-dream-bb1d.workers.dev e6a7746 pr-633 Tue, 05 May 2026 04:01:12 GMT

@7w1
Copy link
Copy Markdown
Member Author

7w1 commented May 5, 2026

Something tells me merging this right now is a terrible idea but im merge-happy and everything seems to be working flawlessly soooooo

@7w1 7w1 merged commit 7bff2bd into dev May 5, 2026
12 checks passed
@7w1 7w1 deleted the feat/theme-edits-v2 branch May 5, 2026 04:08
ProfessorVarox pushed a commit to ProfessorVarox/sable that referenced this pull request May 5, 2026
> [!IMPORTANT]
> Merging this PR will create a new release.

## Features

* Add background styling to user profile cards
([SableClient#712](SableClient#712) by @nushea)
* Add preventing url preview cards by surrounding a link in
anglebrackets like <https://app.sable.moe>
([SableClient#717](SableClient#717) by @nushea)
* Reorganize Embed settings and reintroduce multiple embeds
([SableClient#667](SableClient#667) by @nushea)
* Change Misc. data styling in users profile pages
([SableClient#663](SableClient#663) by @nushea)
* add initial support for sending discoverable emojis and sticker
([SableClient#730](SableClient#730) by @dozro)

### Themes and tweaks from the catalog
([SableClient#633](SableClient#633) by @7w1)

Themes are pulled from [a repo](https://github.com/SableClient/themes)
now, so you get the full power of CSS instead of a palette. Tweaks are
new: CSS overlays that sit on top of whatever theme you are using.

You'll be prompted to migrate to the new system whenever you update, if
you choose not to, you'll be limited to the basic dark/light themes. A
few additional themes have been added (Rose Pine variantes, Catpuccin)
along with some basic tweaks (circular avatars, monochrome avatars, and
square stuff).

You can share themes and tweaks. For themes uploaded online, simply hit
the copy button in settings and paste the link in chat. If the setting
is enabled, a preview will be generated. Third party themes (as defined
by the config.json) have prominent warning banners and fetching is
disabled by default.

You can also export and share theme files directly, although no previews
are generated for these.

If you're intrested in getting a theme or tweak added to the official
catalog, contribute to the themes repo linked above! We're eager to add
more!

### Markdown parser and render updates
([SableClient#727](SableClient#727) by @7w1)

Migrated markdown parsing and rendering to use marked, which should fix
most (all?) markdown issues involving lists/nested structures,
inconsistent/inaccurate code blocks, escape sequences, and all the other
bugs with literally everything.

Added math rendering support via marked and KaTeX, uses standard `$$`
and `$` delimiters. Only renders a subset of latex tags that will likely
need to be expanded so feel free to make issues if needed.

Also adds support for sending markdown tables (although they're rendered
rather plainly at the moment), sending valid html directly (such as for
colored text), and properly escaping anything with backslashes.

Fixes link previews appearing in code blocks, fixes pmp new line
behavior, fixes links not opening in new tabs, and fixes editing
arbitrary html messages, probably.

Finally, the old WYSIWYG editor has been completely removed.

## Fixes

* Fix spam-clicking abbreviations crashing sable
([SableClient#665](SableClient#665) by @nushea)
* Add cache-control headers in Caddyfile for assets, service worker, and
index.html ([SableClient#609](SableClient#609) by
@Just-Insane)
* Fix the first pin event in a room looking empty
([SableClient#685](SableClient#685) by @nushea)
* Fix read receipt scrolling not working
([SableClient#631](SableClient#631) by @Septicity)
* Fix status sometimes sticking in member tile
([SableClient#664](SableClient#664) by @nushea)
* Fix apng files not animating.
([SableClient#737](SableClient#737) by @7w1)
* Some fixes to sync requests being spammed on loading screen and for
multi-account background syncing, it should also load faster now!
([SableClient#736](SableClient#736) by @7w1)
* Fix other dmed party not being added as a founder by default when
creating a dm. ([SableClient#737](SableClient#737) by
@7w1)
* Update verbiage in the credits
([SableClient#728](SableClient#728) by @nushea)
* spoilered text now gets replaced with `[Spoiler]` in the plain text
fallback, as per MSC4454
([SableClient#715](SableClient#715) by @dozro)
* Hide copied settings links on dynamic rows
([SableClient#695](SableClient#695) by @hazre)
* Fix button hover background smearing in virtual list rows by
suppressing transform on hover
([SableClient#614](SableClient#614) by @Just-Insane)
* Fix Workbox precaching by removing injectionPoint override that was
silently disabling all precache entries
([SableClient#611](SableClient#611) by @Just-Insane)

### Change how settings links are shared
([SableClient#695](SableClient#695) by @hazre)

Settings links copied from Sable now stay on the current client URL and
include a small Sable marker in the link. That lets Sable recognize
settings links copied from other Sable instances without treating
unrelated third-party `/settings/...` links as Sable settings links.

When you send a bare settings link in the composer, Sable now rewrites
it into a labeled link so it looks better on non-Sable clients too. For
example: `[Settings > Account > Display
Name](https://client.example/settings/account?focus=display-name&moe.sable.client.action=settings)`.

Invalid or malformed settings-looking links now stay normal links
instead of being shown as settings chips.

If you previously set `settingsLinkBaseUrl` in `config.json`, remove it.
Sable now derives settings links from the runtime app URL, and the old
config key is no longer used.
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.

Show avatars as circles Feature Request: Custom Theme Support

4 participants