[Documentation] URL at https://gobolinux.org/recipes.html and recipe-specification + git sources

[rubyFeedback]

This issue has three issues in one, sort of - sorry!

First, when I did a google search just now, I encountered this here:

https://gobolinux.org/recipes.html

And then the github page here, for Recipes.

The recipes.html page at gobolinux is a bit sparse.

The gobolinux recipes at github is a bit more informative; at the least we see what has changed when, e. g. changed recently. I use this to track the progress of GoboLinux, as recipes are usually updated a LOT in many other distributions; see void linux recipes updated here: https://voidlinux.org/ under "packages changes".

My first "real" proposal is to add a link there, towards "gobo-recipe specifications". That is, for users to
click on, or read in-page there, what the various entries mean for a gobo recipe. Most of this
is easy and self-explanatory, but I remember some recipes included more complicated logic,
such as for use in shell scripts, and I think it would be very convenient to show the specification
too, in particular if other projects target the recipe format of gobolinux. In fact, that is also one
use case for me - I want to improve the old code I have for autogenerating valid gobolinux
recipes (that was also one partial motivation for simplifying the name-guessing of recipes,
towards always lower-case, at the least when handling things, as that is much easier than
having to guess the correct name. For instance in the past, for KDE 3, we had "KDE-Libs" as
a name. I think "kdelibs" would be an easier name, and it would be /Programs/Kdelibs/, or
in that case it actually may be easier for /Programs/Kde/. Then again, it is probably even
easier and more consistent to always have /Programs/NAME_OF_THE_PROGRAM_HERE in
a capitalized manner. Anyway I digress).

The second reason why I tried to find this out was because of sources at Github. These I
usually automatically check out via ruby, which in turn simply does a "git clone URL_HERE".
In my own project I registered all URLs for programs that I keep track. Just recently I had
a look as to whether new projects were added to the gobolinux recipe store. And indeed
I found a new entry:

https://github.com/gobolinux/Recipes
c12b625

I did not yet have simde registered, so I wanted to add it locally in my programs "recipe store",
where I use YAML file to keep track of those programs. I then looked at simde at github:

https://github.com/simd-everywhere/simde

The release tarball was just .tar.gz rather than the full program name + program version. In
such a case I typically just use the latest github source instead, which my scripts would
automatically repackage into e. g. simde-24.06.2025 (in DD.MM.YYYY format notation; this
one is quite popular in central Europe).

But I was not certain how gobolinux would handle such git-based recipes. That's also one
reason why I think a full specification, linked in from the gobolinux webpage shown above,
would be very useful. So, perhaps not just "merely" a specification only, but also as an
explanation. Like, the specification, which can be somewhat terse, and then also a few
paragraphs explaining how this is used in practice. Like a mini-tutorial or something like
that. Documentation in GoboLinux should ideally become better; I am aware of the
do-it-yourself situation for unpaied projects of course, but there is also a chicken-egg problem
in that, e. g. a new user, but also an old user who may not have used GoboLinux in a long
time, may not remember something or know something about GoboLinux. This is why I
think documentation is extremely important. At any rate, thanks for reading this.