You are here:  Home » Blog

Archive for the 'Uncategorized' Category

Saturday, December 27th, 2008

Yesterday I moved www.webcommunicate.net and blog.webcommunicate.net to WebFaction. I had been using WireNine as my host since May 2007.

I have no complaints about WireNine. They’ve been great. I still use them for some of my clients’ websites and wouldn’t hesitate to use them in the future. I opened the WebFaction account in September only because they are set up better for Django, a development framework I use for some behind-the-scenes tasks like keeping track of invoices, expenses, etc. Ultimately I decided to move everything to WebFaction for the sake of simplicity.

So, I now have two hosts I can recommend: WireNine and WebFaction. I have more experience with WireNine, but I suspect WebFaction will be just as reliable.

WireNine uses cpanel, a very popular control panel that most web people are familiar with by now, since it is used by so many hosts. WebFaction has their own control panel. Normally I think it’s a mistake for a host to develop their own control panel, but in this case I like it. It’s a very straightforward, no frills interface with dropdown menus across the top.

In addition to the Django installation, I have also installed WordPress, Xaraya and Drupal on WebFaction. WebFaction has an auto-installer for Django, WordPress, Drupal, Joomla, Rails, TurboGears, Zope, etc. Xaraya is not an option in their auto-installer but it was easy to install nonetheless.

Tuesday, September 23rd, 2008

I’ve been playing with Django a bit in the last day or two. It’s impressive. I suspect I’ll have some use for it. The admin interface is nice to look at and super fast.

I set up a hosting account at WebFaction for the purpose of trying Django. WebFaction will install Django (or Rails, Drupal, Joomla, etc) for free when they set up your account. My account was set up in just a few hours.

Django also provides me with an excuse to learn python, a language I haven’t used before now.

I’ll have more to say about Django once I’ve spent more time with it.

Monday, August 25th, 2008

Sometimes I send emails to clients that I suspect I’ll need to refer back to at a later date, in some cases months later. Some examples are emails where I’m providing instructions on how to use some feature in the client’s content management system, emails where I’m asking for clarification on scope-of-work, or anything with a substantial amount of content I may want to reuse later.

To make sure I don’t lose those sent emails, I set up a new gmail account today to serve as an archive. I will BCC that new gmail address whenever I want to save something.

My usual email program, Thunderbird, has a decent search feature, but it’s not as good as gmail’s. Also, I don’t want to have to worry about whether I’m deleting important emails whenever I quickly delete a lot of old emails in Thunderbird. By BCCing the gmail account, I know I’ll have those emails forever and they will always be easy to search for.

Thursday, May 15th, 2008

I’ve worked on a couple Drupal projects in recent months, after a few years when I worked almost exclusively with Xaraya.

At the outset of the Drupal work, I wrote a one-page reference comparing the file structure of a Drupal theme with that of a Xaraya theme. I revised it today. It might be useful for those who have some experience with one CMS and want to try out the other.

Now that I have a substantial amount of experience with both Drupal and Xaraya, I have no strong preference for one over the other. They’re both very good.

The user interface for Drupal 6 is a bit slicker than the Xaraya interface. The ability to change the order of menu items and data fields with a drag-and-drop AJAX interface is great new feature in Drupal that, for now, Xaraya lacks.

See also this related post.

Wednesday, December 19th, 2007

With Google News Alerts, you get results for your specified search terms sent directly to your email inbox whenever Google finds matching web pages — which is quite often, as you’ll find out if you use the service.

I’ve been using Google News Alerts to find RFPs and contract jobs that suit my interests.

Meanwhile, with so many people posting their resumes online, Google News Alerts could also serve as a recruitment tool. Search terms could include job titles, industry buzzwords, and the city where you need to fill an opening.

Anybody who has used the news alerts knows that the biggest problem with the service is how inclusive the results are. You’ll get some results that aren’t very useful even after you’ve gotten better at coming up with good search phrases.

Coincidentally, my work started to get busy again right after I set up my news alerts. So I haven’t paid close attention to a lot of the emails, but I have looked at some of them. In some cases the searches have turned up things in my field that were of interest to me, even if they weren’t actually RFPs.

Wednesday, December 5th, 2007

(The following is an article I published on TechSoup.org early last year. Still worth a read, I’d say. I want to make sure I have a copy here in case they move it at some point…)

Rethink Your Organization’s Web Site

Ways to ensure your site offers value to its visitors

Many organizations carefully deliberate before launching a new campaign, product, or program, but will add new features to their Web sites — or allow old features to persist — indiscriminately, without a clear idea of how, or if, those features provide a valuable service to their target audience.

Because they see Web content as harmless and impermanent, these organizations make changes to their site as if doing so had no impact on the site’s overall success. Yet posting something online doesn’t necessarily mean that you’ve added value to your organization’s Web site, or furthered its goals. On the contrary, content and features that don’t provide value will detract from your efforts by:

  • Burying valuable services from your audiences;
  • Wasting time and resources that could be spent on valuable services; and
  • Diminishing visitors’ confidence in your ability to understand what they value, thereby lessening their opinion of your organization and encouraging them to seek information or services elsewhere.

Getting into the Service Mindset

Anything you offer on your Web site, be it static content or an interactive feature, can and should be considered a service, and therefore held to the same standards you apply to any other service your organization offers.

In other words, everything on your site, down to the phone number listed on your “About Us” page, is a service to your visitors. Examples of services offered by most Web sites include:

  • Providing contact information for the organization or for individual staff members;
  • Supplying information about the organization and its work or areas of expertise.

Other services a nonprofit or NGO site might provide include:

  • Publishing a directory of experts in the field;
  • Aggregating current news from multiple sources;
  • Providing a means for visitors to interact with one another or publish content;
  • Supplying an archive of news and information from various sources;
  • Helping site visitors comparatively shop for products and services.

Once you get into the habit of thinking of every feature on your site as a service, you’ll want to ensure that every page of your Web site offers real value to both your readers and your organization.

Evaluating Your Web Site’s Services

If you’ve designed campaigns and programs, you already have many of the skills you need to evaluate your Web site. You’ve spent time thinking about how to maximize the effectiveness of your offline campaigns and programs, and you’ve assessed their value to your organization. You can apply this same type of critical thinking — along with some common sense and research — to your Web offerings.

The keys are:

  1. Don’t fall into the trap of thinking that because you’re not a techie you can’t make good decisions about your site.
  2. Don’t think that you’ve added value to your site simply because you’ve managed to get something online. You wouldn’t apply that kind of thinking to organizing a conference call or developing a campaign, so don’t let yourself off easy with your online efforts.

On the other hand, there is at least one very important difference between the Web and your other services, and that is that the exit barrier for Web services is generally much lower. If your audience doesn’t find what they’re looking for on your Web site, they’ll quickly search for something better elsewhere, particularly when it comes to content. But even with interactive services that require setting up an account, users can easily lose interest if they sense that they can find something better elsewhere. Because it’s possible to try out most online services quickly — and often at little or no cost — loyalty may be less of a factor than with “real world” service providers like banks, auto repair shops, or couriers.

Thus, before adding a new feature to your site, search for comparable services on the Internet to make sure that what you plan to provide is unique, that it serves a real need, and that your organization is qualified to meet this need. You must truly understand how each of your services will contribute to, and differentiate, your site in order to ensure that implementing them will be worth your while.

Some Additional Tips

Think of user scenarios.

This is good advice for evaluating everything you do on your site, from providing a contact number to implementing more ambitious interactive Web applications. Imagine scenarios where someone might use your services. What are they doing when it occurs to them to go to your Web site? How do they first find it? What do they do when they get there? Think of as many scenarios as you can, involving as many different types of users as you can, and you will start to get ideas about how to make your site more helpful to your users.

Consider doing less and doing it better.

Are you trying to do too much with your site? Do you envy the large, labyrinthine Web sites of rival organizations? Consider the possibility that certain parts of your rival’s site might not be getting that much use, and that you may be more effective by focusing on a small set of services that you can provide better than anyone else. Ask yourself: Is your site trying to do so much that you no longer know if your target audience is benefiting from the services you provide? If so, perhaps you should scale back.

Consider doing more.

Are there services your organization could offer more effectively or more inexpensively online? Never stop thinking about ways your Web site can do more of the work of your organization. You don’t have to act on every idea, but keep track of them. Better yet, solicit input from your audience to spur ideas about ways you might better serve them.

Make it very easy.

When you do offer a service, make it easy to use. It can be tempting to just “put it out there” and see whether a service catches on, with the idea that you can improve things later if it shows signs of appealing to your audience. However, you will never know for sure if a Web service can work unless you commit to doing it well and removing all possible hindrances for your users. Consider this: If indeed the service fails, you don’t want to wonder whether it could have succeeded if only you had made it a little easier, or inviting, for people to use.

Everything is connected, and small details matter.

Everything on your Web site is connected — in more than just the obvious structural sense. Sometimes, improving one part of your site can lead to greater success in another seemingly unrelated part. Here are just a few examples of small adjustments that can make a real difference:

  • Renaming one or two links in your main menu to make them catchier or clearer.
  • Redesigning your search results page to encourage people to search again if their first search didn’t yield good results.
  • Displaying your listserv sign-up form more prominently.
  • Simplifying a registration form.
  • Making it easier and more inviting for people to contact you to provide feedback about your Web site.

As much as possible, sweat the small stuff.

Look at your Web traffic.

Web traffic reports can be misleading if they are not used carefully, and they are not always a perfect measure of success. Depending on your organization and its mission, you might have more reason to celebrate one or two important listserv sign-ups than a couple thousand page views. Sometimes, a poorly designed site can get more traffic just because it takes more mouse clicks for visitors to find what they’re looking for. (Think of the last time you spent an eternity on an especially bad government Web site and how much traffic your frustration generated.) On the other hand, traffic stats can sometimes provide important insight into how to better promote some site features, and might even reveal some successes you were not aware of. The stats might also embolden you to eliminate some features that are not popular with your users.

Do not discount unintended audiences.

Are you getting a lot of listserv sign-ups from people with whom you never expected to communicate? That might tell you something about the content you are offering. In any case, remember that those unintended audiences can sometimes lead you to your intended audience. People are complicated and have varied interests: you never know when someone who does not fit the mold of your target audience might in some way take an action — referring you to a colleague, posting a blog entry about your site — that might help more of your intended audience find you.

What Now?

It can take some effort, initially, to get into the habit of demanding that your Web site do valuable work for your organization and its audience. If you’re not sure where to start, try selecting one part of your Web site — or even one part of a page — and take a step to improve it. Solicit input from colleagues, finding out from them if there are ways it might better serve your visitors. (Interns are a great source of input, too: because they’re probably leaving in three months, they can be honest.)

Meanwhile, consider deleting or downsizing low-value features on your Web site. Is part of your Web site getting very little traffic? Is there a page that no one in your office seems interested in maintaining? If you can’t bear to remove it permanently, tell yourself you’ll take it offline for a month. Don’t leave a note: if people clamor for the missing page, you can always put it back in a month. If no one notices it’s gone, forget it was ever there — and concentrate on improving something else.

Tuesday, November 20th, 2007

I’ve built upwards of a dozen sites using Xaraya and a few using Drupal.

Most of my experience with Drupal came a couple years ago, but I’ve been messing with it a bit lately to see where things stand with its development. I’m finding that Drupal’s theming and user management are much improved from a couple years ago and are now just about on par with Xaraya.

I still have a slight preference for Xaraya, in part because it does some things in its core for which Drupal requires add-ons. Also, Xaraya has been doing those particular things — flexible template-based theming and granular user privileges — for a little longer. That’s not a knock on Drupal, which strikes me as a very good CMS these days. I just tend to favor something that’s built from the ground up to do what I want.

Though theming in Drupal is — with the advent of CCK and contemplate — apparently just as flexible as Xaraya’s blocklayout system, I find Xaraya’s XML template code more readable than the PHP in Drupal’s templates. Since I spend a lot of time looking at code, the readability of templates can impact how easy it is to do my job, and the likelihood of mistakes. Also, the less I have to type, the better.

Just to provide a very basic example, I find this…

#$title#

…nicer to look at than this…

<?php print($title); ?>

The advantage becomes more significant when templates are complicated and contain conditional logic, loops, etc.

Here’s a slightly longer comparison, though still pretty simple:

<xar:if condition="count($this) gt 5">
<p>
<a href="#$the_url#">#$this[0]#</a>
</p>
</xar:if>

vs.

<?php if (count($this) > 5) { ?>
<p>
<a href="<?php $the_url; ?>"><? echo $this[0]; ?></a>
</p>
<?php }; ?>

For me the XML/HTML mix is easier on the eyes than the PHP/HTML mix, especially since the former has less intermingling of angle brackets. Note that in the Xaraya example, PHP functions can be used inside the condition statement. Xaraya uses two-letter comparison operators instead of the normal PHP operators.

See also this related post.

More Xaraya blocklayout syntax examples at www.xaraya.com.

This thread might be a good read for developers interested in finding out more about changes to the blocklayout compiler in Xaraya 2.0. Much of what is described in the thread is over my head. Release of Xaraya 2.0 is still a ways off as of this writing.

Wednesday, November 14th, 2007

It looks like I’ll go ahead and launch this blog. I suspect there will be long stretches of time when I won’t have time to post any updates. When business is brisk, mostly. But who knows. It’s certainly worth trying.

A lot of my clients are people who I have not ever met face to face, and they probably don’t always have much of a sense of what I’m like as a person. I won’t do a lot of blogging of the personal variety here, but perhaps a fuller sense of my thought processes and tendencies may emerge.

And I do occasionally think of things I’d like to say about business, technology, etc, but don’t want to write a long, formal article. Blogging is an excuse to jot some things down more informally that might be relevant to other people’s businesses, organizations, etc. In any case, when you put stuff out there, unintended benefits sometimes accrue.

Wednesday, October 24th, 2007

One of the questions I often see posed on CMS forums is something to the effect of “does it have a lot of modules?” I would tend to prefer a CMS where I can do what I want with as few modules as possible.

And I don’t mean that all the functionality for the CMS is crammed into fewer modules… I just mean I want the modules in a base installation to be powerful & flexible enough to perform a wide variety of content management tasks. That to me is better than a CMS where there are hundreds of extensions I can add.

Why would I care if something has 150 modules or 1500 modules? I’d rather not learn more than 20 or so if I can help it. The more modules you use, the more likely it is that you’re going to run into bugs or use something that isn’t well supported. Also, in the event that someone else needs to take over your work on a project, it’s easier to find someone who is familiar with the core modules and a few others.

Powered by Xaraya