-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Top bar 2.0 #78
Comments
I decided to not implement dropdowns and stuff yet. This stuff needs some styling for sure.
No one really liked the two-line approach, so it seems, but it will go to 1.3 nevertheless. I may try to attempt to try to implement something else later, perhaps. |
With localization added in 1.5, the top bar 2.0 should support multiple languages too |
...And that would mean wiki-local l18n support. Oh boy! |
Once #115 is done and we have the word Profile in our vocabulary, we can replace the current user's name in the topbar with the word Profile. That would fix the overflow problem with long names (Yogurt has complained about that once or twice). Also, once #115 is done, there is no need to have the admin panel link in the top bar. We will just remove it. Next, we can have URL Then we can think of a better layout. |
No, we should not remove the username from the header. It's important for the context. |
Why not? What context? Isn't the wiki name and that emoji in the title not enough for the context? |
That's not it. I like having my username displayed in the header at a glance, because I have different usernames across different wikis. |
Fumu fumu |
I said,
Now I say no “perhaps”. The special hypha has to go. Also considering the cool navigation inspired by Betula. You know, horizontal scrolling on phones and whatnot. |
No one likes the current top bar.
Let's address what is wrong with it now:
What I want top bar 2.0 to have:
Two-line approach
Here's what I though of. We have two lines:
Link to the home hypha, search bar, user links. I'm sure there is a way to fit them all on any computer screen.
Navigation links. More advanced than now, dropdowns supported maybe.
The dropdowns should work without JS. We have the tag for that:
<details>
.On mobile devices, it may look like that (top to bottom):
Default navigation links
If we take this approach, we will have much more space for the navigation links. What do we put there? Not much, I guess.
Configuration
The current approach with the special hypha shall be demolished and forgotten. Perhaps.
The sidebar approach
What if we take all the navigation links and put them into a sidebar to the left of the hypha section?
Well, it is possible, but I wanted to put TOC there...
The text was updated successfully, but these errors were encountered: