This repository has been archived by the owner on Sep 2, 2020. It is now read-only.
Wireframes
Note: latest ux/ui posted to wiki/UI Mockups
- Overview
- Landing and Sign On
- Directory
- Account Settings
- Build
- Build Visual
- Assess
- Levels / Milestones
- Help
- User Roles & Issuer Settings
Here is the most up-to-date wireframes for Badgekit.org. As we make modifications, edits and iterations we will edit this wiki so that it reflects the most recent thinking.
These first wireframes give a brief overview of the entire flow, from badge creation to assessment.
- note: Most issuers will display available badges using the API or an embed widget. Action menu could offer link or embed to display a single badge. Discuss top here: #60
next in this flow would be Assess below
- Would be great to have groups. "Moz spring collection" ... "Our orgs"
- Includes Create New Button
- Includes metrics and all the actions
- Share would offer embed code and link to share with potential earners.
- Top of view includes link to info on how to share the whole bunch of badges.
- Sort list of badges below
- Summary of all actions available on badges
- Stats and sparklines. maybe revealed on menu:hover
- preview of a draft, template, or published badge.
- permalink would be nice to share a draft for a viewer among collaborators.
- queue of applications.
- list of awardees
- much like published, but fewer actions on badges
Learn more about Build here
Provides a non-linear approach to building a badge.
- Borders on the visual-metaphor-as-menu could indicate progress.
- A couple of strong examples would be very helpful.
- Core info required by the spec
- I've split description
- i would lock these elements after a badge is published
- Includes options to facilitate badgekit (e.g. groups)
- Includes options that could be elevated later into the spec (e.g. time)
- Note sure if @carlacasilli wants Limits or Unique
- I wouldn't lock these items after a badge is published
- Enables more granular criteria
- Each bit of criteria has some info attached
- Issuer can set more flexible overall requirements
- Collapses nav filters of directory into hamburger
- Should this link back to visual metaphor instead
- Visual side of things still needs more exploration
- Wireframes coming sooon...
- Final preview
Design a badge visuals.
Learn more about Assess here
- This system is still TBD
There are two sides to a Level:
- Level Badge - a meta badge of sorts, automatically queued or issued after someone earns points associated with support badges
- Support Badge - a badge that fulfill the Level's Criteria
- Note: these names are not final
- Define Level Badge
- Set Level points to a standard badge to support Levels
- Mentor/Assessors view of Badge Applicants and their progress toward Levels
- MVP!!
