Don't put user contributed theme in core repository

[azzamsa]

Hi,

IMO, putting a user-contributed theme in the core repository will lead to some bad consequences.
We need to limit ourselves to only having two built-in themes: light and dark. Other themes should go to a different repo, like lla-themes.

Helix puts user-contributed themes in their core repo, but now they have a similar discussion Coming up with a policy for "built in" themes · helix-editor/helix · Discussion #10635.

We can implement something like Yazi flavors, a glorified them repos that users are able to update using a simple git pull. Or just a simple copy-paste similar to Alacrity approach.

On the other hand, Wezterm doesn't hardcode any theme, it just sync and pull from different sources, if you want to go that route.

But for starters, I think the Alacritty approach is the easiest.

Thanks for lla 🧁

[chaqchase]

Hi @azzamsa ! Thank you for sharing your thoughts on theme management.
I completely agree with your perspective on theme management. We're actually planning to move in exactly that direction - separating themes into their own repository under a dedicated organization that will house all lla-related projects (themes, plugins, etc.).
The current approach of including themes in the core repo is temporary. The main reason is to avoid confusion for users who might look for official themes in my personal GitHub account. Once we establish a proper lla organization, we'll migrate all the themes to a dedicated lla-themes repository, similar to what you suggested.

For now we already have a simple way to pull and install themes because they're not included in the main binary for easy theme management

lla theme pull        # pull all builtin themes
lla theme install /path/to/theme.toml  # install custom themes
lla theme install /path/to/themes/     # or install from a directory

[azzamsa]

This would be great!
Thanks for putting a lot of effort for lla 🧁