DUE: 11:59pm Tuesday, November 27, 2018 on CCLE.
This snapshot provides an opportunity to share a progress report, wireframes (see below), how well your team is functioning, and any challenges you are facing. Your brief report will help us work with you and your team to resolve challenges and meet any needs expressed.
Requirements for this assignment
Task: Submit 1 project snapshot per team. Write a 2-4 page double-spaced reflection that describes:
- What you have accomplished so far
- How well the team is functioning
- Any challenges you are facing or questions you have
- Anything you need, such as additional training, space for group work, source materials, or anything else you would like to share.
You should also submit a wireframe for each page you plan to include in your site, with headings for each data visualization, map, and section of text. You don’t have to have working maps or visualizations at this point, but please indicate which visualization, mapping, and timeline tools you intend to use, along with the web-publishing technology you plan to use (e.g., WordPress, flat HTML, Jekyll, etc.).
You can submit your wireframes via CCLE in any format you like, as long as we can open it (e.g., PDF, .docx, JPG, etc.).
Francesca Albrezzi, a previous TA for this course, has some very helpful slides with more information about wireframes.
The exact tool you use to make your wireframes doesn’t matter so much: there are dedicated wireframing tools, but a lot of people like to use PowerPoint, or just sketch by hand. Some fancier wireframing tools create clickable HTML prototypes, so people can interact with the site, but we won’t be that elaborate in this class.
If you’d like to use a dedicated wireframing tool, we suggest Balsamiq. Choose the free 30-day trial and export your designs as a PDF.
Here is an example of a very good set of wireframes. These were created with Balsamiq, but they’d be just as good with another tool.
What are wireframes?
Wireframes are a simple (but important!) element of designing the architecture of a website. Think of them as your site’s “skeleton” — boxes that indicate where site content will go, but without the exact text, images, or visualizations. In fact, many designers prefer to leave wireframes as “sketchy” as possible, so that when the team is judging the quality of the information architecture, people aren’t distracted by images or font choices.