1 / 10

Whatcom Villages website

Whatcom Villages website. Requirements Purpose: Provide organization visibility for active and prospective members Serve as an alternative to email attachments Allow for dynamic content Provide easy posting access for designated people Need it yesterday. Other considerations.

warner
Download Presentation

Whatcom Villages website

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Whatcom Villages website • Requirements • Purpose: • Provide organization visibility for active and prospective members • Serve as an alternative to email attachments • Allow for dynamic content • Provide easy posting access for designated people • Need it yesterday

  2. Other considerations • Content management – definition needed • What types (size, format, limits?) • Organization contact information • Allow comments? • Provide for user registration/login?(see Lincoln Park Village user form) • Individual contacts? • Data collection? • Maintenance, maintenance, maintenance!

  3. Other considerations • URL (domain name registration) • Hosting • Development • Designer(s) • Developer(s) • Tools • Budget • Growth plan • Maintenance, maintenance, maintenance!

  4. Options considered • Build a page on an existing website – Whatcom County Council on Agingor • Build our own stand-alone websiteor • Build a page on a social media website (Facebook, Google+) – will limit audience

  5. Page on WCCOA website • Pros: • Existing website. No need to start from scratch. • Decisions about tools already set. • Probably fast to launch, but depends on host requirements. • May not have to depend on volunteers. • Professional IT staff (possibly). • Familiar site for users to find.

  6. Page on WCCOA website • Cons: (more research needed to confirm) • Need to work with existing development structure • Possible developer cost (shared with WCCOA?) • Development standards • Need to look like WCCOA site? • Development tool(s) unfamiliar • Coordination needed to launch • Navigation • Inconsistent display between browsers (and sessions) • Limited accessibility • Coordination for content management? • Ongoing support • Cost? • Availability? • Process?

  7. Stand-alone Page • Assumptions: • Use WordPress-like tool • Own URL (domain name) • Own identity (look and feel) • Information dissemination only, to start (e.g., no user comments) • Evolve more features gradually

  8. Stand-alone Page • Pros: • Volunteer help may be available from WCC’s WordPress classes • Fast learning curve • Complete independence of identity • Flexibility for evolving the site • Provide own maintenance

  9. Stand-alone Page • Cons: • Content manager(s) have to learn WordPress (we’re told this is not difficult) • Responsible for own design, development • Responsible for monitoring user input • Responsible for own maintenance and support • Person responsible unavailable, sick, etc? • Dependent on semi-technical volunteer help • Monthly and annual ISP charges

  10. Techsoup.org: A Nonprofit’s Guide to Building Websites • http://www.techsoup.org/support/articles-and-how-tos/nonprofits-guide-to-building-simple-low-cost-websites • Steps: • Register domain name • Evaluate needs: • Purpose • Resources available • Maintenance • Tools • Graphic design (style guide?) • Anticipate future needs • Pick a development tool • Contract with a hosting site • Blogging software? • Integrate site with existing tools (database)

More Related