I just watched again the video at Cloudcannon and still wonders what it is useful for. You can edit copy live on pages, but who needs to do this? To correct a typo? To update an info? Then you kind of bury the previous content… and it’s very limited, or it seems to be. The reality is that the smallest client don’t need to fix typos, but to create content. Another post, another event, add a paragraph, remove one… all of these things are beyond editing what’s already in place. I’ve worked from numerous clients, from the super small one to the extremely big ones. Let’s just consider the small ones, and I can’t find one who will only need this kind of edit. On top of that, you edit what’s online, when most likely you need to put things in place (as a designer) waiting for the client to edit them, but once online I find it a bit late for such edits. Plus those edits, how do you bring them back to your source? Next time you publish your Webflow code, it vanishes, so you’ll need to track clients edits to replicate them in Webflow?
If it’s only about being able to edit some blocks, loosing the previous content, not being able to create anything (there is a notion of repeatable blocks in CC but I can’t figure how big this feature is), isn’t it kind of a gadget? The other benefits are light. Publishing from dropbox to avoid remembering a ftp password?
I really don’t want to make this sound like bashing, but I’ve read all the Cloudcannon discussions here and the least I can say is I’m the opposite of convinced. I am, like you, in need of such a solution: giving independence to small to medium clients, without asking anyone to log on a Wordpress-like backend they’ll never use (how many time did I do that?). We even once published a Cloudcannon-like edit system on a Drupal. But once the pages published no one ever felt the need to modify the copy or change an image.
Have you really worked with CC? What did I get wrong?
I’ve put a lot of hopes in Webflow for my small to medium clients business. I can’t think of Webflow not coming up with CMS features rather sooner than later.