I love you and all, but what's with your error messages? I mean seriously, they are frustrating and they don't help me recover my lost data. You should really consider changing a bit what you transmit and communicate through these messages. Thank you.
There is no shame in admitting that this blog is powered by Squarespace ("The Apple of the CMS industry" - as the community names it). By all means I recommend you give it a try. The interface is clean, modern, intuitive and in case of wonders, there is always the great support from the Squarespace team and its users. As much as I like to praise this lovely platform, there is one "tiny" little problem that grinds my gears: the error messages.
They are frequently appearing when trying to write a blog post and instead of helping me recover, I end up losing the data. First things first, there are multiple types of errors you receive, but the outcome stays the same. The message is composed of an unfriendly text, some back-end spitted comments, an icon that looks like a clickable action (X marks the spot) and two options that don't do squat. The Reload button just refreshes the page (the blog post listing page in fact) and Clear just closes the modal window and guess what? You get back to the same page as the Reload . Two actions for the same result - kudos!
Regarding the text itself, I don't know what L2FwaS9jb21tb25kYXRhL1Nhdm... means, but I know a thing or two about JSON files and my question is: does a regular user without computer science background needs to know this kind of information? If it doesn't help me, then how it's going to help him/her?
The "easiest" solution I can think of is an auto-save feature. It could eliminate part of the frustrations of losing your data and get back on your feet again writing.
The other solution I am thinking of is to be honest with your users. Sh!t happens! We are not perfect, but instead of creating disappointment or anger, try easing the pain. The messages could be more user-friendly and instead of Reload or Clear why not going for a Save current progress - Send report approach. The users can keep their work and you get feedback from them. It's a win-win situation. And of course, no programming texts!
Know your users or at least try. I'm convinced that the Squarespace team does an excellent job improving their platform and with a little more attention and refinement, they could get closer and closer to offer a complete and satisfying experience. Keep up the great job ;)!