By Vinitha Nair on April 10, 2008 4:47 PM
| Permalink
|
Comments (0)
Hey, Anna and the rest of the NML team,
I'm attaching several docs to this blog for feedback. The more Russ and I brainstormed the info architecture, the separation between user (ie member who registers an account - w/ NML staff as alpha testers) and visitor became more apparent. For the purposes of the LL group, these docs represent the data flow for a user- anyone who interacts, participates, and manipulates the LL will need to create an account.
I completely agree with starting from a skill because it is a logical
launch point for any element, and the more we brainstormed the more it
allowed for some sense of structure but also kept it fluid. Here is a flowchart to show basic info flow:
flowchart_nml0408.pdfBelow is a VERY rough LL interface but don't look at it for
visual or graphical appeal. It was more to give you a sense of how
elements can interact with each other but with tying to a particular skill keeping in context the non-linear/nodal search features you
wanted. The 'nodes' themselves could be much more graphically themed,
or iconic. The idea is really that the search is less 'random' but
doesn't feel that way to the user. This same interface will be used
for both a 'visitor' who wants to explore the site, as well as the
member, the main difference is that the member will be able to
participate with the elements (or destination pages) they select from
the search.
It looks like we are moving away from the concept of a structured module and more
a more exploratory way for teens to experience the LL.
Next are a couple of wireframes for a Member Profile. The first is a general page, and the second shows an example of what would appear prompted by the Search Skills option.
wireframe_memberprofile.pdfwireframe_memberprofile_search.pdfBelow is the element paper mock-up using "Blog" as an example. It doesn't have to be overcomplicated but each element will need its own page with instructions to the user. The 1st page has the questions and requirements for each element based on our last conversation, 2nd and 3rd page should be more helpful in organizing content around an element. This doc only reflects the option for element "Blog".
PH1-CMS_Elements0408.pdfBelow are the wireframes for the Create an Element page...
wireframe_elements.pdfwireframe_elements_blog.pdfI also had the idea of scaling knowledge around the four c's so that students see this as a process...
Step 1 - Connect: It all starts with a connection! Register to be a member...
Step 2 - Communicate: Post your opinions on someone's elements [can think of a better word later..]
Step 3 - Create: Develop your own elements, remix from existing elements, etc...
[Russ wanted me to break this into two sub-sections - a) Create elements, and b) Create activities for the more advanced, or perhaps for the in-classroom settings ie adult-supervised. Neither of us felt a teen would create offline activities on their own, but that could be something to run by a focus group.]
Step 4: Collaborate: Share with the community!
[This is where we can talk further about integrating a user's created element with social networks, or creating widgets, etc.]
Russ and I are brainstorming the tech pieces and will have more on that soon. We, and I suppose like you all, are still mulling over the "Activities"- meaning where to house them, who gets to create them, why they would, and how that gets displayed.
