DrupalEd features wishlist

Firstly, a mega-thanks to the people who have taken DrupaEd so far already.

It was a snap to install and configure, and includes a heap of "quick-start" features.

DrupaEd is already a mix of modules and content, so why not take it further?

I'm posting this to the group to provoke some thought.

Here are some features on my wish list:

A school (email) newsletter (Simple News for example) for distribution to anyone who subscribes (either public or member).

A school "Acceptable Usage Policy" page, and enforcement via registration page, this can be achieved with the Drupal Legal module (http://drupal.org/project/legal), and configured for any relevant roles.

A school "About Us" page, perhaps a hierarchy of Book Pages, containing boilerplate content for the most typical pages a school would require. Examples include:

• "Welcome from the Principal" page.
• School moto, vision, mission, philosophy, credo, ...

• School location, map (GMap?), office contact details.

• Enrollment information (and query form)

• Financial information (fees, concessions, grants, allowances)

Most schools include some typical community groups, which could be set up as sample groups:

• Parents & Friends (or regional equivalent)
• Student Representative Council (SRC)
• Sports teams and other interest groups
• Old Scholars and Alumni - a group for ex-students.

Preset Helptip (http://drupal.org/project/helptip) content for all admin/creation/editing forms, all content-types, and all installed features, fully pre-configured (remove context sensitive help from the page and put it in a block).

Preset vocabularies/views to classify content based on a subject, year, and grade.

A school usually includes some kind of organizational hierarchy, with staff usually associated with only one or two particular sub-groups within this hierarchy.

DrupalEd is quite "flat", with all groups sharing the same root level, is their a way (other than Taxonomy) to present the Groups in sub sets, or within a tree hierarchy?

This is one feature we haven't worked out yet and would love some input on. A particular application of this we need is a parent/teacher/student private group for each student, where a feedback channel could develop (potentially the BEST real world benefit of entire website).

All these features are "frills", I know, but they would add to the value of DrupaEd, and would make the distribution better (IMHO).

It is quicker to "edit" than "write", so including boilerplate content has value for many people.

Sample content could be easily isolated (and purged) by tagging it with an "installation" vocabulary listing terms like: primary, secondary, college, university, community, administration, or whatever is relevant.

Sorry for length of my post, I'm full-o-beans and hopeless at self editing, what are the thoughts of those that read this far?