I’m trying to add a modified css for lemmy-ui to my self-hosted instance running on Docker. I’m following this guide but the custom theme is just showing up as litely. Steps taken:

  • Went to bootstrap.build, made the necessary edits.
  • Exported the bootstrap.min.css as well as the _variables.scss
  • Renamed them to theme-name.css and _variables.theme-name.scss
  • Do the necessary bind mounts so lemmy-ui can access the files. Can confirm the files are correct and appear within the container.
  • From lemmy web ui, select from drop down the theme called theme-name (it shows up with the right name and all).
  • Press Save, but theme is just litely.
  • Use dev tools on browser and can confirm theme-name.css is just the litely css. cat theme-name.css within the container is showing the right content.
  • LEMMY_UI_EXTRA_THEMES_FOLDER is set correctly since the option for theme-name is showing up, it’s just loading litely instead.

Not sure what I’m doing wrong here :/

  • lckdscl [they/them]@whiskers.bim.boatsOPEnglish
    0·
    1 year ago

    If you see my response to the other comment on this post, I basically had the same issue, my theme looked like the screenshot you attached when generating with bootstrap.build. I ended up not using it at all.

    I didn’t want to get into bootstrap, so yes I edited it by hand. My theme isn’t perfect yet, it took me 2 hours or so by editing the vaporwave theme.

    • tko@tkohhh.socialEnglish
      0·
      1 year ago

      OK, thanks for the input. My theory at the moment is that Lemmy doesn’t actually need the SCSS files. If you look at the CSS file, it doesn’t reference the variables at all. That’s why you’ve had success modifying the CSS by hand. Somebody in the Matrix chat said that they pulled down the lemmy-ui code so that they could generate the CSS file in the same way that the built-in themes do. I’m going to take a look at that now and see if there’s a way to extract that portion.