Codeberg/Community
54
325
Fork
You've already forked Community
12

About page for Codeberg.org #75

Closed
opened 2019年08月04日 06:04:01 +02:00 by strypey · 10 comments

There is currently nothing at codeberg.org/about. It would great to have a page there that sums up the project in a nutshell, briefly explaining its mission and organizational structure, and linking to the various pages that may be important to prospective users (Terms of Use, Privacy Policy etc).

For example, until I created an account and started digging around in your repos, I was still a bit confused about whether Codeberg was an instance of software primarily developed by another group (like NotaBug.org), or an instance of self-developed software (like GitLab.com). From what I can tell, it's more like NotaBug, except using Gitea instead of Gogs. This is the sort of thing an about page could clarify for the curious.

There is currently nothing at codeberg.org/about. It would great to have a page there that sums up the project in a nutshell, briefly explaining its mission and organizational structure, and linking to the various pages that may be important to prospective users (Terms of Use, Privacy Policy etc). For example, until I created an account and started digging around in your repos, I was still a bit confused about whether Codeberg was an instance of software primarily developed by another group (like NotaBug.org), or an instance of self-developed software (like GitLab.com). From what I can tell, it's more like NotaBug, except using Gitea instead of Gogs. This is the sort of thing an about page could clarify for the curious.

Related: #33

Related: #33
Member
Copy link

@strypey : that's good feedback, thank you. If you like, you might check out https://codeberg.org/Codeberg/build-deploy-gitea/, and help improving content! Static pages can be added in folder etc/gitea/public/, the welcome page (not logged in) is in etc/gitea/templates/home.tmpl.

@strypey : that's good feedback, thank you. If you like, you might check out https://codeberg.org/Codeberg/build-deploy-gitea/, and help improving content! Static pages can be added in folder etc/gitea/public/, the welcome page (not logged in) is in etc/gitea/templates/home.tmpl.

I realize this issue is a bit old, and that I don't know what has been done since then. As a newcomer to Codeberg I just wanted to add a suggestion: If not logged in, the main page https://codeberg.org shows a nice page with a big logo and a few paragraphs ("An Unprecedented Revolution", ..., "Our Mission"). This page could be used as /about for a start. I had this idea because this page seems to be no longer accessible as soon as you are logged in.

I realize this issue is a bit old, and that I don't know what has been done since then. As a newcomer to Codeberg I just wanted to add a suggestion: If not logged in, the main page https://codeberg.org shows a nice page with a big logo and a few paragraphs ("An Unprecedented Revolution", ..., "Our Mission"). This page could be used as `/about` for a start. I had this idea because this page seems to be no longer accessible as soon as you are logged in.

@blipp

Yes, something like that.
I wanted a much simpler start page and then make the current the about page with maybe even more content.

on https://codeberg-test.org there is a simplified version of the start page.

@blipp Yes, something like that. I wanted a much simpler start page and then make the current the about page with maybe even more content. on https://codeberg-test.org there is a simplified version of the start page.

I just sent a new About page as a sample. Nice to meet you here @strypey and @hw.

I just sent a new [About](https://codeberg.org/Codeberg/build-deploy-gitea/pulls/12) page as a sample. Nice to meet you here @strypey and @hw.
Member
Copy link

@Malsasa : PR seems fragmentary, did you miss to push something?

@Malsasa : PR seems fragmentary, did you miss to push something?

For me, the mission is clear, the landing page is good, but unfortunatelly, it seems that the unclarity in core mission messaging just surfaced when someone posted about Codeberg on HN. Maybe there will be some other suggestions... the About page discussed here sounds like a good idea.

For me, the mission is clear, the landing page is good, but unfortunatelly, it seems that the unclarity in core mission messaging just surfaced when someone posted about Codeberg on [HN](https://news.ycombinator.com/item?id=22795930). Maybe there will be some other suggestions... the About page discussed here sounds like a good idea.
Member
Copy link

It seems that one of the most-mentioned issue in this HN post is that not everything is properly translated into all languages.

As translations can best be performed by native speakers, it would be great to see pull requests and contributions improving existing and adding new translations to the home page and all UI components!

It seems that one of the most-mentioned issue in this HN post is that not everything is properly translated into all languages. As translations can best be performed by native speakers, it would be great to see pull requests and contributions improving existing and adding new translations to the home page and all UI components!

closing in fafour of #14 (comment)

closing in fafour of https://codeberg.org/Codeberg/Community/issues/14#issuecomment-597329
-> https://codeberg.org/about
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
8 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#75
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?