You only need the API key to continue visually editing the page. If you want to export your content you can just export your page data as JSON and pass it to the open source Makeswift Page component found in this package:
Hm, I'm looking at it right now in Firefox 82 with uBlock Origin and everything looks fine to me. Do you have any other details? Thanks for the report!
I like to say it's 75% easier to learn than Webflow with 80% of the capabilities. Over time, we want to get that up to 95%. Webflow has an amazing product if you already know how to code. You can make award winning websites in Webflow, but it will take you time. Makeswift sites may not be winning any AWWWARDS (yet), but you'll be able to build something good in a fraction of the effort. In addition, other people on your team can learn it as well, parallelizing your throughput. If speed is top priority, then our product is for you.
Squarespace and Wix are great for people who want to set up a template, skin it, and forget it. Their focus on wizards and templates optimizes the user experience for beginners, but at the cost of flexibility for advanced customization. There are a lot of people that this makes sense for.
Makeswift is designed for opinionated people who are constantly tinkering with design, layouts, and new ideas, but don't want to climb a giant learning curve. We're focusing on making a generic, flexible user experience with composable components that doesn't have opinions about how you build your pages.
From your comment and article it seems you're focused on marketing teams rather than a general purpose website builder. It would be great if you communicated this in your homepage. I know a couple of marketing teams using WP just to use themes and building landing pages.
Extensibility is a good way to sum it up, but there's many specific issues with each. The biggest problems we hear about with Squarespace are responsive layout overrides. The templates are also generally pretty rigid.
Wix's current editor is based on fixed position (think photoshop / illustrator). This approach works great for banners, graphics, icons etc, but is inherently at odds with web design. The solution for fixed position builders is to hardcode breakpoints, but there are too many devices. It's better to just design a UX around the box model, as that's how we code for the web anyways.
Editor X has potential but there's a little too much magic happening in the layout for my taste.
These are just a few of the many pain points. From our research, companies rarely keep using Wix / Squarespace after a certain stage. I personally haven't tried scaling a Squarespace or Wix site, but I also have never gotten them to a point where I was happy with all of the details before deciding to just code it myself.
Wix has a responsive layout from what I've seen as a casual maintainer of a rather large Wix site, which was originally built by a non-coder. Maybe it was part of the template he used, but a row of 3 images on Desktop automatically becomes a column of 3 images on mobile, and the top menu turns into a hamburger. You can also switch to mobile mode while editing to adjust the layout of the mobile version.
It's more complicated than this. You design a desktop version of the site in Wix, and it automatically generates a mobile version. Some widgets like image galleries and lists are responsive, but they have hardcoded rules.
So, it's not a fully responsive templates, but they are good enough for most websites.
Especially now that I’m over 40, the important of contrast can’t be overstated yet right now everyone seem to be competing on how many barely discernible shades of grey they can have layered over their sites and content.
Lots of good common sense guidance in there - and it’s freely available/useable to all.
We do all hosting ourselves at the moment. As for trying it out, we're currently in early access and you'll need an invite code to use it but if you apply [1], you'll get one in your inbox pretty quickly.
At Makeswift we're on a mission to build the best tool for creative minds to bring their ideas to the world. The concept is simple. Combine the experience of a buttery-smooth, elegant design tool with the infrastructure required to go to production. Instead of mocking up static images and prototypes, build production-ready websites out of live components. Working with React engineers? Reuse their work by integrating existing components directly into Makeswift. Our vision is to open up our APIs and foster a component ecosystem that will bridge the gap between developers and designers.
We're hiring the first engineers outside of the founders following a 1.5M seed round. If you're interested in working with a product led, early stage startup up against ambitious technical challenges, read more about the opportunity here:
At Makeswift we're on a mission to build the best tool for creative minds to bring their ideas to the world. The concept is simple. Combine the experience of a buttery-smooth, elegant design tool with the infrastructure required to go to production. Instead of mocking up static images and prototypes, build production-ready websites out of live components. Working with React engineers? Reuse their work by integrating existing components directly into Makeswift. Our vision is to open up our APIs and foster a component ecosystem that will bridge the gap between developers and designers.
We're hiring the first engineers outside of the founders following a 1.5M seed round. If you're interested in working with a product led, early stage startup up against ambitious technical challenges, read more about the opportunity here:
If you manage a Next.js marketing site and have non-technical teammates who want to move faster, we've created Makeswift for you.
We've just launched a way for engineers to incrementally add visual editing capabilities to their Next.js sites and would love some feedback.
What do you think?