sot-skills-report's Introduction

'Summer of Tech' Skills Report Challenge

This github project was created to support and centralize the efforts of the group taking on the Skills Report challenge at the August 2015 Wellington Data for Good meetup.

Group notes on Google Docs.

Please ask @widged for the sharing link if you are part of Wellington Data for Good and keen to contribute.

Install dependencies

cd SOT-skills-report
npm install

Test

cd SOT-skills-report
npm run unittest

Deploy (transpile to es5)

Babel and webpack are used for transpiling. Instructions on how to install webpack and babel can be found at: http://www.2ality.com/2015/04/webpack-es6.html

cd SOT-skills-report
webpack
open dist/index.html

sot-skills-report's People

Contributors

Stargazers

Watchers

sot-skills-report's Issues

Write a Design Brief

Pauline and Joseph are taking charge of the design brief. Contact @Sebbenbear (Pauline) if you would like to be part of the discussion.

Things that popped up in the discussion today that can be used as guidelines:

Let’s have bubbles!
Integrate the proposed style with the SoT website redesign (aligned with their brand).
Try to tell a story.
Keep in mind that business owners are the impatient type. The document should tell some story before the user starts interacting with it. There should be a default view, with default options selected for each graph.
Make sure to capture the two aspects that SoT considers critical: (1) give a view of the breadth of skills that students have (you can find a student that fits pretty much any set of criteria) and (2) communicate that students skills are aligned with the demands of businesses (there is a great number of them that possess solid core skills).
Define how the visualisation is expected to influence the user. What do SoT want business owners do after seeing the visualisation, they should sign up, take contact by phone, etc?
Keep it small. The visualisation should not be more than 2 screens long
Be mindful of managing the user’s expectations. If one part of the visualisation is highly interactive, then the user is likely to expect that other parts are as much.
Do some research on the expected primary user.

Questions to consider when researching the primary user:

What is the business pain point (when hiring) .
What are the key reasons the target audience contacts Summer of Tech? Cost? Service? Value?.
How might they resist? How long last their attention span?
What are the major concerns that they express? Good culture fit? Ready to get going (competent). Self starter attitude.