New theme dark-blueorange

[Schnuffel2008]

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.

[sopex8260]

Please consider submitting it as a plugin like the other themes.

[Schnuffel2008]

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?

[AG_2023]

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.

[Schnuffel2008]

Thank you so much. I am happy that you Like it. Please tell me when you'll find problems.

[Monviech (Cedrik)]

Here is an example PR of the last theme that was merged.

https://github.com/opnsense/plugins/pull/4189

[Schnuffel2008]

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?

[Monviech (Cedrik)]

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/

[Schnuffel2008]

Okay, thank you for clearing this. So I don't have to offer them to the users of the theme.

[Schnuffel2008]

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?

[Monviech (Cedrik)]

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.

[sopex8260]

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 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.

[Schnuffel2008]

Hmm,

don't know what I am doing wrong. But it still isn't working

[Monviech (Cedrik)]

I explained it above. You fork plugins to your /own/ repository, and create the PR from there.

https://github.com/opnsense/plugins

--> Press "Fork"

[sopex8260]

Hmm,

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.