The real reason Twitter beat the snot out of Pownce

Twitter gives our mundane lives meaning, that’s why it beat the snot out of a more ‘feature-rich’ Pownce.

To prove my point, let’s rewind about a year and a half ago to Tamar Weinberg’s comparison entitled ‘Twitter vs. Pownce: Who Pwns?‘ Dutifully she does what many of us do while shopping for software, cars, and food processors – she compares and scores the features of one product against another to a conclusion that reads:

Pownce 5, Twitter 3. Pownce wins!

There’s only one problem with that approach, while features may sell a product, it is ultimately functionality that sustains a product; software or otherwise.

Which is why I think Scoble succinctly hits the nail on the head while unwittingly predicting Pownce’s demise in his Twitter vs. Pownce post also from early July 2007:

“But, anyway, I still like Twitter the best. Why? No complications. It does only one thing. I find that on my cell phone I go back to Twitter before I go back to any of the others. It’s lightweight.”

Put another way, when it comes to microblogging, Twitter has it all over Pownce because it makes it easy to do the one thing we all want from microblogging – making the mundane instances of our lives meaningful, while learning new things about our friends without coming off like a stalker.

Disagree as some “new media marketeers” might, the reason we like Twitter is the same reason we fell in love with Blogger, it got out of the way and let us opine reflectively about how our cats would join us in contemplating the lint in our navels.

For example, why anyone would follow my own Twitter page is beyond me, yet some find the fact that I fertilize my lawn in December and enjoy smash-mouth football entertaining and interesting.

And like blogging, Twitter easily allows our friends and relatives to quickly comment at their convenience – only with the excellent 140 character excuse for not engaging in exposition and detailed explanations.

All this while providing others context about ourselves that may not come out in our blogs, lectures, books and top-rated podcasts. This latter point is nicely explained in this 2:25 YouTube video from the good folks at the CommonCraft Show aptly entitled ‘Twitter in Plain English.’

Pownce unfortunately lost sight of these primal purposes for microblogging, and in the process ‘featured-creeped‘ their product to death. Not an uncommon instance for software in any era. Especially when said offering described its services with a church-speak-like mission statements:

“… Pownce is a lightweight productivity app, built on top of the stream, and it has all the pluses and minuses of a productivity app (including that you can use it to share music with friends!)”  – Pownce is competing with 37Signals, not Twitter!

Any wonder we all stopped using Pownce around 160 days ago?

So what has this got to do with your church and/or charity website? Glad you asked.

Remember, software features are only relevant to the primary activities you’re trying to accomplish with the assistance of automation.

Put another way, when you’re picking or designing a program to get something done – ignore all the fluff-n-stuff that has little or no bearing on what you want to get done.

For example, if all you want to do is post 1-up snips of your daily life, then Twitter is just enough software to get it done. No need to worry about file storage, groups, rooms, etc …

… which is also why I’m thinking Twitter is also likely to eventually beat the snot out of FriendFeed; but I digress … so more on that topic latter.

For now, here are some related links on this topic:

Your mileage may vary on this one, but deep in your heart, you know I’m right about making the mundane meaningful vs. marketing appeal of Twitter.

Now please, if you don’t mind, link this post in your next tweet, add it to all your social network links so I can be proven wrong about the marketing thingie. A simple @deanpeters reply is all it takes!-)

Do you not know that in a race all the runners run, but only one receives the prize? So run that you may obtain it. Every athlete exercises self-control in all things. They do it to receive a perishable wreath, but we an imperishable. So I do not run aimlessly; I do not box as one beating the air. – 1 Corinthians 9:24-26

Posted in Uncategorized

Working with the WordPress theme Vigilance 1.16

I’ve been a bit dissatisfied with the HealYourChurchWebsite look-n-feel since early this summer. After a lengthy search of various WordPress themes, I’ve settled on Vigilance 1.16. Here are some of the reasons why along with some of the things I discovered and/or did to make it more suitable to my tastes.

What I was looking for:

I was looking for a 3 column theme that had a clean look, was configurable, and wouldn’t put be behind the 8-ball with later versions of WordPress.

I also wanted to avoid one of these themes offered by various and emerging “clubs” as they tend to focus more on ad revenue generation than providing one’s users with the ability to get things done.

In my case, my users want to get these things done:

  • aggregate my posts with ease
  • find stuff to help with and/or addresses specific issues
  • quickly and easily link and/or copy the title or content on their blogs
  • print my posts and read them offline and/or nail them to the door of their church

Some other themes I considered were:

I had a hard time NOT using this theme. Under the hood, it is very well thought out and implemented. That said, it is suited to a slightly different audience than mine – that is small organizations or businesses and not so much individual webmasters and developers. That said, don’t be surprised if I make the switch to it one day – or at least implement it immediately on other projects.
From the folks at Daily Blog Tips, this theme had many elements I liked, but there were just too many sacrifices of semantic markup for SEO and/or layout to make me want to use this long term.
Another theme that had many elements I enjoyed, but to me had too many ‘highly styled’ element treatments that to me, made implementation of any custom CSS a bit more hassle than I wanted.
Similar to Ashford, this theme was better suited towards church and charity websites. That, and while it did have several SEO-centric elements, there was enough there that I wanted to re-code or customize that made me look elsewhere.
Fresh Editorial
Again, an attractive theme that while nice, would have locked me into some renderings that would just drive me a bit bananas.

There were other themes but the above list themes I might use for other projects – and just what type of stuff I want to get into or avoid for a personal blog such as HYCW; including:

  • Has a good WordPress Admin/Configuration screen or screens
  • Is easily modified via CSS and through the Vigilance Child Theme
  • Does not sacrifice usability for SEO visibility
  • Is coded clean and clearly enough in PHP that I can confidently make modifications
  • Shows a history of active updates, participation, and interest
  • offers easy upgrades

Oh yeah, one other big thing I was looking for:  easily allow my users execute on the actions and/or activities they desire, need, and seek.

Oh yeah, one other big thing I was NOT looking for:  force me to sell my first born child into some SEO club.

How I made it work:

Having some time over this past holiday weekend, I figured it was time to bite the bullet and make it happen. Here are some steps you may find useful:

Install the theme

cd wp-content/themes
cd myvigilance
nano style.css
nano vdean.css

As you can see, ‘myviligance’ is the name for the basic child theme for Vigilance – which I immediately took advantage of that by adding the following to the file /wp-content/themes/myviligance/style.css:
@import url("vdean.css");Oh Sure, I could have just added all my code into style.css directly, but I just felt more comfortable working this way – and was glad myviligance was set-up in such as way that I could.

Configuring the Theme

First stop was the vigilance options panel, which is immediately available after you select the “myvigilance” child theme as your default:

With it, I was able to modify things such as:

  • Layout and Colors
  • Top Banner Image
  • Alert Box
  • Sidebar Image
  • Sidebar Feed Box
  • Footer

Then using Chris’s Web Developer extension for FireFox, I got busy with the CSS:

What I did was make test changes I previewed in the “Edit CSS” panel of the Web Developer extension – then once satisfied, physically modified vdean.css either through the command-line editor on the actual Linux platform … or the CSS “Theme Editor” link provided via the WordPress “Design” tab.

Hacking the Theme

Hey, what red-blooded coder with 25 year’s experience isn’t going to make some code changes here-n-there?

  1. I moved the tags to the bottom of the post. I know it’s less SEO friendly, but it is ALOT friendlier to my readers whom use tags as a way of finding related articles. I also added the CSS class “post-tags” to the markup for easier modification: <p class=”post-tags”>
    … Said changes needed to be made in index.php, page.php and single.php. Perhaps the use of an include file can consolidate this in future iterations of the program?
  2. Downloaded and modified some of the colors of some of the icon images.
  3. Uploaded a number of header images to rotate.
  4. I moved the admin edit link to the top of the post, which is generally where I need it and look for it. I also gave it the class “edit-this” for easier management later:  <?php edit_post_link(‘Edit This’,'<p class=”edit-this”>’,'</p>’); ?> … Likewise, changes were required in index.php, page.php and single.php.
  5. In sidebar-feedbox.php, I added the class ‘rss-feed-title’ to the header tag.
  6. install the Social Bookmarking RELOADED plugin in place of the Gregarious social bookmarking plug-in that stopped working after v2.3 of WordPress.
  7. in search-form.php, I added the class ‘search-form’ to the header tag.
  8. Then in sidebar.php, searchform.php, and sidebar-feedbox.php – I changed all instances of<h2> to <h3> because semantically, I just believe that’s the way God intended it.

While these hacks mean I’ll have to do the same for future releases, I’m at least hoping that the good folks over at will at least consider adding some additional classes to the header tags I cited above to make for easier CSS management of various elements.


There’s enough available out-of-the-box with Vigilance 1.16 that most webmasters of church and/or charity websites could use it out-of-the box. And whle the same can be said for worth themes such as Tim Bednar’s Ashford, I’m hoping my choice – when finally tweaked to perfection – will provide my particular user-base the best interface needed for their required activities.

Until then, I’ve still got ALOT of modifications I need to finalize. For example, I’m not pleased with my treatment of hyperlinks, image/caption boxes and/or a few other elements associated with the post layout.

Still, this is all managable through the CSS file at this point – so suggest away.

Posted in Uncategorized