I would like to try making a few minor changes to the CSS in either kbin or lemmy both of which I’ve been trying out. I favor a more dense interface and think styles could help visually separate different kinds of content. Maybe to reorganize some stuff if I got more ambitious.

I have some experience with web stuff, css. I can get around in git. But I am not a sysadmin or a programmer. And I have never worked on such a large comprehensive project.

Here are the repos I found:

codeberg Kbin/kbin-core

  • seems to have no contib guidelines
  • issues: 50 open, 4 closed

github LemmyNet/lemmy

  • contrib - same link for both repos but doesn’t really give much useful info

  • Issues: 184 open, 1,594 closed

github LemmyNet/lemmy-ui

  • issues: 197 open, 507 closed

Do I need to run the whole server with back end to fiddle with the CSS? Or can I use the developer tools in my browser to produce an alternative stylesheet?

Maybe it is just way above my skill set to make full PRs in something so complex. Should I post mock ups of how I’d like it to look as an issue?

Or just wait for someone who knows better how to get it done to come along?

  • Sibbo@sopuli.xyzEnglish
    10·
    1 year ago

    If you want to start contributing to a complex open source project, there are different approaches depending on how well prepared the project is for new contributors.

    Some projects label some issues as “good first issue.” If you find those, go ahead and comment into the issue that you are interested in resolving it. It helps to discuss first what you want to change, and especially ask if the issue is still relevant and the text in the issue still up to date. You may then even get some help and some pointers what to watch out for when implementing, which help you understand the code better.

    If there are no such issues but you have some ideas anyways, you could create an issue and discuss the idea.

    If you don’t have any own ideas, you can make an issue asking what issues are good for first timers.

    But in the end, always communicate, and sometimes also don’t fear to create a prototype if the community around a project does not seem to know well what they want for certain issues.

    • crank@beehaw.orgOPEnglish
      3·
      1 year ago

      hmmm all good thoughts. I would like to see about trying to do some stuff locally without discussion to see if it is viable for me at my level of skill and time availability. If I can get a dev environment running and figure out the basic tasks involved then I would probably start discussions about what I might do.

      There doesn’t seem to be much prior issues, especially kbin, on this topic, unless it is in a separate repo that I am not seeing.

      I am guessing that neither project anticipated it was about to get slammed and may not be ready to deal with that on the server admin side and also be managing bug requests and onboarding new devs with all kinds of ideas.

      • Sibbo@sopuli.xyzEnglish
        3·
        1 year ago

        That is a great approach! I think if you manage to set it up yourself, the project may benefit from a pull request with a dev setup guide 😉

        • crank@beehaw.orgOPEnglish
          2·
          1 year ago

          Even in the best case scenario I probably don’t have the breadth to write something PR-ready but an issue with notes would probably be doable. (Unless the existing docs are already docs are already perfect, which they could be.)