Another Change To My Writing Workflow

Till not long ago kept all my drafts in one big posts’ drafts. It was a good way to log things I’ve learned, while preparing to share those learnings in this blog. Keep this huge file public, meant to encourage me to iterate on drafts and eventually turn them into posts.

In an earlier post I mentioned that this strategy didn’t work very well, as this draft file turned into a draft cemetery – whatever got into it, didn’t come out. I, therefore, changed my workflow, and implemented the WordPress scheduling feature. I found that writing a first draft, and setting a publish date 2 days or so into the future, is much more effective in keeping me focused finishing up posts, and eventually help me write more.

The only thing is that I need to write those drafts somewhere, and I still want those drafts to be online. Instead of going back to my old single draft file, I figured I can start drafts in separate files, categorize them as drafts and publish them into the future. But I don’t want those drafts to show on the main page, so I installed the “Ultimate Category Excluder“, which let me exclude posts from certain categories to show up in the homepage.

Update: This “hiding category” solution won’t work… to begin with, even if I hide a category, when publishing a draft post, subscribers get a notification that there’s a new post on my blog. I don’t want that to happen. Second, the whole scheduling thing doesn’t work anymore, because the post is already live when I post it as draft… so no motivation to go back to it, more than do it when it’s part of a larger file…

 

No Exuses To Blogging

No-Excuses-Guide-to-Blogging-Sacha_Chua-v2.jpg

Awhile back I wrote about my experience learning to touch type. While writing it, I found this related article by Sacha Chua, which helped me rationalize to myself why it is such an important skill to learn. I ended up spending almost an hour browsing Sacha’s site. The amount of resources, posts, tips and tutorials that she shares is humongous!

Continue reading No Exuses To Blogging

Moving to WordPress

pelican-to-wordpress.png

That was quick.

Couple of weeks ago I wrote about thinking to move my blog to WordPress. Since then, I’ve used WordPress1 in conjunction with my static blog, and published posts to both sites. This experiment helped me to reaffirm the pros and cons of using WordPress, especially the part about concentrating on writing rather than site administration. During those two weeks I posted more, and became comfortable working with, and in, WordPress.

When I realized that I started to publish first to my dummy WordPress blog, and then reluctantly to my static blog, I made the decision to switch. Yesterday I completed the migration.

Following is the checklist I’ve used to manage the migration. It helped me going through the process with no downtime, and no prodissues 🙂

Continue reading Moving to WordPress

Should I Keep Using Pelican Or Move To WordPress

I’m currently using Pelican to power this site. Pelican is a static site generator (SSG) that takes markdown files as an input and generate html pages as an output; no database, no server-side logic; just simple, static HTML.

When I created this blog, using WordPress or Tumblr wasn’t an option, simply because every geeky blogger I follow wrote about how much those platforms suck, and how using SSG to run their blog were the best move they have ever made. I chose Pelican1, because of its popularity and because it is written in Python.

Continue reading Should I Keep Using Pelican Or Move To WordPress

Should I Move My Blog Here?

I’m currently blogging using Pelican as my static site generator (here’s a link). I started with that because it seemed like the cool thing to do – write your own blog, control everything, and write posts in plain text, or markdown.

But as time went by, and I wrote more and more, I got annoyed with the constant need to maintain and manage Pelican. I start getting bored, tinkering its internals. What’s more, it started to take longer to post new entries. Pelican generate the entire site, every time a post is edited. So as I’ve accumulated posts, making changes and seeing their results became a long process. With 26 posts now, it takes almost 2 minutes to a see a change I made in the development site.

So I want to give WP a try. Don’t know if I’ll like it, and if I’ll be ok with loosing some of my control. But who knows…

 

That’s it for a test page, right…?