Custom branding proposition #21
Labels
No Label
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/TODO
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Service
filed
Service
janitord
Status
Abandoned
Status
Blocked
Status
Controversial
Status
Need More Info
Status
Not planned
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blek/bfile#21
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
I think that the following things could be customized:
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