Drupal in Ed - Group Redesign Specifications

This is a wiki page where we can capture all of our design plans for the new Drupal in Education group. Below are the specifications for the tabs and sub-tabs. Please feel free to edit these, or if you'd rather, comment on them in the Drupal in Ed - Group Redesign Discussion. This design draws heavily on what the Drupal Dojo group did.

Group Page Layout

• Home - single column
  • Custom welcome content block and then
  • Classic OG River of News below it
  • **Recent members**
  • **active discussions / last left comments / something community oriented with posting frequency to highlight active discussions quickly**
• Discussion tab - single column
  • Subtab: All Table (Discussion River of News - table format)
  • Subtab: All Teasers (Discussion River of News - with teasers)
  • Subtab: K-12 Schools
  • Subtab: College/University
• Events tab -
  • Subtab: Calendar
  • Future Events - table starting with next event, sorted soonest to furthest out
  • Past Events - table starting with last event, sorted most recent to oldest
• Polls tab
  • Single column with some custom text on top and a list of polls beneath
• Implementation Resources tab
• Subtab: Case Studies

**I don't think this would be a wiki style since case studies are typically specific to an implementation**

• Subtab: How To/How Do I
• **Subtab: Recommended Projects**
• **Subtab: Project Wishlist**
• **Subtab: Handbook / Help / FAQ**
• Jobs tab
  • Single column with some custom text on top and a list of jobs beneath
• Members tab
  • Recent members
  • Faces subtab
  • Subscribers subtab

Group Tags and Usage Guidelines

Here are a few examples of functionality tags to start:

• Modules - questions/suggestions/recommendations about specific modules
• Themes - questions/suggestions/recommendations about specific themes
• Groups - specific to organic group-related functionality
• LMS - specific to learning management systems
• How To - general purpose questions or suggestions that don't fit the other functionality tags

Target educational environments. If a post applies to all, use the All Environments tag:

• All Environments - for all educational
• K12 - for K-12 education institutions
• College - for college or university settings
• Corporate - for corporate environments
• Nonprofit - for nonprofit environments

Target educational roles. If a post applies to all, use the All Roles tag:

• All Roles - for use by administrators
• Administrator - for use by administrators
• Teacher - for teacher-specific usage/functionality
• Student - for student-specific usage/functionality
• Parent - for parent-specific usage/functionality

Content Types / fields to include (with rationale please)

• Job posting (expand current one)
• Event
  • Region - ability to quickly filter out ones that aren't remotely near you. Break US / large countries down into regions (north east, south west. etc) or state / province. Type: Auto complete
• Discussion (as is)
• Wiki Page (as is)
• Poll (as is)
• Case Study
  • A separate content type for case studies so that they can include specific classification / descriptor fields.
  • Title / Body
  • Target environment Taxonomy
  • Target Role Taxonomy
  • Region (same reason / type as above)
  • Complexity of Implementation: It would be nice to have some kind of level of difficulty associated to things like "How to" and case studies. There are several types of implementations that are EXTREMELY difficult to pull off and knowing what level of proficiency is needed to implement would be very useful. If i'm a newbee I don't want to get all excited about a case study only to realize 2 years was invested in it's development by a team of drupal and server programmers. Select field or taxonomy if we want to expand this
  • Team Size: Able to get a feel for how big the project is based on the number of people involved. Projects churned out of shops are usually easier to implement by other shops whereas single users might have trouble implementing a shop solution. integer
  • Development Time: How long it took to develop and implement this product. text field
  • Estimated implementation time: If it's talking about a release maybe we can capture how long it might take me or you to implement it. Possibly this belongs elsewhere (like in the modules / projects / how to section) text field
  • Organization involved: Ability to see who's putting this case study out there or filter by projects / implementations from a particular source. This could also help give greater visibility to some companies / universities who are pushing a lot of stuff out there in the drupal for education community. auto complete field
  • Projects used in this implementation: This could be a listing of the modules, themes, and installation profiles in used. Whether they are public or private projects it doesn't matter. What would be interesting to see is if there are standard modules / themes that people are using on a regular basis and this would become clear rapidly with something like this. Potentially a free tag based taxonomy so that other things could tag this up
  • Drupal Version: It would also be nice to quickly filter out projects / concepts implemented in 4,5,6 or head for greater search granularity. Select