3 ms·
Sure it demos well, but it's closed-source. Vendor lock-in sucks, full stop. And the time investment spent learning it won't pay off bc those skills won't carry
by chrisweekly 13y ago
Sure it demos well, but it's closed-source. Vendor lock-in sucks, full stop. And the time investment spent learning it won't pay off bc those skills won't carry over to the vast majority of other future projects that don't use it.
Building a site on bootstrap (from source, ie integrating bootstrap's less files as dependencies in your webapp via grunt and bower) is defensible; becoming entirely dependent on the capabilities of something like webflow, imho, is not.
I suppose if you're a designer in a hurry to build a pretty, throwaway site (eg a microsite for an event) then this might be worth your while. But if you're building something for the enterprise, anything you or your team might want to maintain and extend, I think it represents an unacceptable level of knowledge debt, to rely on site-generating tools like this.
YMMV of course. My views are skewed towards the UI architecture needs of a multi-million-dollar global company.
/$.02