Is your feature request related to a problem? Please describe.

Not having this information readily available, and having to go to all theme's repository to know this.

Describe the solution you'd like

I think having a last updated date somewhere would be useful to let people know if they want to use it, because otherwise maybe the theme will be outdated or will not work properly.

Additionally, maybe having something like "Photon compatible", "Proton compatible, and so on, since there some forks of Firefox that are not up to date in comparison or use other themes may be compatible with older versions.

Describe alternatives you've considered

N/A

Additional context

N/A

I was the owner of silentfox but didn't have to resources to maintain it so I deleted the repo. Now its just there with a non functioning link.

I find this https://github.com/1000ch/gulp-cwebp
It could be added to our workflow to automatically convert our images, with a 2º github action or in the one we already have

maybe we could make it run automatically when there are changes in the "theme.json" file.

the only inconvenient is that we must remember to include in the "theme.json" the url of the image already with the ".webp". if I am not mistaken.

the image is the one above.
My theme is this: https://github.com/Godiesc/opera-gx
I searched the name of the image that the store has and is this: 18217146305253-e257fbc0-993b-4e79-a0b4-0c0e6c95228b.webp
Thanks.

I think it would be interesting to add some resources to the website to make it more complete. We could add them to the footer for example.

Resources:
https://github.com/Timvde/UserChrome-Tweaks
https://www.userchrome.org/
Tool to inspect the UI: https://developer.mozilla.org/en-US/docs/Tools/Browser_Toolbox

What do you think?

{
"title": "WaveFox",
"link": "https://github.com/QNetITQ/WaveFox",
"description": "Tabs with a unique shape",
"image": "https://github.com/QNetITQ/WaveFox/blob/main/Image.png"
}

{
"title": "CompactFox",
"link": "https://github.com/Tnings/CompactFox",
"description": "A simple theme that compacts a lot of the UI elements",
"image": "https://raw.githubusercontent.com/Tnings/CompactFox/main/Images/CompactFoxPreview.png"
}

A few things I am thinking after looking at the code.

1. I think it would be easier for developers and people who made themes to put them here with PUG to render the HTML5 code;
2. And to help optimizing and creating a better code, it would definitely be easier if it was made with npm, hence making easier scripts and live preview feature.
3. Animations, they are heavy and take some time to load, maybe removing them or changing their load times.

I'd be happy to help with everything, I am just going to include a Pull request with some grammar corrections along this post, too.

With more and more themes being added to the list things get a little cluttered.

I've been thinking about maybe trying to implement a search system. Since the themes are stored in a json object it shouldn't be too hard to add a .filter function to limit the results. This would require to add a new field fo keywords, and some tagging of the already listed themes.
I do think that it's worth the effort tho because it makes it a easier for the user to find what they're looking for.

With this feature in place it could also be beneficial to limit the amount of results that are displayed upon the first page visit to the recently added X amount of themes instead of listing everything by default as this reducdes page loading time by a lot.

Edit: Instead of taking the latest themes to display on the front page we could also (finally) do a random sort as suggested in #30 .. :D

I'd be willing to tinker around with this and implement the features but that's something I can't just decide on my own. So feel free to tell me your thoughts and ideas. ^—^

Is your feature request related to a problem? Please describe.
The cumbersome installation steps are one of the reasons that prevent people from using userChrome.css.
It would be helpful to have an theme installer.

Describe the solution you'd like
I made a installer prototype, currently it only works on Linux, but it is easy to make it support other platforms.

If you are interested, I can move the repo to FirefoxCSS-Store and improve it together.

Describe alternatives you've considered
N/A

Additional context
N/A

https://github.com/hornster02/Firefox-Three-Rows-Simple-Compact-Clean-CSS

images
18kB size
https://github.com/hornster02/Firefox-Three-Rows-Simple-Compact-Clean-CSS/raw/main/Three_Rows.webp
or
26kB size
https://github.com/hornster02/Firefox-Three-Rows-Simple-Compact-Clean-CSS/raw/main/Three_Rows.png

Thanks.

{
    "title": "Bali10050's theme",
    "link": "https://github.com/Bali10050/FirefoxCSS",
    "description": "A minimal looking oneliner, with modular code for easy editing",
    "image": "assets/img/themes/Bali10050sPreview.webp",
    "tags": [ "Bali10050", "oneline", "light", "dark", "linux", "windows", "rounded", "proton", "responsive", "minimalistic" ]
  }

https://raw.githubusercontent.com/FirefoxCSS-Store/FirefoxCSS-Store.github.io/main/images/themes/Bali10050sPreview.webp

GitHub Pages offers to serve from the /docs folder instead of the root directory.
I'd suggest that we switch to that to declutter the repository a little bit.

What are your thoughts on this? c:

I'm not sure if you accept requests to add themes from people that don't maintain them. But if you do here are two I think should be added.

https://github.com/rafaelmardojai/firefox-gnome-theme
https://github.com/BloodyHell619/Firefox-Theme-DarkMatter

Is your feature request related to a problem? Please describe.

Right now it is necessary to go to each theme's repository in order to preview them.

Describe the solution you'd like

If one could click the images to expand them and be able to appreciate how the theme looks without leaving the store, it would be a more comfortable experience in order to decide which one to choose.

Describe alternatives you've considered

N/A.

Additional context

The link to the repository could be contained within the theme's name, or in a GitHub, Gitlab, etc logo inside the drop down menu.

I've created a feature branch for markdown in Pug support. This way site content (like the disclaimer) would also get displayed nicely when viewed on GitHub – well, and it's easier to write for people that aren't used to pug.

I really like the idea and it doesn't really add any extra bloat. This could come in quite handy when we decide that we maybe want to display more content on the site. Things that I have in mind would be the generic tutorial or the theme submission guideline. c:

What are your thoughts on this?

Background
Firefox has a process known as "Experiments" that are used to create new webextention apis. Depending on the popularity and quality of these APIs, they get uplifted to stable Firefox. For example, the top-sites api started as an experiment and has been uplifted into Firefox.

Is your feature request related to a problem? Please describe.
Currently, installing userchrome customizations is a finicky process that involves messing around in the Firefox.

Describe the solution you'd like
Firefox has an experimental theming option available to webextentions called theme_experiment, which allows the loading of custom css files as part of a theme. It would be more convenient for users to install a theme than to place files in their file system.

Describe alternatives you've considered
#69 tries to solve the same issue, however, its solution would require the installation of third party software, increasing the barrier to entry.

Additional context
Browser support is a bit iffy for this type of addon. Waterfox works flawlessly, so long as you move out of their compact UI mode. Firefox developer edition (and, in theory, firefox nightly) work so long as you disable xpinstall.signatures.required and enable extensions.experiments.enabled. Firefox Beta and Stable do not work at all.

Currently, the only addon that supports this form of theme is my fork of cascade I used for testing this. If you want to test it out, use one of the browsers above and install the XPI from this release.

For more information about packaging themes, see cascadefox/cascade#23

Update logo preview

"image": "https://github.com/QNetITQ/WaveFox/blob/main/New%20preview%20.png"

Mozilla Thunderbird also supports customization through the userchrome.css file. It would be very useful if the store had a separate section for Thunderbird.

While I really like the use of template literals, using insertAdjacentHTML in our main.js has one major flaw: We need to make sure that we sanatise the JSON data.

As long as we manually review and merge new themes this isn't a big deal. But if we decide to fully automate the process later on we have to keep that in mind to prevent unwanted JavaScript from getting invoked at runtime.

Please remove the theme from the theme repository

Fix this to...literally anything relevant? 😃

I hesitated to submit this since it's not a complete theme, but I feel like it's worthy to display in a CSS Store.

https://github.com/M1ch431/FirefoxW10ContextMenus

{
		"title": "FirefoxW10ContextMenus",
		"link": "https://github.com/M1ch431/FirefoxW10ContextMenus",
		"description": "Emulates the Windows 10 context menus in Firefox.",
		"image": "https://raw.githubusercontent.com/M1ch431/FirefoxW10ContextMenus/master/Preview.png"
}

Describe the bug
You need to refresh the website to see the changes after re-sorting it by the most recent topics.

To Reproduce
Steps to reproduce the behavior:

1. Click the sort button to switch between sort types.
2. When you switch to random, you instantly see the new sort, and the same with the oldest one.
3. But when you click to switch back to the "latest" sort, you see no change if you do not refresh the website.

Expected behavior
When you come back to "latest" sort, you should see the changes like the others sorting modes

By the way, thank you very much for the new feature 😁

Describe the bug
The style Monterrey Fox no page goes to a 404 error page

To Reproduce
Steps to reproduce the behavior:

1. You just click on Monterrey Fox

Expected behavior
The page should load

Desktop (please complete the following information):

• OS: [e.g. Linux distro: Garuda Linux (Arch_based)
• Firefox, Firefox Nightly, Firefox-Developer-Editin, FireDragon (Firefox fork)
• Version [e.g. 22] 90.0.2

In a screen of 798x744 there's no options to download, nor preview. Going to give a look and update here.

they could be sorted randomly on the user's device or every time we add a new theme.
Can we do that?

The more I think about it, the more I want to change the company to something different. It just doesn't really sound all that fitting. Maybe something like the author would be better?

The GitHub action to check theme.json need to be updated. It fails now because the "tag" parameter was not contemplated

Is your feature request related to a problem? Please describe.
I want to create a NixOS flake that will contain all the themes from themes.json. For that, I need a 100% stable way to get all the CSS that need to be imported and all the Firefox settings that should be changed in order to use the theme.

Describe the solution you'd like
Add those descriptors to the themes.json file so they can be easily parsed so then I can create a home-manager module and make a PR to home-manager repo and/or to this repository in form of flake.nix (many github repos already include a way to easily use them on NixOS, ex. Hyprland (Wayland window manager) - https://github.com/hyprwm/Hyprland/blob/main/flake.nix)

Additional context
We can already easily configure Firefox declaratively on NixOS.

So I can write a module that will provide NixOS users with something like:

programs.firefox.profiles.<name>.cssStoreTheming = {
  enable = true;
  theme = pkgs.firefoxCssStore.themes.essense;
}

I thew together a really simple Actions workflow to build the project from source on demand. This means that for now this has to be triggered manually.