Custom branding proposition #21

Closed
opened 2023-11-16 10:09:28 +01:00 by blek · 2 comments
Owner

So, my idea about custom branding is as follows:

There is a resourceD, right? FileD could have config parameters like brand.big_logo, brand.small_logo or something which would be a resourceD resource.

On startup, fileD would check if resourceD has these resources available via some kind of http/rpc api (to validate the config, basically). Then place them in a nice, neat way somewhere on the pages.

Maybe also add possibility to replace the default stars image in the header with something else.

So, my idea about custom branding is as follows: There is a resourceD, right? FileD could have config parameters like `brand.big_logo`, `brand.small_logo` or something which would be a resourceD resource. On startup, fileD would check if resourceD has these resources available via some kind of http/rpc api (to validate the config, basically). Then place them in a nice, neat way somewhere on the pages. Maybe also add possibility to replace the default stars image in the header with something else.
Author
Owner

I think that the following things could be customized:

  1. The "field with stars" image
  2. Maybe remove the 1 and put a custom logo in the middle?
  3. Custom logos in social previews and favicons

Preview

I think that the following things could be customized: 1. The "field with stars" image 2. Maybe remove the 1 and put a custom logo in the middle? 3. Custom logos in social previews and favicons ![Preview](/attachments/f9f7346f-d771-44e0-9341-d0e0c2b751d7)
126 KiB
Author
Owner

I've reconsidered the position about custom branding: it is not that big of a deal and not close to be a significant part of the project.

However, if you want to see custom branding, you are free to implement it yourself. I will not delete the custom-branding branch, which contains most of the code needed for custom branding

I've reconsidered the position about custom branding: it is not that big of a deal and not close to be a significant part of the project. However, if you want to see custom branding, you are free to implement it yourself. I will not delete the `custom-branding` branch, which contains most of the code needed for custom branding
blek added the
Kind/Feature
Kind/Enhancement
Priority
Low
Status
Not planned
labels 2023-12-08 08:42:21 +01:00
blek closed this issue 2023-12-08 08:44:58 +01:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blek/bfile#21
No description provided.