[Beet Themes] - Seperate all custom changes in themes from upstream #816
Labels
No Label
administration
Akkoma
Android
Bare metal
bug
Communication
Community
Cryptpad
Discussion
Documentation
duplicate
enhancement
etherpad
Feature request
Feedback
finances
Fixed
forgejo
fun_project
Goal 2024
help wanted
Howto
🤔️ Investigate
ios
jitsi
lacre
Lacre Test
ldap
Lemmy
LibreTranslate
low prio
Lufi
macos
Mail
Merch
monitoring
movim
needs_refine
New Auth
Nextcloud
nice to have
on hold
proposal
question
Ready
refined
Roundcube
searX
spam-protection
Staging Server
Themes
TOR
Urgent!
Website
windows
wontfix
xmpp
Yearly Report
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/Disroot-Project#816
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
To be able to maintain the forks in easy way we should make sure all custom changes in themes are done on separate files so that no upstream data is changed as it will make it harder to keep track of changes. This approach will create an easy and simple setting for additional future flavors of themes.
List of current custom themes on disroot:
Searxng theme
We don't have the exact same structure as on upstream.
In static:
disroot.less
filedefinitions.less
and instyle.less
. I don't think we could do otherwise.grunt
to get the css generated.In template:
simple
bybeetroot
base.html
andindex.html
for dashboardSo at the moment here is what I do when I need to update:
git clone searnx repo
static/themes/simple
folder of the searxng repo and thebeetroot_static
of our theme repotemplates/simple
folder of the searxng repo and the `beetroot_template of our theme repo.I don't have a smart way to that quicker. Perhaps using a script? So we clone the repo, apply the script that would implement this little changes here and there. Then we just have to copy the files over in our repo.
But that's trickier for the
base.html
andindex.html
files.Forgejo
We have only three files to check so that's pretty easy.
theme-beetroot-auto.css
: we change change the wordforgejo
bybeetroot
@import "disroot.css";
on top of each of those files so that we don't edit them. But that's not that simple as we comment out some of the css rules in there...--disroot
color vars to be set like on any other theme (I mean the exact same colors)Roundcube
What I do it that I download release and check diff with
skins/elastic/
.The easy part is that we have the same structure as upstream.
Images
favicon.ico
andlogo.svg
are modifieddisroot-root
andlogo.png
are addedStyles
We have specific disroot files:
_colors.less
_dark.less
_darkc.less
_styles.less
_variables.less
In those files we don't only have disroot colors, we also change some rules.
We need to run
lessc
command also onembed.css
,print.css
andstyles.css
files to get themin.css
versionTemplates
menu.html
from svg to png on a logologin.html
General
meta.json
watermark.html
Lufi
What I do it that I download release and check diff with
themes/default/
.The easy part is that we have the same structure as upstream.
CSS
lufi.css
andmaterialize.css
but as we didn't explicit noted what is Disroot changes, I don't even know if differences are because of our changes, or because it was done by dev!materialize.css
IMG
We use our own logo
Templates
We remove a line in
about.html.ep
coz we don't log IPs.Other
README.md
is on own file (not in upstream repo)Makefile
on our repo, but not in upstream repo so I guess we cold remove this.@Disroot/Owners as you can see, I've tried to sum up what we change for already existing theme. Now, you can check and see if you can come with a smart solution...
@meaz thanks or the above. it makes it easy to work. I'm on it. i will try to push some solution.