Add new post, preferably elsewhere

Now here’s something I hadn’t seen before: “4 Solid Reasons Not To Write and Edit Your Blog Posts Directly in WordPress.” Of course, I had to check that out.

The first sounds reasonable enough:

[W]riting your blog posts in a Word doc gives you an instant back up copy of your original content! Wouldn’t you want that, just in case (God forbid!) something happens to your website and your site back up wasn’t as good as you thought it was?

Downside: Having to use Word. Although there are reasons why you may want to:

If you write for other publications, you often are asked to submit the content in a Word doc so the editor can format, upload and add images.

And what’s more:

Having a copy in a Word doc gives you instant access to repurpose the content you have already created … having it saved as a Word doc saves you from logging in and copying and pasting each time you need it!

If I were writing full-time, those few seconds might mean something to me.

This, however, is the one that’s fun:

[Unfinished drafts] do clog up your database, which could make it run slower and is a performance hit. That all depends on how big your database is; it has to be pretty big, like approaching 1000 posts and pages, to really notice the difference. But, if speed is money, then you’ll notice!

I approached 1000 posts and pages, oh, let’s say 14,000 posts and pages ago. The limiting factor has been, not the size of the database (about 72 MB), but the speed with which the Web server on Machine A talks to the database server on Machine B.

And if that’s not heretical enough, try this: the pony stories (see sidebar) are written in the WordPress editor. There are two reasons for this: I like it better than Fimfiction’s editor, and it enables me to maintain a Work In Progress blog without any effort. There are, incidentally, eleven versions of the most recent chapter.

(With thanks to CASUDI.)


  1. Dan T. »

    22 February 2014 · 12:11 pm

    No need for proprietary M$ formats. I edit things in plain ASCII text in UltraEdit.

  2. CGHill »

    22 February 2014 · 12:36 pm

    I expect to hear from a vi user any moment now.

  3. Bill Peschel »

    22 February 2014 · 3:25 pm

    A big disadvantage of writing in Word is that any unusual characters, such as em dashes, translate as “?” in WordPress. I have to resave as a text file, open it in a text editor, then copy it over. Or remember where I placed the @$%^@$% dashes.

  4. CGHill »

    22 February 2014 · 6:50 pm

    I’ve basically learned over the years to do everything as HTML entities, even if it’s a pain in the neck.

  5. jsallison »

    22 February 2014 · 8:53 pm

    I use word, openoffice, libreoffice, notepad, whatev depending on where I am and what box I’m pecking away at. I’ve also been known to use canary yellow legal format notepads and pencils or the back of the odd loose envelope. Ya do what ya have to. Teaching my granddaughter to read using MLP fanfic, she was chosen the official pony princess in her preK class last year.

  6. jsallison »

    22 February 2014 · 8:57 pm

    And she’s officially peeved that there appear to be no MLP zebras. I sense a marketing opening…

  7. CGHill »

    22 February 2014 · 9:13 pm

    Well, there’s one, though toy versions have been few and far between.

  8. McGehee »

    23 February 2014 · 9:24 am

    I edit in the “View” window, and double-check by switching over to the HTML window to make sure View knew what to do with any unusual characters.

    I am more likely to have to edit HTML tags (like referencing my stylesheet for paragraph indents or blockquote styles) than entities.

RSS feed for comments on this post