New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Branding template #1613
Comments
work for Branding template #1613 Signed-off-by: Stefan Schiessl <stefan.schiessl@blockchainprojectsbv.com>
Would custom themes be in scope of this? Or solely a method of easily replacing the branding throughout the web wallet? |
After migration to the new bitshares styleguide is done it should be easily doable (right now possibly too, but waste of effort). With the new styleguide it should boil down to copying one of the existing themes and adjusting it, |
@sschiessl-bcp right. For now style-guide contains styles only for UI components we are going to use on bitshares-ui. Later I want to integrate it more close to bitshares-ui themes or even create separate repo with themes for bitshares-ui and bitshares-ui-style-guide where all info about theme will be placed in one json file. |
Please post your expected hours for this. |
No expected hours since this facilitates my commercial use of the wallet |
This feature aims to facilitate branding/customizing the reference wallet, e.g. for a white-label customized exchange. It's intent is to have a single point of entry that controls key branding aspects. The most simple customization job will then only require to edit this one single file.
Reasons are:
a) It facilitates the work of anyone that wants to create their own exchange or simply have a slicker interface with less assets shown etc.
b) It gives incentive to existing exchanges to keep their wallets up-to-date and maybe even get them to upstream as well by realizing the synergies
c) Up-to-date wallets are better for security, and it doesn't matter which BitShares powered exchange gets hacked, it is still bad publicity
A pull request will follow.
The text was updated successfully, but these errors were encountered: