EDIT: Might be able to get this set up. Hang tight!

There was a little bump in users, and the LemmyWorld admins posted this, but the included apps guide was out of date. I went to ask about it and saw the account that made the post is no longer active (moved instances). I then tried to update it myself and made progress, but got overwhelmed.

Two parts of my suggestion:

Part 1) Have a repository to pull from

Users don’t like to go off site, which is why a pinned post with the resources works well. However, pinned posts go out of date, and it’s a lot of ask for one person to manually edit it and keep it updated.

Instead, why not make a repository with a collection of markdown files containing the post body contents. Then there would be one source of truth that everyone can update.

The post contents would also include:

  • Link to the contribution page, so it’s easy to suggest changes
  • Last updated date, so that if a post goes out of date the users can ask it to be updated or just go to the source.

Whenever the post needs to be updated, the OP can paste in the newest contents.

Part 2) A nicer list of resources

I guess this is more of a ‘nice to have’ feature, but it would be nice if we had a site that was easier to navigate, ‘prettier’, and more accessible to casual users. We have this for our community/Subreddit, and it’s pretty easy to keep updated: https://ubcwiki.ca/index.html. It runs open source mdBook

Right now Lemmy has awesome-lemmy and [awesome-lemmy-instances](Owner avatar awesome-lemmy-instances). But they’re not the nicest to look at, and it’s a bit annoying to find content (especially awesome-lemmy) because of the format. There’s a lot of text on one page, and little variation in spacing/text size.

The new site could have the same contents, a lot could be copy and pasted over, and it could be updated from the same repo. Only difference is that it would be nicer to use.

  • wiki_meEnglish
    1·
    1 year ago

    You could use github pages and have awesome-lemmy deploy to it and have html web page without all the extra github stuff , it should be relatively easy to do.

    I suggest against creating another project, i see this type of duplication and it really can be confusing (which source do i use?) plus it is a duplication of effort and the fediverse does not really have a lot of contributors unlike companies such as google and facebook.

    On the other hand i am the second most frequent contributor to awesome lemmy and might not be entirely objective.

    If you want a github organisation could be set up for awesome-lemmy and after a while you could become an owner and it won’t have the bus factor of 1, maybe we can even set up a “lemmy community” github organisation (something like nix-community) and that could make it easier to discover some projects and if for some project and contributor loses interest another one could be assigned (without all the links and it’s name recognition going to waste)

    • Otter@lemmy.caOPEnglish
      1·
      1 year ago

      I was silly and posted the comment before I was done writing it. I’m done writing it now, sorry about that

    • Otter@lemmy.caOPEnglish
      1·
      1 year ago

      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@lemmy.ca 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

      threadiverse-community (organization)
  |-> awesome-lemmy (repo): structured the same way as it is now
  |-> LemmyKnow (repo): to run the website & the post pages
  |      |-> website has pages with resources
  |      |-> repo has MD files for posts that users can copy from
  |-> other Lemmy related projects

      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@lemmy.ca 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

      • wiki_meEnglish
        2·
        1 year ago

        I got a bit lost. How does it usually work for those, and what is the advantage of keeping that format opposed to website?

        What would you like to know?, you basically just edit the file and submit a pull request, you can even do it using only github GUI.

        I makes it very easy to contribute (you don’t need to know HTML/react whatever) and read it if you are using github, and github makes discovering repositories easy using topics (see for the example the “lemmy” topic).

        If I have the right idea, it would be something like

        Yeah i think you got it, i would prefer info on awesome-lemmy won’t be replicated on LemmyKnow.

        • Otter@lemmy.caOPEnglish
          1·
          1 year ago

          Right ok makes sense :)

          I’ll send a message later on once we get an idea of what we want to do