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

Codeberg's "clone me on Codeberg" ribbons #446

Closed
opened 2021年05月14日 05:50:21 +02:00 by vanous · 5 comments

We already have a great logo and badges, it would be also nice to have a ribbon for a webpage corner, like those "get me" or "clone me" on GitHub ones 1, so one can point to the source repo from Codeberg pages page. The use would look something like this, but my attempt is very ugly.

Not sure if this suggestion is well placed here or should be done in the Design repo.

We already have a great [logo](https://codeberg.org/Codeberg/Design/src/branch/master/logo-kit) and [badges](https://codeberg.org/Codeberg/GetItOnCodeberg), it would be also nice to have a ribbon for a webpage corner, like those "get me" or "clone me" on GitHub ones [1](https://github.blog/2008-12-19-github-ribbons/), so one can point to the source repo from Codeberg pages page. The use would look something like [this](https://vanous.codeberg.page/typing-game/), but my attempt is very ugly. Not sure if this suggestion is well placed here or should be done in the Design repo.

Check out ribbons/fork-me-on!

Check out [ribbons/fork-me-on](https://codeberg.org/ribbons/fork-me-on)!
Owner
Copy link

Cool.
For the CDN:

Note: This method is not recommended as the URL is subject to change.

What do you mean? The version? That could be simply replaced by main, right? Or the address of the repo? We could decide somewhat quickly if we want to keep or rename it.

I think this CDN method might be desirable for those who host on Codeberg pages since it does not matter there ... for external repos, they might not want to include Codeberg as a third-party resource.

Cool. For the CDN: > Note: This method is not recommended as the URL is subject to change. What do you mean? The version? That could be simply replaced by `main`, right? Or the address of the repo? We could decide somewhat quickly if we want to keep or rename it. I think this CDN method might be desirable for those who host on Codeberg pages since it does not matter there ... for external repos, they might not want to include Codeberg as a third-party resource.

I was unsure about the repo address and was thinking if it could be combined with GetItOnCodeberg into something like Codeberg Badges.

Also, unfortunately the CDN wouldn't work right now because the content-type is text/plain.

I was unsure about the repo address and was thinking if it could be combined with GetItOnCodeberg into something like Codeberg Badges. Also, unfortunately the CDN wouldn't work right now because the content-type is `text/plain`.
Author
Copy link

Awesome, thank you!

Awesome, thank you!

Closed in favor of #456

Closed in favor of #456
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#446
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?