[Howto] - Draft new theme concept #865
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/Disroot-Project#865
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?
We should start by drafting new theme idea before we move on to the file structure as this will greatly impact it.
The draft should include:
Perferably this should be done in a form of working concept so that it can be then tested and we could work on file structure even when the theme isn't complete yet.
@fede @antilopa could you remind me what were the themes already existing that you were thinking to perhaps use as a start?
It's called Learn2 (Git sync) and it can be found here:
https://getgrav.org/downloads/themes
It also has a skeleton here:
https://getgrav.org/downloads/skeletons
@meaz we were specifically referring to the learn2 theme but should check what else is out there. Here is a demo of learn2+git-sync:
https://demo.hibbittsdesign.org/grav-learn2-git-sync/
Nice. I don't think we need to go into a complicate change. At first, I guess changing colors only might be enough. The most important thing imo is the files structure: it needs to be super easy.
I agree.
Something like this ?
Looks nice.