Trying a new blogging process - Google Docs

Why don't I blog more? I get a lot of those questions. The biggest reason has been that I never get through a blog entry without having to close my browser and losing my session. This can happen intentionally or unintentionally, like when Firefox crashes or my computer runs out of memory.

Hopefully, I have addressed that problem. At the suggestion of Dan Vega, I am going to try using Google Docs to write my entries first. Until a few nights ago, I had never used Google Docs, but I am now impressed. It's very easy to use, and I love the auto-save functionality. BlogCFC has always had this problem for me - losing what I write. I often go back, write and re-write what I have written, and I have always seemed to lose the entry before I publish it. This happens a lot less since I upgraded my BlogCFC a few months ago (although I am a little out of date now), but it still happens if the browser craps out. I blame that on my ability to tax a browser/computer over the application itself. Anyway, hopefully, I'll start blogging more with this new process.

Does anyone else run into this problem? How do YOU solve it?

TrackBacks
There are no trackbacks for this entry.

Trackback URL for this entry:
http://www.brianmeloche.com/blog/trackback.cfm?630FDCD3-3048-2E57-0AFD40F18C6D2346

Comments
I have been using Google Docs for blogging for about 5/6 months and it works great. I obviously only use it for lengthy, in-depth posts but it allows me to easily work on it over time and generally results in better posts. Here is my Google Doc workflow (it is nothing mind-blowing but you may find it useful):

1) I lay out the idea for my post by creating a bunch of section headings (if the section is complicated I may jot some notes into the section). This works like a quick and dirty outline and gives the finished product an article-like appearance IMO

2) Fill in each section

3) Re-read several times and make revisions (at this stage you can add others as readers if you want some third party review)

Looking forward to your upcoming posts :)
# Posted By Brian Rinaldi | 6/25/07 7:25 AM
I do something similar to Brian. I actually have one document titled Article Ideas. In this document I keep a list of ideas for future postings. Once I commit to an article I start a new google document and break it down into sections and then I can add details as I go. Glad to see its helping out!
# Posted By Dan | 6/25/07 7:29 AM
Brian, a couple thoughts. First, do you realize that BlogCFC has an option to set an entry as not released, in which case you can "save" it. I'm still running 5.005, so it's functionality that's been there a while. Perhaps more recent versions let you stay on the page to continue editing (for now, it goes back to the entry list and you have to re-select it to continue editing.)

Also, this may seem old-school (leave it to me, the geezer), but another tip is to edit the entries in an editor. Besides saving them to a local directory (or leveraging any auto-save mechanism it may have), it also has the benefit of letting you use the editor's features to add HTML features (bold, bullets, etc.) without you having to enter the HTML yourself (again, perhaps a later version of BlogCFC has a new WYSIWYG editor, but the version I run does not). Does Google Docs let you get the HTML underlying a doc you create? Just never thought about it before.

Finally, I suppose a benefit of using GD (versus an editor and local files) is that you can edit the doc on a machine other than your own. I don't have that requirement, but certainly if one does, then it's yet another notch in GD's belt.
# Posted By Charlie Arehart | 6/25/07 9:00 AM
You know Ray's blog has xml/rpc support right? That means it is ready to use third-party tools for blogging.

I, myself, use: Ecto: http://ecto.kung-foo.tv/, but there are other's out there. Windows Live Writer and Qumana to name a couple..
# Posted By Critter | 6/25/07 10:28 AM
Windows Live Writer
http://get.live.com/betas/writer_betas

Granted it is windows but it works well.
# Posted By Scott P | 6/25/07 10:52 AM
I just write mine as email drafts (using my local email client). When I'm happy with it, I go to my website, add a new blog entry and then delete the saved draft from my email program. Autosave, works when I'm offline (when I write most of my longer blog posts), simple.
# Posted By Sean Corfield | 6/25/07 8:39 PM
@Brian R: My problem is that I get interrupted a lot in mid-post, so even a SHORT entry is susceptible to being lost. I also like writing and editing, and editing, and editing some more, before I post.

@Dan: I'll give that some thought. I have gotten into the habit of making notes and reminders to myself, so that might also work for me.

@Charlie: Yes, I realized that you can do that, but even that has not worked out for me. For one reason or another, I never save in time... or my browser hangs, or my computer hangs (e.g. my laptop at work has a weird problem where it shuts down on an incorrect password in RDC), but I like the constant saving of Google Docs, and it's a nice little editor.

@Critter: No, I didn't realize BlogCFC had XML/RPC support. Hmm. I used to use w.bloggar a few years ago when my WVMUG blog was on Nucleus CMS. These days, I am Mac G4 at home (no Intel) and XP SP2 at home, so I need something that I can use in both environments. Google Docs seems to be a good choice for now, but I'll consider other possibilities as they present themselves.
# Posted By Brian Meloche | 6/25/07 8:46 PM
What's the difference between going into gmail, clicking compose, the merely saving the draft for a later time. Going into googledocs seems excessive. Unless you're using more rich text formatting then I think ...
# Posted By noname | 6/26/07 4:59 AM
I have tried using GMail, too, but GMail is now being blocked at the office, so that won't work, at least in the short term. I don't think it's actually GMail, but Google Ads that are blocked.
# Posted By Brian Meloche | 6/26/07 2:19 PM
Has anyone else had an issue with the html that google docs produces?

Generally with the Podcasts on CFFrameworks.com, the post is written collaboratively on Google Docs - and then copied and pasted to BlogCFC when everyone is happy withi it...

We often have a problem with random CSS being inserted (almost like MS Word HTML) - which tends to break things...
# Posted By Dan Lancelot | 7/15/07 4:40 AM
Also, this may seem old-school (leave it to me, the geezer), but another tip is to edit the entries in an editor. Besides saving them to a local directory (or leveraging any auto-save mechanism it may have), it also has the benefit of letting you use the editor's features to add HTML features (bold, bullets, etc.) without you having to enter the HTML yourself (again, perhaps a later version of BlogCFC has a new WYSIWYG editor, but the version I run does not). Does Google Docs let you get the HTML underlying a doc you create? Just never thought about it before.
# Posted By Jack roberts | 5/18/08 10:53 AM
BlogCFC was created by Raymond Camden. This blog is running version 5.5.002.