Skip to content
This repository has been archived by the owner on Jan 15, 2025. It is now read-only.

White labeling #397

Open
1 of 5 tasks
feruzm opened this issue Mar 9, 2021 · 2 comments
Open
1 of 5 tasks

White labeling #397

feruzm opened this issue Mar 9, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@feruzm
Copy link
Member

feruzm commented Mar 9, 2021

  • configurable backend, optional private api for user stored data (drafts, bookmarks, schedules etc.)
  • signup page
  • faq / terms of service / privacy policy
  • coloring/theming that allows logo and color tweaks
  • app name, domain, imagehoster base env variable
@feruzm feruzm added the enhancement New feature or request label Mar 9, 2021
@talhasch
Copy link
Collaborator

talhasch commented Mar 9, 2021

We can redirect signup page to https://signup.hive.io

@feruzm
Copy link
Member Author

feruzm commented Mar 9, 2021

We can redirect signup page to https://signup.hive.io

Yes, I agree.

Some initial thoughts for other parts,

  • Logo, faq, tos, privacy policy, better would be to have json file that injects those data and any instance could put in their json url into env to use.
  • page title and meta should be ok, I believe we have more generic title and meta data that doesn't include Ecency, so should be ok as is, can be marked as done actually.
  • colouring/theming is mostly design related tweaks which I think we could just rename globalStyle into ecency theme and make other themes optionally switchable. We might need community or blocktrades team help for defining hive.blog theme for example, but structure of code offer theme changing..
  • app name is of course another .env variable, just like we should have domain name into this section as well.
  • image hosting upload and base change is supported by render-helper perhaps this should also be part of .env variable.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants