[Howto] - Draft new theme concept #865
Labels
No labels
🔥
🦾 1
🦾 2
🦾 3
🦾 4
🦾 5
🦾 6
administration
Akkoma
Android
Bare metal
bug
Communication
Community
Cryptpad
🙌 Decission needed
Discussion
Documentation
duplicate
enhancement
etherpad
Feature request
Feedback
finances
forgejo
Free to take
Funding
fun_project
help wanted
high impact
housekeeping
Howto
infra
In progress
🤔️ Investigate
ios
lacre
Lacre Test
ldap
Lemmy
LibreTranslate
low impact
low prio
Lufi
macos
Mail
Merch
monitoring
movim
needs_refine
New Auth
Nextcloud
nice to have
on hold
proposal
PR ready
question
Ready
refined
Roundcube
searX
spam-protection
Staging Server
sysadmin
Themes
TOR
upstream issue
Website
windows
WIP
wontfix
xmpp
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…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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.
@meaz great start. I think you could push this to git so @antilopa could pick this one up to finalize it. What we should focus on in the meantime, is the file structure to see what will fit best to the theme to make it easy readable, at the same time not cluttered. Shall we pull #866 to the milestone?
I didn't do any change locally, just tested with Firefox inspector directly :)
ahhh. ok. I am -preparing grav role to deploy howto and disroot website on staging server, but wanted to make it cool and I over complicated stuff. Hope to fix it or otherwise I revert to less good but working solution. Once deployed, we could setup learn2 fork and then work on both the theme as well as setup/update file structure. So my proposal is: Wait until staging howto is set before we proceed further with stuff.
New role is done and a WIP state of the website is now running on staging server pulling staging branches every three hours (we could change it if needed). This means @antilopa you can start working on the theme too :) I will move this to June. I will have to sit with your @antilopa to workout proper workflow so it's easy for you to push your work from your dev server for the rest of the team to give feedback on staging. Looks like creative June/July for you.