Managing your Non-Profit's website


Published on

A presentation given at the Making Links 2008 conference in Melboure. It's an update of the talk I gave at Connecting Up, Brisbane in May 2008.

Published in: Technology, Economy & Finance
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Managing your Non-Profit's website

  1. 1. managing your non-profit organisation’s website Jason King Making Links Conference, Melbourne 2008
  2. 3. be your organisation’s web champion … … every non-profit website needs one
  3. 4. here’s a non-profit website… … that badly needs a champion
  4. 5. you are the admin … … take control of your own website
  5. 6. Manage your own web content with … Joomla! WordPress Drupal Plone … or many, many other CMS !
  6. 7. secure your domain name now… … before someone else does
  7. 8. … and don’t forget to renew it! <ul><li>When their poems disappeared </li></ul><ul><li>to be replaced by something weird, </li></ul><ul><li>belatedly the Poetry Society knew </li></ul><ul><li>that they had forgotten to renew </li></ul><ul><li>their Internet domain; </li></ul><ul><li>and Viagra ads were not quite germane for their new schools poetry campaign. </li></ul>
  8. 9. how do other non-profits use the web? start here: …
  9. 10. think beyond your website… … use social networking to reach people
  10. 11. plan your site’s structure… … sketch a site map
  11. 12. keep your planning lo-tech … … post-it notes don’t crash
  12. 13. Needlepoint is a valid web planning tool
  13. 14. Wireframes help you visualise your site layout. They are done before any graphic design. You can create them easily in PowerPoint
  14. 15. involve staff, trustees, volunteers and clients in planning your site but limit decision-making to a few people (web champion, committee)
  15. 16. write a brief (and try to keep it brief) <ul><li>always have a brief, even for a small project </li></ul><ul><li>refer to it at crucial stages </li></ul><ul><li>concisely detail the functionality you need </li></ul><ul><li>insist that code meets W3C & WAI standards </li></ul><ul><li>include background information, timescales & expectations </li></ul><ul><li>include a basic site map </li></ul><ul><li>ideally, get a techie to help you write it </li></ul>
  16. 17. the brief specified a brochure-style website
  17. 18. Someone suggested adding a blog and forums
  18. 19. what’s essential to this web project? what can wait? What won’t work?
  19. 20. what’s essential to this web project? web 2.0 blog forums ajax maps video plugins kitchen sink FAQs online services widgets feed corporate hymn api what can wait? What won’t work?
  20. 21. Avoid scope creep by getting work signed off at crucial stages
  21. 22. who should build your website?
  22. 23. your trustee’s nephew who’s doing web design as a school project? maybe not
  23. 24. the chap who did a great job installing your network? but who knows little about web design
  24. 25. would a volunteer be suitable for a small project? absolutely, provided they are an experienced web developer
  25. 26. could you design the website yourself? yes, provided you have the skills, but what if you leave the organisation?
  26. 27. should you commission a web developer? how will you find them? how much should you expect to pay?
  27. 28. insist on standards-compliant code <ul><li>A charity’s website was designed using outdated practices: font tags, frames and a table-based layout and style attributes in the html throughout many dozens of pages. Next year, when their corporate identity changed, they had to redesign the entire website. On a better-designed website they could have simply amended the CSS and changed a few images. </li></ul>
  28. 29. Involve staff and clients in testing
  29. 30. test your website for errors <ul><li>HTML: </li></ul><ul><li>CSS: </li></ul><ul><li>Broken links: </li></ul><ul><li>Colour contrast: </li></ul>
  30. 31. guess how many HTML errors?
  31. 32. Four Surprised there are so few errors? Valid HTML is only one aspect of accessibility
  32. 33. Just in case you get run over by… … a Melbourne tram tomorrow
  33. 34. compile a tech folder for your website
  34. 35. what should you record? <ul><li>domain control panel login </li></ul><ul><li>domain renewal date (put in your diary!) </li></ul><ul><li>web hosting control panel login </li></ul><ul><li>FTP details </li></ul><ul><li>CMS logins </li></ul><ul><li>third-party website logins (Google Analytics etc) </li></ul><ul><li>contract and support details </li></ul>
  35. 36. do you backup your website? <ul><li>Whilst uploading new documents to an educational charity’s website, Dreamweaver glitched and deleted both the local and remote copies of the site files. </li></ul><ul><li>A volunteer designed an Internet radio station’s website. After a petty disagreement the volunteer deleted the entire website. </li></ul>
  36. 37. Get a Google Grant <ul><li>Free online advertising for your non-profit using Google AdWords. Apply now because you can wait up to six months! </li></ul>
  37. 38. analyse your web stats … … to help improve your website Notice the sudden rise in visits? That was the result of a Google Grant
  38. 39. managing your non-profit organisation’s website Jason King Making Links Conference, Melbourne 2008 Presentation is available to watch again at Planning your Non-Profit Website’s Development
  39. 40. Thanks <ul><li>to the following users whose use of a Creative Commons license meant I could re-use their photos in this presentation: dannyman, Marco Wessel, Daryl Mitchell, aynne, activeside, daveknapik, iamilk, Sam Knox, vidnar, ardenstreet, maadmob, pingmag, sita puddin pie </li></ul><ul><li>and to Vincent Flanders for bringing the glaucoma website to my attention. </li></ul>