Since I have very recently found myself engaged in blogging, I'll choose to explain how a blog site saves drafts, publishes posts, and deletes posts that are already public on a website. When you start writing a new post, but don't publish it quite yet, most modern blogging sites will automatically save your post without you having to go click the save button. It's copying the contents of your blog to the host site's server while preserving your copy of the file that you're currently writing. So, when you navigate away from the page without saving, the system will automatically save one last time, and there you go, your blog will be saved in the "Drafts" area of the blogging dashboard, and you can go back to access it anytime you want. When you actually want to publish the post, however, the site deletes all past saves in order to publish the post and save space. Fortunately, it does this only once the publishing process has been 100% completed. It also deletes that post from the "Drafts" section and moves it to the "Published Posts" section, or whatever your blogging site calls it.
When you want to delete an already-published post, the blogging site first removes it from the public website. Most blogging sites then put that post in the recycle bin, and you can delete it permanently from there if you want to. After that happens, your post is gone forever--there's no way of getting it back. Coming back to the idea that most blogging sites automatically save your work every few seconds (I've noticed that Wix is more aggressive in saving than WordPress), I find that it can be distracting that there's a little bar near the top of the screen that keeps moving back and forth every few seconds, and it can slow down the performance of the blog site; for example, typing can become a little laggy (which is especially annoying for me since I type fast), or the whole thing can crash, and a "We ran into a technical error" message can come up. I've had this particular thing happen quite a few times in the same session. I also find it a coincidence that the whole thing locked up and the error message popped into view the instant I was writing this.
Anyway, my main point is that there are downsides of blogging sites that automatically save your work every so often, and they include the distraction that emerges when you see a bar that keeps moving back and forth along the top of your website, and this auto-saving may also decrease the performance of the site altogether, not to mention crashing it. I haven't noticed any other problems with the way blogging websites create drafts, publish them, and then delete them, except for the performance issue mentioned above.
And that is all for Writer's Journal #11.
Komen