WordPress for Government Websites
Upcoming SlideShare
Loading in...5
×
 

WordPress for Government Websites

on

  • 1,942 views

As of release 3.0, WordPress is ready to serve small government websites. Communities could save thousands of dollars per year opting for WordPress over other choices for their site's content ...

As of release 3.0, WordPress is ready to serve small government websites. Communities could save thousands of dollars per year opting for WordPress over other choices for their site's content management system.

Statistics

Views

Total Views
1,942
Views on SlideShare
1,930
Embed Views
12

Actions

Likes
2
Downloads
17
Comments
0

2 Embeds 12

http://planningtech.pbworks.com 11
https://twitter.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

WordPress for Government Websites WordPress for Government Websites Presentation Transcript

  • WordPress for Government Websites?!
    • MCP @ MIT
    • BA UPD @ UMKC
    • Planning Tech @ UMKC
    • Geek @ Luminopolis
    Jase Wilson
  • What’s this about?
    • A. Managing small gov. websites
    • B. Time & money
  • The Problem
    • Govs. need more web services
    • Info needs to be managed
    • Dwindling Budgets
  • Options for maintaining small gov. websites
    • No CMS*
      • Hand code all content
      • Can be useful for very small, simple sites
      • Impractical @ 10+ pages
    *(content management system)
  • Options for maintaining small gov. websites
    • One-off CMS
      • AKA “roll your own”
      • Custom CRUD (& possibly GUI)
      • Made in-house or by contractor
      • Useful in very unique situations
      • Unwise for most: abundant simpler options
  • Options for maintaining small gov. websites
    • Language Framework CMS
      • Similar to one-off
      • Begins with a broadly distributed skeleton system
      • (Rails, Django, CakePHP, etc. etc.)
      • Good choice for enormous entities / complex sites
      • Impractical for all but largest gov. organizations
  • Options for maintaining small gov. websites
    • Proprietary / Vendor CMS
      • Already built, ready to tailor
      • (Ektron, CivicPlus, etc.)
      • Purchased or SaaS
      • Can be extremely costly
      • Sometimes slow innovation pace
      • Risk of vendor lock-in
  • Options for maintaining small gov. websites
    • Open Source CMS
      • Already built, ready to tailor
      • (Drupal, WordPress, etc.)
      • Core is free
      • Extensible (large communities of contributors)
      • Increasingly wise choice for small & mid gov. orgs
      • Of the people, by the people, for the people
  • Drupal
    • de facto OS CMS for federal government
    • (whitehouse.gov, SBA, many others)
    • extremely competent
    • powerful when used correctly
    Open Source CMS choices for government
  • WordPress?
    • Started as blogging engine
    • As of latest major release (Feb 23, 2011), Full blown CMS
    Open Source CMS choices for government
  • Joomla Textpattern Cushy Silverstripe Frog etc., etc... etc., etc... etc., etc... etc., etc... etc., etc... etc., etc... Open Source CMS choices for government
  • Open Source CMS choices for government Sometimes, you just need a kitten. vs.
  • By the numbers: market share
  • By the numbers: usable hooks* *hook = function endpoint for integrating extensions WordPress exposed hooks from v 1.2.1 to v 3.1 Drupal 7: 267 WordPress 3.1: 1469 http://adambrown.info/p/wp_hooks http://bit.ly/dIPaBFg Graph Source: http://adambrown.info/p/wp_hooks
  • By the numbers: installations Graph Source: Jen Lampton, “Why WordPress is Better Than Drupal, Developers Take Note” (July, 2010) http://slidesha.re/917HF0 (excludes WP.com)
  • By the numbers: registered extensions Graph Source: Jen Lampton, “Why WordPress is Better Than Drupal, Developers Take Note” (July, 2010) http://slidesha.re/917HF0
  • By the numbers: registered themes Graph Source: Jen Lampton, “Why WordPress is Better Than Drupal, Developers Take Note” (July, 2010) http://slidesha.re/917HF0
  • By the numbers: community size Graph Source: Jen Lampton, “Why WordPress is Better Than Drupal, Developers Take Note” (July, 2010) http://slidesha.re/917HF0 # of people in the community
  • Still a kitten?
  • More != Better
    • Although there are some advantages to scale:
    • More members = more knowledge & support
    • More users = easier to hire maintainer
    • More hooks = greater flexibility (in the long run)
    It’s true:
    • Simpler setup & maintenance = less $
    • Big community = more managers in labor pool
    • Less moving parts = less things that can go wrong
    • Intuitive workflow = increased productivity
    • Platform agnostic = runs anywhere (even IIS!)
    • Tons of hooks = integration with other services
    • Perhaps most significant of all...
    So, Why WP?
  • So, Why WP?
    • It’s made for communities!!!
    • - powerful threaded commenting engine in core
    • - multiuser, multisite out of the box
    • - user levels, from superadmin to subscriber
    • - dozens of forks & plugins for forums (bbPress, buddyPress, p2, etc.)
  • When WP?
    • * Local gov. sites for populations < ~50,000
    • * Special neighborhood / community sites
    • * Planning sites!
  • Resources
    • Download core, plugins, themes http://wordpress.org
    • Extend http://codex.wordpress.org/Plugin_API
    • Hooks database (by Adam Brown) http://adambrown.info/p/wp_hooks
    • Help from advanced users http://wordpress.stackexchange.com
  • Thanks
    • ? & !
    • [email_address]
    • @luminopolis