Closed Andre601 closed 1 year ago
This may break some of the badges people are currently using, but I could give it a try. Maybe I'll keep a legacy badges folder, and then have a new assets folder which is the one that should be used.
Should this be counted as documentation? Or moved somewhere else.
This is what I have done for organization
This may break some of the badges people are currently using, but I could give it a try. Maybe I'll keep a legacy badges folder, and then have a new assets folder which is the one that should be used.
Maybe use GitHub pages for this? Like have the new badges on a github.io domain while keeping the old ones where they are right now. Another alternative would be to create a new branch as the default to use while putting the current one as a separate branch. That way should image links remain the same, while you can provide a new format.
Should this be counted as documentation? Or moved somewhere else.
Would say it counts towards documentation, yeah.
I think going the github pages way works out, because I was going to make a website for this anyway (not an automated badge picker though, idk how to do that)
It could be useful to put the images/SVGs into separate folders based on what they are for.
f.e.
spigot
orplugins
containing the badges for platforms supported ordownloads
for badges about where you can download them from.As an example:
badges/downloads/modrinth_vector.svg
Another thing that could be nice to add is a page to preview the badges. Something like a
PREVIEW.md
that would display the badges and also show their Markdown-code to use. Would allow people to more easily know what badges look like.If wanted can I work on this myself and PR it later on.