I think it completely depends on how fast you are with the tool you're familiar with. I'm equally as fast in Webflow now as I was with Sketch/Photoshop - The best part is once I've finished in Webflow, It's ready to go live instantly (provided the end design is web related). With Sketch/Photoshop, there's still the extra step in converting the design to code...So even if the prototyping process takes a little longer, you may save time in the end!
That being said, I still love using Sketch and try to find ways to bring it into my workflow. Especially when used with InVision (It's magical).
But still nothing like going from design to production in ONE step :)
Yikes, not to be critical, but....
The text formatting is so off and line height padding of elements and text are so tight in that article, I found it unreadable.
Hope that layout wasn't created in their tool. :/
Mitchell, likewise, I still find the lowest cost and time factor of change is through high-fidelity mockups. I've been "on the Sketch" - since the day 3 came out. Officially addicted.
Even if it was created with their tool it speaks nothing of it's ability. That's like saying someones mockup sucks so it must be Photoshop's fault..
But I agree, they should tighten up the formatting of their blog posts, for sure.
However, I would expect that out of the box, some of the basics such as text line height padding, would be reasonably correct.
In other words, you would have to go out of your way to screw up something so basic.
Main thing though, it makes me more skeptical of their message and product, if that is representative of the output.
The main problem in the workflow you suggedt is is that webflow doesn't give the CMS solutions.. So after your frontend is ready you still need a developer to complete the project..
If you're OK with open source CMS solutions, it isn't terribly difficult to tie in an HTML template into something like Wordpress.