This probably sounds ridiculous, but I gotta say it out loud anyway because it’s been driving me bananas for the past few days. I want to create an information resource specifically for Star Trek meme creators. I haven’t been able to get it out of my head, so I think I gotta just build it already.

What would this site even have on it, you ask? Off the top of my head, I’m thinking the contents would consist of: the list of official Trek fonts for all shows (already in progress), links to screencap sites, links to the few Trek meme generators that are out there, software recommendations by platform, maybe a few guides here and there. Basically, all the stuff that would make it possible or easier to make your own Trek memes. Most of us here already have our own workflow set up just the way we want it, but not everybody does, and I’m also thinking a resource like this could help lower the barrier to entry a little.

I write code and documentation for a living, so it’s kinda in my wheelhouse. It would be a fun thing to do on the side, and I’d be lying if I said I didn’t have a platform and host already in mind.

But I’m wondering if this would actually be used? And would anyone here be interested in contributing?

  • Kelly Aster 🏳️‍⚧️@lemmy.worldOP
    link
    fedilink
    arrow-up
    2
    ·
    9 months ago

    On the other hand, the advantage of using markdown platforms (like Docsify) is that they can be hosted directly from the repo without having to be deployed on a host; yeah, hosting, I forgot to mention, can be a bear to maintain and is not something I’d like to take on or pay for. That shit can get expensive. There are wiki service providers like Nuclino that have a free tier of hosting, but they all look like they’re closed source. One of my requirements is it be open source so anyone can fork it and do what they want with it (also addresses the “what if I get hit by a bus” question). The same goes for other collaborative CMS packages, I don’t wanna deal with hosting.

    So something like Docsify would have a higher barrier to entry, but it’s also something I am comfortable with/capable of managing. Even if we had someone volunteer to take on a DevOps role and set up & manage a deployment pipeline, there’s still the issue of the hosting costs. Yeah lol, it sorta comes down to money, and I unfortunately I think I gotta draw a hard line in favor of free open source over free proprietary. omg I don’t know if that sentence makes sense. I’m so baked, what time is it? Is it tomorrow yet?

    • jawa21@lemmy.sdf.org
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      9 months ago

      It’s always tomorrow somewhere :p As for proprietary vs FOSS (typing this from Arch, btw) - I really get it. However, with things like hosting in general which I’ve struggled with finding good solutions for my edits a lot I’m not sure there really is a good solution here. I’d argue that since this is meant to potentially be a resource for all Trek meme editors and/or content creators, then odds are that pure accessibility and low maintenance/hosting costs are going to have to be considered first and foremost. The point I’m trying to make is that IMO this should be able to benefit everyone that could use such a thing, which will unfortunately (IMO) require something proprietary - especially if it actually takes off and eats up a good amount of bandwidth per month. If someone hosted it on their bare metal at home, there could be a lot of a) security risks and b) down time.

      Also, this looks promising at a glance. Take a look: https://meta.miraheze.org/wiki/Miraheze Admittedly not FOSS, but it is opensource.