More branding and theming options for self-hosted instances

(#1329) Feature Under consideration self-hosting theming

2mo agoby RexSystem edited originally by @ghost on GitHub

Problem

Customization for Fluxer Instances (as its own category ofc within "Instance Config") Making it so we can change the following; fluxer embeds, codes, system messages, icons, wordmarks, buttons, colors, login screen, etc.

Proposal

Giving an option so members can make their own selection of icons, backgrounds, images, to use so it isn't generic. Cropping or Size Tool for the Wordmark so that it can be a bigger size rather than small size. Allowing for the Home Button to be a different color w/o the fluxer wave (ik it's customizable with the client but imo would be better to do it within the instance) Also a higher yet cooler addition, allow for a mockup 2017 discord login. (idk if it's possible but it would be cool)

Notes

image image image image

623606044-196f0bb2-151c-4ada-97a5-8e92e8adde4b.png
676×162 | 18 kB
623606113-07da6321-8cdb-4724-8e00-f9bff3605970.png
103×92 | 6 kB
623606156-82d857ca-0c8b-42d6-9703-8c79e45887ea.png
1375×963 | 73 kB
623606219-194b1436-d6eb-4bd5-928a-f7d9c70db49c.png
1313×654 | 1.3 MB

History

1 comment

RexSystem 1 vote 2mo ago originally by @ghost on GitHub OP

Only thing I forgot to mention, and I think other instance owners will agree.. Theming and branding should be for what the instance owners wanna make, and not limited to the maximum extent of freedom. Even if it looks as crazy as Windows 95-2000 Classic Theme Era

, Also that it's probably better for a longer extent of editing, since Fluxer is AGPL-3 licensed, it gives a better way for users to make it work instead of hardcoding it into the source. Right now, going that far basically means forking the whole thing. A config-level option (theme file, env vars, whatever) would let owners get full creative control without needing to maintain a fork just for cosmetic stuff.

Permalink