#140 Could you please consider to separate the Codeberg items in the top menu from my items?

Open
opened 4 weeks ago by hunger · 7 comments
hunger commented 4 weeks ago

The web site has a top bar with Dashboard, Issues, Pull Requests, ... etc. which belong to my user when logged in.

There are also codeberg-related items in that top bar like Codeberg Issues, Blog, etc.

I do appreciate those being there (otherwise I would not have found the place to report this so fast;-), but can those get more clearly separated from my items?

E.g. add some spacing before the codeberg items or make them visually distinct?

The web site has a top bar with `Dashboard`, `Issues`, `Pull Requests`, ... etc. which belong to my user when logged in. There are also codeberg-related items in that top bar like `Codeberg Issues`, `Blog`, etc. I do appreciate those being there (otherwise I would not have found the place to report this so fast;-), but can those get more clearly separated from my items? E.g. add some spacing before the codeberg items or make them visually distinct?
hw commented 4 weeks ago
Owner

Pull request welcome! The relevant code is in https://codeberg.org/codeberg/build-deploy-gitea/

Pull request welcome! The relevant code is in https://codeberg.org/codeberg/build-deploy-gitea/
ashimokawa commented 4 weeks ago
Owner

@hunger I deployed that on codeberg-test.org, you can see it there

Two problems I see:

  • Looks a bit odd on mobile
  • People already complained that the top bar takes too much space for their setup
@hunger I deployed that on codeberg-test.org, you can see it there Two problems I see: * Looks a bit odd on mobile * People already complained that the top bar takes too much space for their setup
hunger commented 3 weeks ago
Poster

I guess this needs more CSS then, at which point I am unfortunately out.

Maybe we could merge all the Codeberg items into one “About” and only link to that (with an nice separator in front). That would reduce the need for horizontal space quite a bit.

I guess this needs more CSS then, at which point I am unfortunately out. Maybe we could merge all the Codeberg items into one "About" and only link to that (with an nice separator in front). That would reduce the need for horizontal space quite a bit.

-- spam deleted --

-- spam deleted --
davidak commented 2 weeks ago
Collaborator

Yes, it would be one solution to have just “About” there or just the Logo which links to the homepage which should have all information.

The links can also be added to the footer.

It works for GitHub, so why shouldn't it work for us? They are successfull because their UI is not cluttered with unneeded information.

Yes, it would be one solution to have just "About" there or just the Logo which links to the homepage which should have all information. The links can also be added to the footer. It works for GitHub, so why shouldn't it work for us? They are successfull because their UI is not cluttered with unneeded information.
hw commented 1 week ago
Owner

:) PR welcome!

:) PR welcome!
fnetX commented 1 week ago

I guess I won't find the time to check for that, but you could either create some flexible div containers that center the codeberg items in the middle of the navbar or, probably a better approach, move the codeberg related things into an dropdown still allowing a quick access to these items.

I'll set up an reminder for me to look back into that if no one else finds the time to do so ... but I'd really appreciate someone w/ more experience looking at this.

I guess I won't find the time to check for that, but you could either create some flexible div containers that center the codeberg items in the middle of the navbar or, probably a better approach, move the codeberg related things into an dropdown still allowing a quick access to these items. I'll set up an reminder for me to look back into that if no one else finds the time to do so ... but I'd really appreciate someone w/ more experience looking at this.
Sign in to join this conversation.
No Milestone
No Assignees
6 Participants
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
Cancel
Save
There is no content yet.