MITE/Functional descriptions

= Design Principles =

Design should be driven by information architecture, with aesthetics enhancing information architecture. Info architecture(s) should address new and existing members.

Iterations should concentrate first on info architecture and design enhances that architecture.

= About these descriptions =

The following descriptions are "User stories" which are descriptions of the functions of the technology that we will deploy.

We'll attempt to create these descriptions without using lots of technical jargon

First priority is administrator support area:


 * /MITE/Call to action page
 * /MITE/Register for newsletter
 * /MITE/Discussions
 * /MITE/Resources
 * /MITE/Implementation plan templates
 * /MITE/Support Resources
 * /MITE/Content creation with images
 * /MITE/Connecting data to salesforce
 * /MITE/Migrate resource files to Drupal
 * /MITE/Pipeline process

= Roles =

See: MITE/Roles

= Functional Overview =

= Notes on itereation one =

Notes for iteration one:

Forms described at http://docs.google.com/present/edit?id=atccndcxxr2_185fmb8wqhh are implementation plan template, which should be available along with fields

Fields that actually show up in the group:

1. name of member institution 2. web site of institution 3. logo of institution 4. brief description of institution (size, community served, mission) 5. City, State 6. Main contact: first, last, email, phone 7. Learning Management System(s) in use