hey @rob1998 thanks for the work on this.

A couple things:

1 - Let's go ahead and include custom.css in the repo, that way there aren't browser errors if the user chooses not use it. At least the file is present (even if it's empty) so the browser isn't throwing up errors. Also, we will need to include SOME text in the custom.css file because you can't commit an empty file. So, really anything will do that's commented out, but we'd def need a wiki section on this with some obvious customizations the user might make, like "background-color" - not saying we need to include that in the actual custom.css file, but I'm sure you get the point.

The custom.css file needs to reside in the /assets/data/css/ directory within the repo. This is primarily because of Docker. That directory will be symlinked when the image is built. If this isn't done, every time the user updates the image, the custom.css would get wiped.
What do you think of including the custom.css in the User Prefs settings page? Mock-up below:

FEAT: Custom CSS settings page #141

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions