I’m a designer and the decision for webflow was driven by @callmevlad 's basic vision, to give everyone the chance to build great websites, without having the need to work with a developer. After publishing some projects and learning to use this great tool, what is strong orientated on css, surely I’m a little bit more than a designer, meanwhile, what is ok, so far, as I assume the final results from Webflow seems so much better as regular homepage builders, or similar drag and drop tools.
Coming back to the basic vision, I don’t know, why we have to face now all that stuff about cookies and other technical things behind Webflow, just for following the EU GDPR stuff?
I solved all actual law privacy stuff, e. g. for Google Analytics and other things with a german platform, but they are not aware of tools like Webflow So, concerning Webflow I have a black hole at this moment, and wether I know, which texts I should add to this privacy policy pages of my clients, nor I know, what to tell my clients about potentially necessary contracts with Webflow.
I strongly hope, we will have soon a checklist with clear information about what we have to do in context of Webflow.
And in addition to that I want to mention at least Cloudflare, what is a necessary service to use with SSL, as some domain providers are not able to handle two different DNS entries. I’m not talking about custom code, what is surely not a problem of Webflow.
Btw. this domain stuff was working with some luck and support, but it is already sometimes at a technical level, where I would wish to have a service package from Webflow, which I could order, when it comes to connecting the clients domains.
Any feedback would be appreciated
Thx
Harald