[JesseK]

Above all, keep it clean and non-invasive. Get approval of the FIRST logo placement to be on the safe side. Get some feedback from Manchester on a mockup if you can if only to ensure they don't not like the idea/design. Since this is you doing it, the majority of their feedback for what to implement should be at your discretion.

Event invitations could be useful, but I wouldn't do it for every regional event -- getting 50+ invitations would be very annoying. Perhaps things like the Championships, RoboProm, championship wrap party, etc, would be more useful so users can pre-plan and further socialize online. If events were created for each regional event, no automated invitations should be done -- users of the application would have to manually sign up.

Specifying between engineering and non-engineering mentors would be helpful (thinking longer term) so that teams who need to reach out for help have a more specific subset of people to talk to.

Optional linking to a chiefdelphi nickname would be useful to find chiefdelphi users (who want to be found) at a regional event. Putting a name to a face really helps move the conversation along sometimes.

==> Lower Priority Features <==
Perhaps put in unofficial polls similar to Slashdot's (e.g. what did we think of X component in KOP, funny ones about chiefdelphi, etc).

A "Design Review" section may be useful for teams that want feedback on designs if they post pictures. Sure, chiefdelphi is a great source for reviews and comments, but very few engineers outside of FIRST even know about chiefdelphi; putting something on facebook may attract these engineers to FIRST and get them interested in starting a team.