Whitelabeling Documentation
Posted: Fri Nov 19, 2021 9:05 am
Coming here for thoughts on whitelabeling documentation, as we are going to have a huge request for this going forward. We currently host on AWS. My product team is asking whether it is possible to have a custom product name in a back end config or the database and then push that out so that Flare could do it on the fly from a single URL. The example is this:
If we could do something like &product=FB in the URL that Flare would accept for the variable and then just have &product=WF passed in to replace the name that would save all the extra publish outputs.
I currently have variables and separate outputs and AWS buckets (URLs) for each differently named version. I'm not sure that Flare and/or AWS are capable of something like this or how you would even start to set it up.
Do you have any ideas or suggestions? Does your company white label? How do you handle it?
Thanks!
If we could do something like &product=FB in the URL that Flare would accept for the variable and then just have &product=WF passed in to replace the name that would save all the extra publish outputs.
I currently have variables and separate outputs and AWS buckets (URLs) for each differently named version. I'm not sure that Flare and/or AWS are capable of something like this or how you would even start to set it up.
Do you have any ideas or suggestions? Does your company white label? How do you handle it?
Thanks!