Basic link to Documentation #37

Merged
hw merged 1 commits from :docs-link into master 1 year ago

This PR links to Codeberg Documentation from the title bar. (See Codeberg/Documentation#7)

This PR links to Codeberg Documentation from the title bar. (See Codeberg/Documentation#7)
Poster

If you prefer, I can implement the solution suggested in my comment there and link to https://docs.codeberg.org/improving-codeberg

If you prefer, I can implement the solution suggested in [my comment there](https://codeberg.org/Codeberg/Documentation/issues/7#issuecomment-77864) and link to https://docs.codeberg.org/improving-codeberg
hw commented 1 year ago
Owner

merging, but it is getting kind of crowded, not? ;)

merging, but it is getting kind of crowded, not? ;)
hw merged commit 5140f719f3 into master 1 year ago
hw deleted branch docs-link 1 year ago
Poster

Yes, you're right. Should I implement the solution suggested above and write a PR (Combining "Join" and "Donate" into "Support Codeberg e.V." with a link to https://docs.codeberg.org/improving-codeberg)?

Yes, you're right. Should I implement the solution suggested above and write a PR (Combining "Join" and "Donate" into "Support Codeberg e.V." with a link to https://docs.codeberg.org/improving-codeberg)?
hw commented 1 year ago
Owner

Considering that funding is kind of fundamental, there should be as little friction as possible...

Considering that funding is kind of fundamental, there should be as little friction as possible...
hw commented 1 year ago
Owner

What do you think about a second (stacked) banner? (sketch attached)

What do you think about a second (stacked) banner? (sketch attached)
Poster

What do you think about a second (stacked) banner? (sketch attached)

In my opinion it would probably be better to have Codeberg-related links in the footer of the page and to have the main menu focus on the daily used functions of Gitea. Maybe we could even redesign the footer to be a little bit more prominent. As an example, Github's design is very nice in that regard.

The best approach in my opinion is still Moritz's extended Menu which he presented in his PR to build-deploy-gitea. As this is a rather medium-to-long-term solution, for the short term we might consider to move at least some of the Codeberg-related links to the footer.

The links could even remain there as a duplication for those who intuitively look for such links in the footer, rather than in the main menu (which would include me for example 😄).

> What do you think about a second (stacked) banner? (sketch attached) In my opinion it would probably be better to have Codeberg-related links in the footer of the page and to have the main menu focus on the daily used functions of Gitea. Maybe we could even redesign the footer to be a little bit more prominent. As an example, Github's design is very nice in that regard. The best approach in my opinion is still Moritz's extended Menu which he presented in his PR to build-deploy-gitea. As this is a rather medium-to-long-term solution, for the short term we might consider to move at least some of the Codeberg-related links to the footer. The links could even remain there as a duplication for those who intuitively look for such links in the footer, rather than in the main menu (which would include me for example :smile:).
Poster

How about we keep Donate, Documentation and Codeberg Issues in the header, separate them optically a little from the Gitea links (i.e. by adding a margin-left) and add a footer that collects all important Codeberg-related links in one place, duplicating the links to Donate, Documentation and Issues?

I could write a PR for that, if you want :)

How about we keep Donate, Documentation and Codeberg Issues in the header, separate them optically a little from the Gitea links (i.e. by adding a margin-left) and add a footer that collects all important Codeberg-related links in one place, duplicating the links to Donate, Documentation and Issues? I could write a PR for that, if you want :)
Poster

Here's a mockup of how I would imagine the footer.

I'm not sure yet where to put the language selector in this design though.

Maybe centered in the very bottom, under the small print?

Or put it as a Globe icon in the main menu? Or in the user menu that opens when clicking on the avatar?

Here's a mockup of how I would imagine the footer. I'm not sure yet where to put the language selector in this design though. Maybe centered in the very bottom, under the small print? Or put it as a Globe icon in the main menu? Or in the user menu that opens when clicking on the avatar?
hw commented 1 year ago
Owner

Maybe we could even redesign the footer to be a little bit more prominent. As an example, Github’s design is very nice in that regard.

How visible is the footer for an active dashboard or typical project page with lots of content? Wikipedia's campaign banners seem a closer relative here?

Also keep in mind gh's dashboard ads/feature banners are huge, have historically been often flashy with graphics, and always center of the screen, or right in the navigation panel.

> Maybe we could even redesign the footer to be a little bit more prominent. As an example, Github’s design is very nice in that regard. How visible is the footer for an active dashboard or typical project page with lots of content? Wikipedia's campaign banners seem a closer relative here? Also keep in mind gh's dashboard ads/feature banners are huge, have historically been often flashy with graphics, and always center of the screen, or right in the navigation panel.
hw commented 1 year ago
Owner

(fwiw as this is a closed PR, do we want to move this discussion into an open issue so that it becomes more visible?)

(fwiw as this is a closed PR, do we want to move this discussion into an open issue so that it becomes more visible?)
Poster

How visible is the footer [...]

I only meant a little more prominent. Like in the Mockup above.

The donation link would remain in the main menu.

do we want to move this discussion into an open issue so that it becomes more visible?

If the approach as shown in the Mockup above is not off the table, I would create a PR the next couple of days and we can discuss there. Would that be okay?

> How visible is the footer [...] I only meant *a little* more prominent. Like in the Mockup above. The donation link would remain in the main menu. > do we want to move this discussion into an open issue so that it becomes more visible? If the approach as shown in the Mockup above is not off the table, I would create a PR the next couple of days and we can discuss there. Would that be okay?
hw commented 1 year ago
Owner

sounds great! We can also deploy to -test right away for best visibility

sounds great! We can also deploy to -test right away for best visibility
hw commented 1 year ago
Owner

The donation link would remain in the main menu.

just one thought: if we go for wikipedia-style goal-based (but much larger) campaign banners, during off-season these could be very small ... otoh some campaign lead would be needed...

> The donation link would remain in the main menu. just one thought: if we go for wikipedia-style goal-based (but much larger) campaign banners, during off-season these could be very small ... otoh some campaign lead would be needed...
Poster

Let's talk about donation banners and campaigning in a separate issue, to not mix up things.

Let's talk about donation banners and campaigning in a separate issue, to not mix up things.
Poster

Mockup is now at Codeberg/Design#23 - I'm currently unable to make a PR here, mainly due to #41.

Mockup is now at Codeberg/Design#23 - ~~I'm currently unable to make a PR here, mainly due to #41.~~
The pull request has been merged as 5140f719f3.
Sign in to join this conversation.
Loading…
There is no content yet.