[josefresco]

>For one, the template never lasts as long as you need it to. You realize the design isn't working, or your competitor just unexpectedly made a move. So you start trying to make changes. Swapping out the text and images comes easy, but as soon as you start adjusting the layout, frustration begins to set in. You've got a million other things to do and for some reason you can't get the page to look right on mobile.

I've seen this pain first hand when I "rescue" clients from DIY website builders or am forced to use one myself. It remains one of the main reasons our clients graduate from DIY solutions to working directly with a professional. How are your templates (https://www.makeswift.com/templates) different?

[migueloller]

The promise (and I understand it's something we have to prove) is that extensibility won't lock you down. The most succinct way I can put it is: component composition. We're making a bet on the idea of components as a composable visual entity that can be used for building websites.

By putting the abstraction layer, even with templates, at the component level instead of the page level like most builders do, we believe that all of these pain points Alan mentions in the article will be solved. The component you're using should be flexible enough to modify to your heart's content. And if it isn't, you can just find a third-party component to satisfy that. And if that component exist, then you should be able to make your own by just writing some React (or Vue, etc.), not interfacing with some bespoke API.

And becase these components compose, there shouldn't be a need for a "rescue". That's the vision.