[Howto] - Change/Update file structure of the tutorials #866
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
Fixed
forgejo
fun_project
Goal 2024
Goal 2025
help wanted
high impact
housekeeping
Howto
infra
In progress
🤔️ Investigate
Invoice Ninja
ios
jitsi
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 Issues
spam-protection
Staging Server
sysadmin
Themes
TOR
upstream issue
Website
windows
wontfix
xmpp
Yearly Report
No milestone
No project
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/Disroot-Project#866
Loading…
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?
File structure in Grav is very important as it determines the navigation on the site. Depending on the proposed changes in the theme we should reorganize the file structure. The idea here is to try and find a universal file structure that could apply to all services current and future,.
now that general theme is pushed to staging, its time to work on the structure.
As requested I will deploy instance for @fede and also work on the pages structure. Once we decide on the structure we push it to staging.
Created needed PRs. Awaiting approval and merge.
Below is my proposal for file structure for new howto website. I did some modifications to the structure. I tried to streamline it and create as much unified structure as possible to handle all the services and be easy to add more tutorials for other services in the future (eg. Apps and clients section). Please have a look below. I removed some of the old clients (eg. sailfishos). I used the same name for services as we use on the website so it's easy to find things for those who are less techy. I think we should also change the order of services on the website as well and try to put most used/important apps first.
AccountManagement
Email
Cloud
XMPP Chat
Akkoma
D-Scribe
Cryptpad
Upload
Private Bin
Pads
Mumble
Calls
I still think there are a lot of clicks. For example, to get to fairemail, you'll have to click on email, then email clients, then android, then Fairemail.
Perhaps we could remove one step by removing the OS section, and add the os in the title or add a logo next to it, so for example:
etc.
Yeah we could make it simplier.
I wonder if it will be universal across all other services. I think it wouldnt work on nextcloud specially when you have all the extra apps etc. but perhaps it's exeption and so should be treated that way. One thing to consider though is unlike the current theme, the new one will have a sidebar with the structure out there so I think we could make it so when you click on clients it will open the entire menu you dont have to click individually but could have direct access.
But we should test the clients part on staging to see what works best.
I llike meaz's proposal. When you click on 'clients' you could have an overview page, divided into type of clients (webmail/android/ios/desktop) but in the menu you can just list the clients themsleves, making the structure a bit simpler.
Shall we then implement it next month?