University of Oregon Delta Sigma Phi Website
We designed and developed a website for the University of Oregon Delta Sigma Phi Fraternity in 2014 that allows members and the public to learn more about the fraternity's history and members, as well as keep up on current events with a photo gallery.
Team Members: Carly Hines, Kevin Camacho
Featured Skills: Research, Design, Development
Team Members: Carly Hines, Kevin Camacho
Featured Skills: Research, Design, Development
Research
Competitive Analysis
Our very first step was conducting an informal competitive analysis. We browsed through other fraternity and sorority websites and jotted down things that stood out that we liked or didn't like about each of them. Because there was already an existing site for the one we were creating, we also analyzed it in a slightly more detailed matter, using Nielsen's heuristics as a guide.
Our very first step was conducting an informal competitive analysis. We browsed through other fraternity and sorority websites and jotted down things that stood out that we liked or didn't like about each of them. Because there was already an existing site for the one we were creating, we also analyzed it in a slightly more detailed matter, using Nielsen's heuristics as a guide.
DesignInformation Architecture
The previous website for UO Delta Sigma Phi was poorly organized and overcrowded with information. We analyzed and determined what information was necessary to keep and what we could discard. We sketched an information architecture based on those findings. Theme We used Weebly to put the site together, as they needed a fast and free implementation. We chose a theme and made some small custom design changes to tailor the site to the needs of our users, and to match similar things that we liked from other websites. |
Development
Build
We built the site using Weebly, keeping our Information Architecture and our users in mind. One large problem we ran into was figuring out what to do with pages that didn't have enough content during certain times. For example, the Rush Events page only had a few items when it was not rush season. We ended up combining it with the Why Rush page during that time and simply linking it to the Facebook event page for updates.
We built the site using Weebly, keeping our Information Architecture and our users in mind. One large problem we ran into was figuring out what to do with pages that didn't have enough content during certain times. For example, the Rush Events page only had a few items when it was not rush season. We ended up combining it with the Why Rush page during that time and simply linking it to the Facebook event page for updates.