As I’ve been lamenting for awhile now, I find Blogger’s native interface to be far too unreliable. There is no safety net for errors made during the editing process. Anything you do is saved automatically when you do it, and the temporary memory within any document you have open for editing is reset anytime you flip from the visual editor to the code editor. This glaring problem has caused me to lose several documents over the years, as well as cause me partial baldness from tearing out my hair when documents go missing mid-edit. The interface feels like it was written in a different era and was written for a different purpose than it is being put to today.
The blogger website itself looks like something from the dawn of the internet, probably because it has remained essentially unchanged since Google bought the service, only doing incremental modifications as they tried to keep track of the essentially random directions that Google and then Alphabet pulled the service and other Google owned services through. Over the intervening years, the rest of the blogosphere went other places while Blogger, the original blog platform, cooled its heels in the safety of Google’s embrace.
As we approach a score of years since the millennium (that would be 2020 for the unenlightened) Blogger simply doesn’t do what the average blog writer needs it to do anymore, and neither blogger’s leadership nor Google’s apparently rudderless directions from above have done the end users of Blogger any favors. So, while I still acknowledge that Google owns my soul and safeguards most of my digital life, I’m going to have to strike out for parts unknown if I want to establish a website and a blog interface that does what I want it to do.
I have been trying, off and on for months, to replicate the parts of the Blogger interface that I like. I have stuck with Blogger for as long as I have because it basically does what I want it to do. Publish the articles I write and do the coding so transparently that I can tweak the code when I want to dig that deep into what shows up as an end product. The parts that I like? A What You See Is What You Get (WYSIWYG) editing function for most editing, with the ability to tweak naked HTML code directly, available when parts of the article I’m creating refuse to behave properly.
Documents that are text only can be created any number of places with any number of text editing packages. I’m creating this article on my Google drive because, as I said, Google owns my soul. It’s also everywhere that I am all the time that I’m on the internet, so it makes sense to write within an interface that can be accessed wherever you are, whenever you are. I imagine that I will be doing most of my writing in the future in this fashion. It’s just too easy, and it’s just harder to lose the information that you’ve written when it is duplicated across the multiple systems you access in any given day.
The problem with composing straight into a Google document saved on your Google drive is the same problem with editing in Blogger. No, Google documents won’t lose your text like Blogger does, but you really can’t see the code that underlies the display of text in the Google doc. Also? The moment you want to add anything to your text document, images, video or audio files, especially files hosted elsewhere on the internet, you are left at the mercy of whoever coded the interface for the word processor you are using no matter where you compose at, and the limitations of streaming are set in place by the content providers that put up videos and podcasts for you to consume or to recommend to others.
While what the hosting services provide for in the terms of serving content to you and anyone you direct to their links is out of the hands of average internet user; the former, what text/code editor you use to put your articles together in is entirely in your hands. It is completely possible to blog right out of your Google drive if that’s your cup of tea.
To use this quietly rolled out feature, type in your Google Doc as you normally would and hit the “Publish” button. One of the options is to post to your blog. You’re presented with the following screen:
As you can see, the window asks for your blog type, username, password, and blog name. The support a large number of blog engines including WordPress, Blogger, Moveable Type, and more.
But again, you are confined by what the Google documents editor allows you do do, as well as the limitations of the HTML editors that are available for Google drive. Most of them do not host a proper WYSIWYG interface, one that you can input text from directly. If you can think in code, then you have plenty to choose from. Knock yourself out.
I’d also like to get some more control over what shows up on my site wherever it is hosted. What will be magically added or disappeared by the authorities that manage that site. I may be Google’s bitch, but I’m not willing to be their slave. Which means I need to host my own website, which means finding a web host. I go into that process, and a whole lot more in this article, and the one that follows it. But this article is about migrating a Blogger blog to a WordPress installation that I host myself.
A process that I have now successfully completed. Like most things in WordPress, there is a plugin for that. That plugin actually just comes with a WordPress installation by default. You can get another plugin to go with it that will preserve the permalinks from your Blogspot site so that readers of your previous site will be accurately redirected to your new location on the web. I don’t know how useful that information will be to today’s bloggers. Blogger doesn’t seem to be the place to go for starting public diaries anymore.
It’s easy to leave Blogger and the editing interface that you change to will have to be more reliable than Blogger’s now. Make the move. You can thank me later.