That’s a very fair point, and it does carry weight since you’ve been contributing for so long (thank you for doing all that!). Reducing duplication of effort is a big part of the goal. I was talking to @cynber about the repo/project and nothing has been set up yet. Part of why I was thinking a new project was after reading about awesome-lemmy (and the requirements for ‘awesome’ guides) I got a bit lost. How does it usually work for those, and what is the advantage of keeping that format opposed to website?
I think a Lemmy organization (or threadiverse organization) could work well, and it would definitely make it easier to keep track of the projects. I don’t have as much experience in that area, so I’ll probably defer to others who know more about it.
If I have the right idea, it would be something like
<span style="color:#323232;">threadiverse-community (organization)
</span><span style="color:#323232;"> |-> awesome-lemmy (repo): structured the same way as it is now
</span><span style="color:#323232;"> |-> LemmyKnow (repo): to run the website & the post pages
</span><span style="color:#323232;"> | |-> website has pages with resources
</span><span style="color:#323232;"> | |-> repo has MD files for posts that users can copy from
</span><span style="color:#323232;"> |-> other Lemmy related projects
</span>
Ultimately, if it works out, we could shift over sections from awesome-lemmy to the website, so it’s more accessible. For the site, @cynber can confirm, but I think the plan was md-book running on GitHub pages.
In the meantime, it might be worth it to give the site a try and just not advertise it. If the site doesn’t work out, then the whole thing is kinda moot anyway