Search for sites, join them, and more!

Added by Nathan Pearson, last edited by Nathan Pearson on Apr 28, 2008  (view change)

See how sites are managed using the Sites widget and tool.

Topics covered in this design include:

  • Searching for sites
  • Joining sites
  • Editing or managing "my sites"
  • Two alternative concepts for sites searching and joining
  • Understanding some fundamental interaction design patterns (hub model)
  • Seeing the relationship between The Site, Widgets, and Tools


To learn more, take a look at this week's flash presentation.


Companion screens below:

Not sure why the gallery function displays the images in a backwards order, but I numbered them in order of how they're presented in the video. Hope this helps.

10
9
8
7
6
5
4
3
2
1

Labels

cle1_designs cle1_designs Delete
cle_improve cle_improve Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (2)

 

  1. Apr 29, 2008

    Mathieu Plourde says:

    Hi Nathan, I have nothing to say but "Excellent Job". I really like the fact th...

    Hi Nathan,

    I have nothing to say but "Excellent Job". I really like the fact that the whole screen is used to browse through the sites. When you have too much "widgetry" happening, it gets confusing.

    The idea of searching and filtering is excellent too. But for my institution, we will mostly rely on the course numbers, so instead of an alphabetical index at the top, we would probably need the list of the acronyms of our colleges and departments, or programs. So if this navigation structure would be customizable, it would be great (even if it's only for administrators, since our courses will be populated by our SIS and that we are not planning on using project sites for a while).

    Mathieu

    1. Apr 30, 2008

      Nathan Pearson says:

      That makes sense. Ideally, I'd like to see features like that carved up into mod...

      That makes sense. Ideally, I'd like to see features like that carved up into modules (or "add-ons") that can be plugged into (or out of) the system. That way, folks can dream up all sorts of enhancements, package the functionality into a module container, and share that with the community. If some other campus has similar needs, they could use it or make minor tweaks.

      On some level, I'm viewing all the work I do through this type of lens – "what can be modularized?"

      It's hard to spend time sharing all those ideas though