OSE Identity Usable Across Websites: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
Line 15: Line 15:


==UI==
==UI==
[[Image:Hover.jpg]]
[[Image:Profile.jpg]]


Once our user data is in a structured format, we can do lots of cool things with it such as...
Once our user data is in a structured format, we can do lots of cool things with it such as...

Revision as of 16:45, 28 July 2011

Outline

We are creating a unified OSE identity usable across websites.

Concepts

Basically, each badge icon corresponds to an aspect of what some intrinsic skill someone has, or has available to contribute to OSE. The key aspect is being able to access this data quickly and assess the important information about people at a glance.


Badges

See Badges for background/ideas.

  • Visit Factor e Farm"
  • True Fan"
  • CAD

UI

Profile.jpg

Once our user data is in a structured format, we can do lots of cool things with it such as...

  • Sea of Faces - Visually see who is involved in what. Great for [team] pages!
  • Badge Percentage breakdown - who has what badge - (and who has what skills)
  • OSE Map Mashup - Think crowdmap, but more like this
  • Skill training / knowledge map game layer in the vein of Khan Academy

But before all this can happen, we have to get our user data into a structured format.

Spreadsheet

Edit

Embed

Form

==Target Websites The goal is an easily embeddable Profile Badge can be placed anywhere.

  • Wiki
  • MAKE Projects,
  • forums,
  • IRC
  • website,
  • microfunding
  • etc...


Migration Pathway Outline

  • Outline requirements
  • UI Mockups / references
  • Get feedback from core web people.
  • Get feedback from everyone and their mother.
  • Define Badges
  • Source icons
  • Send concept outline to Eric Doster at MAKE: Project
  • Cull team culturing data into spreadsheet.
    • Create Google Form for easy data entry.
    • Source manpower by contacting members.
  • Mass create profiles.
  • Port profile data.
  • Cross-post embed to wiki team culturing pages, MAKE: Projects, and forums.
  • Blog about it.
  • Migration


Status

  • Contacted core web people
  • Begun recruitment.
  • Drafted emails.