godoc-static executes and scrapes a local godoc process to generate static documentation sites. These static sites, when served to your org or publicly, can provide access to relevant documentation without reliance on any third-party services.
A demo of its output is available at https://docs.rocket9labs.com
I am not an F-Droid maintainer, but as far as I know the code is not vetted by F-Droid after the initial app submission process. Updates are pulled in, built and distributed automatically. The long delay is just because there are a lot of apps to build, and F-Droid is a volunteer-run operation.
If your app doesn’t meet the target minimum API level on the Google Play Store, then it doesn’t get published. It’s just as much of a guideline, so I don’t think this is really relevant to the point of the article.
F-Droid is more of a marketplace for software developers than it is a set of community curated apps. The requirement for F-Droid software to be open source is just a guideline/rule like the minimum target API level on the Google Play Store. F-Droid is a neutral platform in my observations over the couple of years I have published there, and does not curate its content.
The graphical client is powered by the Ebitengine game engine.
Source code:
godoc-static executes and scrapes a local godoc process to generate static documentation sites. These static sites, when served to your org or publicly, can provide access to relevant documentation without reliance on any third-party services.
A demo of its output is available at https://docs.rocket9labs.com