What Web development pitfalls should nonprofits look out for?

Latest post 09-16-2007 6:21 PM by jasonking. 10 replies.

What Web development pitfalls should nonprofits look out for?

03-01-2007 1:52 PM

In his article Seven Web Development Pitfalls, consultant Chris Steins lists mistakes nonprofits should take care to avoid during the Web-building process.

What Web-development mistakes have you learned from? Is there anything you would add to Steins' list?

RE: What Web development pitfalls should nonprofits look out for?

03-01-2007 5:41 PM

-Re-designing a web site without considering how to preserve your existing traffic can result in a loss of some or most of your traffic or a Traffic-Death Re-design.

-Creating a site without considering the marketing aspect, including search engine optimization, means that you may not have as many visitors as you would like. Plan on allocating some money and/or resources to market your site.

-Don't host with a free service unless you can have your own domain name. Some day you will have your own domain and the move may make your site hard to find for a while. Invest the $8-$15 in a domain name and you also can rely on pernament email addresses for your organization.

-Register you domain name in the name of the organization and have 2-3 different contacts listed. If you miss the domain registration renewal emails, and don't notice that your domain and emails stop working, you could lose your domain forever. If someone wanted to, they could later receive any emails sent to anyone at your old domain by clients, vendors, banks, etc.

-Don't register your domain name with the same company that hosts your site. In the rare case where you have a conflict with your hosting provider, they could hold your site "hostage" if they also control the domain. If you have control of the domain, you could move the site and email accounts while you resolve the dispute.

RE: What Web development pitfalls should nonprofits look out for?

03-01-2007 11:33 PM

Great topic!

- Forms and form entries that DO NOT get stored in a database. Make sure any form entries are stored in a database (instead of your inbox) for easy export into Excel . Then you can simply A. Access the file, cut and paste emails into a group and go. B. Export the addresses for easy mailing. C. Run fancy reports etc. You'll thank your team later when this is in place and you're getting 50 form entries per week.

- NOT using Server Side Includes or similar when creating a larger site. Painful, repetitive tasks await. :-)

- IMHO - Do not mix Frontpage and Dreamweaver code. Start with Dreamweaver. If already in Frontpage...start over.

- Building from scratch what could have been purchased off-the-shelf for 1/2 the price and 1/2 the time to implement. Everything an NP needs has already been built.

- Research the vast array of free tools already provided by your hosting company. You should have free blogs, survey tools, polls, CMS's, bulletin boards, chat rooms, forums, wiki's and more...free of charge in your hosting account.


hth,

.

RE: What Web development pitfalls should nonprofits look out for?

03-12-2007 10:24 PM

I agree completely agree with Marc's reference to Dreamweaver and FrontPage. Avoid the vti_cnf folder(s) and the MSO styles that get applied in every page. This can be a nightmare when migrating a site..

I would also recommend utilizing CSS for the site vs. applying styles to each and every tag on a page...funny how some developers still do this to avoid customizing a CSS document(s).

RE: What Web development pitfalls should nonprofits look out for?

03-16-2007 11:13 AM

What form creation software do you use to have form data land in a database?
Melanie

RE: What Web development pitfalls should nonprofits look out for?

03-20-2007 6:32 PM

I have used FrontPage for the past 9 years. I will probably go with Microsoft's follow-on Expressions Web. Haven't made the leap yet.

RE: What Web development pitfalls should nonprofits look out for?

03-20-2007 6:56 PM

What form creation software do you use to have form data land in a database?

Wuffoo.com writes to Excel.

Coffeecup.com Flash Form creator writes to .txt

hth,

.

RE: What Web development pitfalls should nonprofits look out for?

07-24-2007 4:16 PM

Regarding Christian's comment about re-designing a web site without considering how to preserve your existing traffic, also learn about 301 redirects and how use one to combine traffic from www and non-www domains that point to your Web site.

RE: What Web development pitfalls should nonprofits look out for?

07-26-2007 11:13 AM

Some other pitfalls include developing without a clear idea of requirements, overly detailed requirements and failure to plan for inevitable change. We discuss this in our post Top Five Reasons why Agile Methodology is important for Non-profits which also links to another relevant post by Michael Stein.

RE: What Web development pitfalls should nonprofits look out for?

07-29-2007 5:36 AM

IMHO, the biggest pitfall is not understanding the role plays in the objective of your non-profit.

You need to ask yourself;

[ulist]
* What role will the website play in meeting the objectives of the organisation?
*Which functions can the website assist with (giving ie through PayPal, building a community around your cause)?
*What limitations does the website have?[[/ulist]

Once you understand the role of the website, decisions around which technology to use, what strategy to take with development and what is and is not in scope for website development become much clearer.

The other key pitfall is to distribute web knowledge throughout your non-profit organisation. Things can be great if you have one guru who does everything with the website. However, if that person moves on then the content can become outdated quickly, bugs are not addressed and your web presence, and cause, will suffer. Distribute this knowledge.

Cheers,
Kathy

RE: What Web development pitfalls should nonprofits look out for?

09-16-2007 6:21 PM

Here are web development horror stories that had happened to several of my clients:

A charity's website was designed by a volunteer. The site had a very busy health-related forum. They asked him for the passwords but he said don't worry, it's safe with me. He died unexpectedly the next week. It took 3 months to regain control of the site. Lesson: the charity should purchase domains and hosting and retain all passwords, not the designer.

A new website was built for an educational project. Dreamweaver glitched when asked to delete a single file, deleting both the local and remote versions of all the files on the website. It had to be recreated from scratch. Lesson: make a backup.

An ecumenical organisation's website went live but no-one had checked the spelling in the new logo. The semi-literate graphic designer had carelessly written 'ecumental'. Lesson: proof-read everything.

A website was designed using font tags, tables and style attributes throughout the html on many dozens of pages. When the corporate colours of the organisation changed they had to redesign the whole website. Lesson: using HTML and CSS properly can save you a lot of bother later on.

Jason King
Nonprofit Web Design Blog