Hello,
I've created a new skin for opnsense.
I hope you like it. Many thanks to everyone for all the hard work you put into opnsense, and of course to all the skin creators for their great themes. I hope you'll forgive me for simply adapting your original files to my needs. The skin was inspired by Adguard, which is why I also have to thank the creators of this software.
Here is the link for the zip file: https://1drv.ms/u/c/00eaa4d745db4d24/EX5r8keHTelAohibr3SKnDMBN6bt4QFsAfB2yQ1ckvAZaQ?e=2YW78Y
You will find two screenshots attached.
Please consider submitting it as a plugin like the other themes.
I would do that but I don' t know how to do it. I think this is something that the Team members have to decide, or am I wrong?
Thanks you for this theme. I have tried several dark themes for OPNsense but they all made one page or the other unreadable. This theme is very good. All the pages are readable.
Thank you so much. I am happy that you Like it. Please tell me when you'll find problems.
Here is an example PR of the last theme that was merged.
https://github.com/opnsense/plugins/pull/4189
Okay, I will try that if there is interest, although it seems a little bit complicated for me. In this context, I have a quick question. I have used the skins Vicuna, Cicada, etc. as a basis. I noticed that there are completely different SCSS files in the folder assets/stylesheets than, for example, in the standard skin opnsense-dark (with the exception of the 'bootstrap' folder). I have never changed anything in these files and even deleted them for testing, without discovering any negative impact. Are these files needed, and if so, what are they used for?
The scss files are used with a tool called sass to build the css files.
So the themes to not directly edit them, they use the scss files and then build all styles.
https://sass-lang.com/
Okay, thank you for clearing this. So I don't have to offer them to the users of the theme.
I've tried to do make a pull request but it failed with the message that I am no collaborator. Can you please help me a little bit more?
You create a fork of the plugin repository. In it you create a branch, e.g. "my-theme". In your local git client you change to this "my-theme" branch, e.g. via "git checkout my-theme".
Then you push your changes into that branch after you are done.
Then in the github GUI, you can choose "pull request", it will be an own header in your forked repository because you recently pushed changes to a branch.
Then it will work.
Quote from: Schnuffel2008 on September 02, 2025, 12:03:46 PMI've tried to do make a pull request but it failed with the message that I am no collaborator. Can you please help me a little bit more?
You should be able to do a PR, everyone is. You cannot do a commit.
Go to your fork, press the pull request button, change the source and target appropriately and it should work.
Hmm,
don't know what I am doing wrong. But it still isn't working
I explained it above. You fork plugins to your /own/ repository, and create the PR from there.
https://github.com/opnsense/plugins
--> Press "Fork"
Quote from: Schnuffel2008 on September 02, 2025, 02:37:54 PMHmm,
don't know what I am doing wrong. But it still isn't working
You need to change your source to your own repository, now it's the 25.7 branch of the main repository.
Hi,
sorry I have not seen your E-Mail with the explanations Monviech. I've tried my best now and hope I've finally made it. As I said it is a little bit complicate for someone that nether used github.
Quote from: Schnuffel2008 on September 02, 2025, 04:28:13 PMHi,
sorry I have not seen your E-Mail with the explanations Monviech. I've tried my best now and hope I've finally made it. As I said it is a little bit complicate for someone that nether used github.
Unfortunately no, what is your github username?
Sorry for the problems. It ist the same Name Schnuffel2008
Now it should be available I think.
Quote from: Schnuffel2008 on September 02, 2025, 04:42:30 PMSorry for the problems. It ist the same Name Schnuffel2008
Don't worry about it; these are the settings you need to choose.
Go here and choose "New pull request": https://github.com/opnsense/plugins/pulls
Thank you so much for your help. I promise to be less difficult to handle in the future.☺️
Hi,
I have a much better idea for the skin and that will change the name of the skin.
So I think it will be the best to close the PR on github so nobody has to review and check it, and I will reopen it in a few days or weeks when it is ready.
Sorry for the confusion.
Just close it yourself. Its okay.
I closed the PR on github and change this thread to close now.
C.U.
Quote from: Schnuffel2008 on September 01, 2025, 04:39:07 PMI would do that but I don' t know how to do it. I think this is something that the Team members have to decide, or am I wrong?
You can copy in a full theme to a directory on the OS, then just select it from web gui. I think the plugin route is a way to get it installed completely from web gui as a community item, but that's not the only way.
See post #5 https://forum.opnsense.org/index.php?topic=48566.0
Quote from: BrandyWine on September 04, 2025, 01:13:51 AMQuote from: Schnuffel2008 on September 01, 2025, 04:39:07 PMI would do that but I don' t know how to do it. I think this is something that the Team members have to decide, or am I wrong?
You can copy in a full theme to a directory on the OS, then just select it from web gui. I think the plugin route is a way to get it installed completely from web gui as a community item, but that's not the only way.
See post #5 https://forum.opnsense.org/index.php?topic=48566.0
Sure but if you want anyone to use it... It should be a plugin. The amount of people that will search the forum for theme files is not there.
I will do it as s plugin. This is the much better solution. But at the moment I make some extensions for it. Therefore it makes no sense to put work to the team and then change the theme and in peculiar the theme name in a few days again. Just give me some days.
Quote from: Schnuffel2008 on September 04, 2025, 08:53:29 AMI will do it as s plugin. This is the much better solution. But at the moment I make some extensions for it. Therefore it makes no sense to put work to the team and then change the theme and in peculiar the theme name in a few days again. Just give me some days.
As much as you need!
Hi,
I've finished the theme today, changed the name to flexcolor, loaded it up to GitHub, and made a new pull request. Is this all I have to do for having it as a new theme in one of the next Updates?