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.