Merge all Codeberg Badges approaches into one solution #456

fnetX commented 2021年05月29日 16:12:27 +02:00

Meta-Issue: I keep repeating myself in explaining people that we want to unify several Codeberg Badges topics (https://codeberg.org/get-it-on, https://codeberg.org/ribbons), issue #391) into one central repo.

Now I'll point them to this issue.

Motivation:
Right now, we have the following projects:

• official get-it-on, deployed to https://get-it-on.codeberg.org/
• new ribbons, (Update: no longer) deployed to https://ribbons.codeberg.page
• mentioned Codeberg pages in issue #391 that are not yet visible to the public
• an API generator for the get-it-on badges at https://codeberg.org/lucas/CodebergVBG
• an unofficial redesign of the get-it-on badges at https://codeberg.org/getiton/pages

The idea is to move all this into a Codeberg/Badges repo that can be served at badges.codeberg.org and provides a fancy generator frontend following the Codeberg Design Kit and allowing to embed the badges easily by exposing API urls for generation ...

If you're interested in help designing this, just reach out to us.
@lucas are you interested to assist, too? You did the getiton-fork.

Meta-Issue: I keep repeating myself in explaining people that we want to unify several Codeberg Badges topics (https://codeberg.org/get-it-on, https://codeberg.org/ribbons), issue #391) into one central repo. Now I'll point them to this issue. Motivation: Right now, we have the following projects: - official [get-it-on](https://codeberg.org/get-it-on/pages), deployed to https://get-it-on.codeberg.org/ - new [ribbons](https://codeberg.org/ribbons/fork-me-on), (Update: no longer) deployed to https://ribbons.codeberg.page - mentioned Codeberg pages in issue #391 that are not yet visible to the public - an API generator for the get-it-on badges at https://codeberg.org/lucas/CodebergVBG - an unofficial redesign of the get-it-on badges at https://codeberg.org/getiton/pages The idea is to move all this into a Codeberg/Badges repo that can be served at badges.codeberg.org and provides a fancy generator frontend following the [Codeberg Design Kit](https://design.codeberg.org/) and allowing to embed the badges easily by exposing API urls for generation ... If you're interested in help designing this, just reach out to us. @lucas are you interested to assist, too? You did the getiton-fork.

lhinderberger commented 2021年07月01日 00:42:49 +02:00

As discussed earlier on Mastodon, https://codeberg.org/lhinderberger/dot-slash-badges-web is currently in the making, which adds to the list of possible projects that could be included within a unified badge generator.

It adds "repository info"-type badges to the listed "download"- and "ribbon"-type badges.

As discussed earlier on Mastodon, https://codeberg.org/lhinderberger/dot-slash-badges-web is currently in the making, which adds to the list of possible projects that could be included within a unified badge generator. It adds "repository info"-type badges to the listed "download"- and "ribbon"-type badges.

fnetX commented 2021年07月12日 22:23:48 +02:00

Now that dot-slash-badges is apparently the preferred solution and deployment is being prepared, I'd actually like to make sure it is flexible enough and allows the inclusion of the other projects later.

I didn't really find the time to look at it ...

Now that dot-slash-badges is apparently the preferred solution and deployment is being prepared, I'd actually like to make sure it is flexible enough and allows the inclusion of the other projects later. I didn't really find the time to look at it ...

lhinderberger commented 2021年07月12日 23:49:30 +02:00

The way I understood it is that ./badges will in the short term be used for repository badges only, but it can be extended to also include other types of badges later on.
The advantage of that would be that then there's only a single, generic type of badge generation backend around. Also, ./badges already supports baking text to paths.

The current state of this is that ./badges itself is already flexible enough to use custom templates, themes and fonts, making it possible to generate arbitrary badge SVGs from its CLI and Go Library.

What's essentially left to do is:

• Add a way to ./badges to declare template parameters so that the web frontend knows which set of fields to show for any given template
• Generalize the web frontend, which currently only supports the builtin-standard-badge template, using the parameter declaration above

While doing that, I want to apply a number of general improvements to the ./badges generator as well (see lhinderberger/dot-slash-badges#1).

So, to sum things up: To make ./badges web a generic solution for generating all kinds of badges, there is some work left to do. But in the short term, we could simply build a page that basically integrates the existing get-it-on-generator and ./badges web in one page (for example using iframe).

The way I understood it is that ./badges will in the short term be used for repository badges only, but it can be extended to also include other types of badges later on. The advantage of that would be that then there's only a single, generic type of badge generation backend around. Also, ./badges already supports baking text to paths. The current state of this is that ./badges itself is already flexible enough to use custom templates, themes and fonts, making it possible to generate arbitrary badge SVGs from its CLI and Go Library. What's essentially left to do is: - Add a way to ./badges to declare template parameters so that the web frontend knows which set of fields to show for any given template - Generalize the web frontend, which currently only supports the builtin-standard-badge template, using the parameter declaration above While doing that, I want to apply a number of general improvements to the ./badges generator as well (see lhinderberger/dot-slash-badges#1). So, to sum things up: To make ./badges web a generic solution for generating all kinds of badges, there is some work left to do. But in the short term, we could simply build a page that basically integrates the existing get-it-on-generator and ./badges web in one page (for example using iframe).

lhinderberger commented 2021年07月13日 00:06:50 +02:00

Regarding ribbons: Was there some sort of generator deployed at the now-defunct page or was it just a demo of the CSS ribbons found in the linked repository?

If it's the latter, I think the ribbons should stay as they are. IMHO, it makes little sense to render those CSS ribbons into SVG.

Regarding ribbons: Was there some sort of generator deployed at the now-defunct page or was it just a demo of the CSS ribbons found in the linked repository? If it's the latter, I think the ribbons should stay as they are. IMHO, it makes little sense to render those CSS ribbons into SVG.

n commented 2021年07月13日 07:28:43 +02:00

Regarding ribbons: Was there some sort of generator deployed at the now-defunct page or was it just a demo of the CSS ribbons found in the linked repository?

If it's the latter, I think the ribbons should stay as they are. IMHO, it makes little sense to render those CSS ribbons into SVG.

There actually wasn't any generator or any page for the ribbons. Just the repository. The idea was to make codeberg/badges a monorepo with the ribbons as well.

> Regarding ribbons: Was there some sort of generator deployed at the now-defunct page or was it just a demo of the CSS ribbons found in the linked repository? > > If it's the latter, I think the ribbons should stay as they are. IMHO, it makes little sense to render those CSS ribbons into SVG. There actually wasn't any generator or any page for the ribbons. Just the repository. The idea was to make codeberg/badges a monorepo with the ribbons as well.

lhinderberger commented 2021年11月09日 22:20:37 +01:00

A new release of dot-slash-badges is now available that supports the features outlined above.

I have also prepared a new release of dot-slash-badges-web that supports arbitrary custom templates in combination with dot-slash-badges v2.0.0.

Be advised that I have stopped further development on dot-slash-badges-web, but the current state of it can serve as a starting point for someone to develop a "Codeberg Badges" on top of it (e.g. by taking its reusable Vue components).

A new release of dot-slash-badges is now available that supports the features outlined above. I have also prepared a new release of dot-slash-badges-web that supports arbitrary custom templates in combination with dot-slash-badges v2.0.0. Be advised that I have stopped further development on dot-slash-badges-web, but the current state of it can serve as a starting point for someone to develop a "Codeberg Badges" on top of it (e.g. by taking its reusable Vue components).

fnetX commented 2024年08月23日 20:36:16 +02:00

I just realized that the things we do in 2024 are completely different. Let's archive this.

I just realized that the things we do in 2024 are completely different. Let's archive this.