THEORY: When design is agile, we’ve produced “less than” and not taken too many ideas into the mix, stayed within or below scope, waited for users to respond to product, not overdeveloped before getting user information.
For example, the previous website was a Joomla! build from former developer, heavy and not accessible by anyone who didn’t know the Joomla! CMS [not that the designer was willing to share a login, but anyway].
How was this development agile?
- The first web presence implementation was just one HTML page [no screenshot available] — just getting the Save The Date and conference theme “out there” [and collecting SEO on the URL]
- Second was Twenty10 WP theme [the default theme] with a header and a few pages — just getting the Call for Submissions forms up and public without any major design work
- Third implementation of WP Page Lines framework theme with more design, bells n whistles — adding in pages that were requested, more attractive design, and integrating social media presence.
Non-agile ideas that were researched and discarded:
- Implement BuddyPress and create a site where users can interact
- Proposed theme: Custom Community – http://themekraft.com/forums and http://wordpress.org/extend/themes/custom-community