[–] 3 points 6 days ago* (last edited 6 days ago)

Thank you for sharing, I wasn't aware of this feature. But to be fair, PieFed has it easier here because it has a ‘main’ frontend (unlike lemmy, where all frontends are third-party as far as the main software is concerned) that you can apply styling to. Even then, it can only work on that main frontend and not any alternate clients.

I really need to follow PieFed more closely, to be honest. It has so much stuff…

edit: actually, I just noticed this:

The custom CSS/JS/Jinja needs to be submitted and approved first, but then a moderator could add it to the community as the official theme.

So I assume an admin has to add it as a possible theme first, right? If that's good enough, I guess something similar could be done in mlmym too. mlmym should already be very easy to style; it doesn't have a skins/themes mechanism, but that's nothing that couldn't be added.

I think I'm still favorable to the addon approach because it would mean that the custom style could work across every mlmym installation without needing admin involvement, but a theme system is also a reasonable compromise.

  • source
  • parent
  • context
  • [–] 2 points 6 days ago (3 children)

    It doesn't, and due to the way lemmy frontends work, it likely won't ever natively have that feature. Something that might be possible though is a browser addon that applies custom CSS to communities when visiting them through mlmym? But someone would have to make that, and get moderators to submit custom CSS for their communities…

  • source
  • parent
  • context
  • [–] 2 points 2 months ago (1 child)

    Oh, while you're here, I think LANGUAGE_TAGS is also a good candidate to turn on by default (forgot to add it to the readme when I added the feature, so I also forgot about it in my earlier message...), and maybe SHOW_CONTROVERSIAL.

    There's also EMBED_METADATA for embeds (for links on Discord and such) to show, but I don't know if you want that.

  • source
  • parent
  • context