Codeberg/Community
55
329
Fork
You've already forked Community
12

Footer: Adjust large section headers #1605

Open
opened 2024年07月08日 18:50:47 +02:00 by jidanni · 7 comments

Comment

At the bottom of this issue, see the lines

Codeberg
Documentation
Community Issues
Landing Page

Well, the first line and logo should be hyperlinked to something.

All there is is
<b>Codeberg</b>

### Comment At the bottom of this issue, see the lines Codeberg Documentation Community Issues Landing Page Well, the first line and logo should be hyperlinked to something. All there is is `<b>Codeberg</b>`

I mean, the Codeberg header could link to the Landing Page. not sure what Association and Service and Legal could link to.

I mean, the Codeberg header could link to the Landing Page. not sure what Association and Service and Legal could link to.
Author
Copy link

Yes, it should link to codeberg.org. I am real sorry about the other two though. I don't have any good ideas either.

Yes, it should link to codeberg.org. I am real sorry about the other two though. I don't have any good ideas either.

That's OK! Thank you for the feedback, we've been meaning to cut back on the length for a while now though.

That's OK! Thank you for the feedback, we've been meaning to cut back on the length for a while now though.

@fnetX Do you think we could remove the headers entirely to save space? The links are still grouped together and essentially categorized.

@fnetX Do you think we could remove the headers entirely to save space? The links are still grouped together and essentially categorized.
Owner
Copy link

The headers are relevant for quickly finding the category you are looking for. Headings are never leading somewhere, I don't understand the motivation for this. Turning some of them into links leads to inconsistency, also a bad idea.
Removing them means that users need to scan each category to determine if it contains what's relevant to them.

If you want to save space, we can adjust the font size. I don't know why it's that large, but there is likely a reason for this. It's also unintended that the "Blog, Mastodon ..." line has so much space to the bottom. It could be on one line with the language switcher and overall saving a little.

Also keep in mind that the footer was a rather long design process (see Codeberg/Design#23, and there have been a lot of actions in a Matrix chat back when it was implemented). We can continue improving it, but I don't think single opinions should make us fiddle with the footer back and forth, because the months-long design process where we evaluated all ins and outs has a higher weight for me.

The headers are relevant for quickly finding the category you are looking for. Headings are never leading somewhere, I don't understand the motivation for this. Turning *some* of them into links leads to inconsistency, also a bad idea. Removing them means that users need to scan each category to determine if it contains what's relevant to them. If you want to save space, we can adjust the font size. I don't know why it's that large, but there is likely a reason for this. It's also unintended that the "Blog, Mastodon ..." line has so much space to the bottom. It could be on one line with the language switcher and overall saving a little. Also keep in mind that the footer was a rather long design process (see https://codeberg.org/Codeberg/Design/issues/23, and there have been a lot of actions in a Matrix chat back when it was implemented). We can continue improving it, but I don't think single opinions should make us fiddle with the footer back and forth, because the months-long design process where we evaluated all ins and outs has a higher weight for me.

OK, let's adjust the scope of this issue.

OK, let's adjust the scope of this issue.
n0toose changed title from (削除) Hyperlink link to Codeberg (削除ここまで) to Footer: Adjust large section headers 2024年07月09日 17:05:58 +02:00

If you want to save space, we can adjust the font size. I don't know why it's that large, but there is likely a reason for this.

Instead of closing this issue, I changed the title of this issue to make it more discoverable in the future because this seems to be like the only actionable element here in its current form.

We do not plan to do anything at the moment, but we might circle back to this at a later point.

> If you want to save space, we can adjust the font size. I don't know why it's that large, but there is likely a reason for this. Instead of closing this issue, I changed the title of this issue to make it more discoverable in the future because this seems to be like the only actionable element here in its current form. We do not plan to do anything at the moment, but we might circle back to this at a later point.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#1605
Reference in a new issue
Codeberg/Community
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?