Sharing Engine/Design Meeting 3

PSE Ttech meet: discussing wireframes and exploring issues therein
10th January 21:00 (UK time)
11th January 08:00 (Australia time)

Jim Kirkpatrick
Laura Whitehead
Ed Mitchell

Next meet:
Technical architecture and build kick off
Wednesday 1st Feb, 20:30 UK time, Thursday 2nd Feb 07:30 Aus time.

Actions

Laura: Get wiki account
Ed: Create widget options page for different widgets descriptions
Ed: Check wireframe docs and send Laura changes
Laura: Update wireframe docs with Ed's changes to detail and adding widget #3, and publish BY Monday 16th Jan
Laura: update measurement requirements wiki page with requirements before next meeting so we can discuss Piwik vs GA
Jim: review and edit project submission IA wiki page following meeting
Jim: work on technical proposal for discussion at next meeting

Topics

Measurement requirements wiki page and add information

Need to use alpha phase to measure the various widget choices and uses so need to pay good attention to this in alpha

Widget options

See widget options page for ongoing work on widget options

Three presentation widget options

1. basic (as stands): chronologically ordered 'latest projects' listing: links back to TN.org
2. tabbed: limited interaction, enable users to search by location or theme, 2 tabs maximum: links back to TN.org
3. full page: richer interaction, include maps and more: users can stay on webmaster's site

All dynamically generated from TN.org website, linked to the webmaster's site, measurable

One data entry widget option

As per the widget outline diagrams (Laura to provide) based on data elements in IA wiki page

Widget design and presentation

Vital to be tough with information presented on widgets and avoid crowding on widget with information
Our own lightweight responsive theme
Widget 2 and data entry widget to be usable as 'apps' on tablet computers and mobile phones
Use existing panels and panes with Javascript presentation (NOT iFrames) - gives us the flexibility in alpha testing to juggle things
Different views and templates for each widget
All widgets to be re-usable for other content types

Wireframes for project browsing in widget

Need to be attractive enough with useful help text to set context and attract users (the widgets are out of their context) into adding their information
All agreed it's what we're after; details to come in Feb

Wireframes for project submission in widget

Two stage approach approved
Plenty of help text needed
Avoid Transition specific language
Details need tweaking - Ed to cover changes
Location discussed as a design challenge - full page widget can use maps, but others can't; how to help users locate their projects?

Using the alpha phase to get best results

with limited number of users, we can afford to use relatively heavy choices (e.g. panes etc.) in order to offer the most options to users and find out what is wanted the most

Management and planning

Ed - laura handover: april - oct
Everyone's availability over 2012
timetable until next webmasters meet
- Feb, Mar: build to alpha
- April, May: test
- June: webmaster meeting
- June, July: build to beta