doc: remove staticsitegenerators.net, update statigcgen.com link

[nodiscc]

• https://github.com/bevry/staticsitegenerators-list is unmaintained since 7 months, last update checks no longer working
• no activity in https://github.com/bevry/staticsitegenerators-list/issues
• staticgen.com now redirects to jamstack.org/generators

[kokomo123]

no problems with this, at least we have alternatives

[Rabenherz112]

The new project you're linking to doesn't appear to be maintained anymore either. According to their repository, the last commit was made 7 months ago. Additionally, their issue page is cluttered with spam (issues #948, #947, #929, #904, etc.).

Does it make sense to switch to a list that seems similarly unmaintained?

[nodiscc]

Thank @Rabenherz112 for pointing out the lack of updates on https://github.com/jamstack/jamstack.org

So what would be the best course of action now?

1. leave one (or both) links untouched, knowing that the lists are unmaintained (but at least comprehensive)
2. Remove the delegation/redirect on the Static Site Generators tag, copy back to awesome-selfhosted those that are still relevant (even if we curate the list, there are thousands of them, this is no small task and more importantly will absolutely flood awesome-selfhosted with static site generators)
3. copy static site generators that are still relevant to awesome-selfhosted-data, set up our tooling to generate a separate list at https://github.com/awesome-selfhosted/awesome-static-site-generators + https://static-site-generators.awesome-selfhosted.net/
4. same as 3. but with a separate awesome-static-site-generators-data source repository
5. find a better maintained, external list of static site generators

I think 5. requires the less work (assuming such a list exists). 1. requires no work at all. 3. would be ideal as it would not overload the main list, and the work can be reused to better integrate https://github.com/awesome-foss/awesome-sysadmin with awesome-selfhosted (possibly generate the markdown list and a https://sysadmin.awesome-selfhosted.net, but it is still a decent amount of work... 4. would induce a lot of duplication in tooling/issue management, etc.

[Rabenherz112]

I think we should first consider option 5; it seems to require minimal effort and could potentially yield good results.

As for the other options (2, 3, and 4), I believe you should decide on those since they will undoubtedly bring a lot of work, especially for you. From my perspective, option 1 is only a short-term solution because the list will become outdated and less helpful than just searching GitHub (listing generators that are either outdated or non-functional, etc..).

Also, I don't see how options 3 & 4 involve less work than option 2 other than not completely flooding the main readme/website.

[Rabenherz112]

I looked into this issue last weekend (but completely forgot to actually write in this discussion :P).

Last week, the bevry/staticsitegenerators-list was updated to include one new generator, though there were no other changes.

I also searched GitHub for alternative lists, which turned out to be more challenging than expected. Most "awesome-yourProgrammingLanguage" lists have a static generator section, but comprehensive lists that include all programming languages are rare. One of the few well-maintained and longer-standing ones is myles/awesome-static-generators.

[nodiscc]

Last week, the bevry/staticsitegenerators-list was updated to include one new generator

bevry/staticsitegenerators-list@7828482 but aurora cannot be found at https://staticsitegenerators.net/. Is their automatic generation broken? I think we should let them know (and link back here)

If there is a chance to get bevry/staticsitegenerators-list up and running again we should put the other solutions on hold

[Rabenherz112]

ref: bevry/staticsitegenerators-list#467