Custom Branding Support

[W1BTR]

What is the problem you are trying to solve with this feature?

I'd love to use homebox for a small business, but the branding of homebox makes it less likely to be approved by the deciding staff. It's great for hobby/home use, but for the small business space it seems unprofessional.

Small problem, but I believe an easy feature to add (we've all heard that before, though).

What is the solution you are proposing?

Allow a replacement logo and banner in the config or docker image

What alternatives have you considered?

Ive considered replacing the assets in the image, but I've had a hard time finding them. If I can, I could possibly mount a local directory to replace them with.

Additional context

No response

Contributions

• [X] I have searched through existing issues and feature requests to see if my idea has already been proposed.
• [ ] If this feature is accepted, I would be willing to help implement and maintain this feature.
• [ ] If this feature is accepted, I'm willing to sponsor the development of this feature.

[voron69-bit]

I also second this. Been trying to find the assets in the console of the docker, and can't seem to find them. This should be easily replaced via configuration settings in the UI management. The themes are great, but that logo in the header and has to go.

[tankerkiller125]

@voron69-bit In the latest version there is an option to turn off the banner in the user profile settings.

[voron69-bit]

@voron69-bit In the latest version there is an option to turn off the banner in the user profile settings.

AHHH BRILLIANT! Any chance we could change the image?

[katosdev]

@voron69-bit In the latest version there is an option to turn off the banner in the user profile settings.

AHHH BRILLIANT! Any chance we could change the image?

I still need to track down how this is defined in the code, but makes sense to allow customization, especially in instances where Homebox might be used for SMB's etc.

[tankerkiller125]

@katosdev Code wise, the banner is just a component, and the Logo is just an inserted SVG (so no big deal).

My thought is that instead of doing this on a whole instance at once, we could instead do this at a group level, and save the images (either uploaded, or just the URLs to them) at a group setting level in the database, and then use the group setting in the JS.

[katosdev]

@katosdev Code wise, the banner is just a component, and the Logo is just an inserted SVG (so no big deal).

My thought is that instead of doing this on a whole instance at once, we could instead do this at a group level, and save the images (either uploaded, or just the URLs to them) at a group setting level in the database, and then use the group setting in the JS.

That's a good shout actually, also then gives the possibility to extend this with SSO support if sub-teams of an org were to have their own inventory section.