Segmentation

There is a lot of information to present, and several different types of users who will hit the site, and not all information is relevant to each type of user. It makes the most sense to segment users as early as possible, and then provide focused information to provide a better experience for everyone.

Types of Users

We will work under the assumption that there are three types of users.

• First-time hackers. This would be Penn freshman, Wharton students, and other random people at Penn to whom the concept of a hackathon is new.
• Foreign hackers. Students from other schools, presumably who have attended a hackathon before.
• PennApps veterans. People who have attended PennApps before.

Rookies

First-time hackers need to be taught what a hackathon is to understand that this is a "thing" here at Penn. Emphasis should be placed on legitimacy and any kind of help sessions we might have. (History, the number of people who've attended, and sponsors.)

Questions to answer:

• What is a hackathon?
• What is PennApps?
• Who can go?
• What if I don't know how to code?
• Do I have to be there the whole time?
• Will there be food?
• How much does it cost?

Foreigners

Foreign hackers need to be convinced to come out. For them, we want to emphasize why PennApps is awesome, and point out that travel is free.

• Where is it?
• How far is it?
• How do I get there?
• Why should I go?

Foreigners are going to be the most cautious group. I'm not sure what the numbers were from the last hackathon, but my guess is the most focus should be spent here.

Veterans

The last group, PennApps veterans, is the easiest to target. They already know what's up, and if they went last time they probably will go this time. They only need to know when it is, and what's new.

Questions to answer:

• When is it?
• Is anything new?

General

Everyone needs to know when and where it is. That should probably be the last item.

Note on Sponsors

Sponsors should have a way to get in touch if they're interested. This should probably be in the footer and have its own page.