What do you do when the equipment your agency provides, will not support your goals for social outreach or the people ultimately in charge of the equipment do not want to run the software?
The short and long answer is… I have no idea.
BUT… I do know what I did. A bit risky. But in my case it worked. Or at least at this point it works. Subject to change at any given moment.
Disclaimer: I am using commercially available products. While I personally HIGHLY recommend these products, please do not interpret this as an endorsement of these products by my agency or my government body.
One of the most difficult things to do in my agency is to convince the leadership that something is available commercially and better than what we can provide.
It has nothing to do with their lack of technical knowledge or resistance to change. It’s an honest effort to fully utilize resources that we have available “in house”. Nothing wrong with that.
That being said, trying to explain to the uninitiated about SQL servers, running PHP 4.? vs 5.? and the associated connections is a bit tough. You get the glazed eye look after about 5 minutes, and usually what follows is, “put something together and bring it to us” and they move on to the next item of business.
What I did was bypass that step altogether.
This next part is NOT recommended unless you have a great relationship with the management of your agency. And I mean GREAT.
I went online to a hosting solution and registered two domain names that matched my agency’s current .org name. I registered a .us and .net domain. I then contracted with the provider for a hosting account. The scary part? I paid for it out of my pocket, planning to get reimbursed at a later date. IF they liked what they saw.
Then I went to work. I registered an identifiable moniker on several social networks like Twitter, Plurk, FriendFeed.
Then I installed WordPress on the domain and created an account at WordPress.com.
Now the fun started. I wanted a professional site, that didn’t look like a blog but had all the functionality of a blog. I toyed with the idea of installing Joomla and Drupal. I have used those platforms on many different sites and love them as Content Management Sites. The problem with them is the learning curve. Getting non-technical members of my agency to the level needed to maintain the site once I am transferred or retired would have been too much. Positions within my agency are very fluid and can change at a moment’s notice.
I chose WordPress because of the ease of adding an article and being able to limit the damage a “contributor” can do from the limited back end. So WordPress was my answer.
In the next article I will cover themes, how I chose the one I am using and why.