You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HELPq was originally built for [HackMIT](https://hackmit.org), but has been used at hackathons like [Blueprint](http://blueprint.hackmit.org), [Meteor Summer Hackathon 2015](http://meteorhack.meteor.com/), [WHACK](http://wellesleyhacks.org/), [MakeMIT](http://makemit.org/) and [WildHacks](http://wildhacks.org/) (among others!).
12
10
13
11
It is a real-time help queue and mentor management application, targeted at hackathons and classrooms, where there is a need for issues to be claimed and satisfied within minutes. It includes a simple interface for requesting tickets, claiming tickets, administrating users/mentors, and examining metrics.
14
12
15
-
16
13
It is built with an emphasis on three fundamental user experiences:
17
14
18
15
### Keep it simple
@@ -27,8 +24,7 @@ Mentors should not receive any type of push notifications when tickets are reque
27
24
28
25
Mentors can claim tickets, complete tickets, or choose to reopen them. Mentors can only claim a single ticket at any given time. There is no ability to message a student through the app in order to encourage a mentor to find that student and help them in person. A student can, however, choose to include other contact information in case contact is needed to clarify location.
29
26
30
-
Features
31
-
---------
27
+
## Features
32
28
33
29
### Home
34
30
@@ -60,7 +56,6 @@ Mentors should be mobile, and the HELPq is designed for mentors to browse the he
60
56
61
57
If a user is a mentor, they will have an inbox icon in the top right they can click to navigate to the mentor view. If the HELPq is being viewed on mobile or a very narrow window, the app is responsive and will pull up a navigation bar on the bottom for Home, Mentor, and Profile.
62
58
63
-
64
59
#### Claim
65
60
66
61
You can claim a ticket by selecting "Claim Ticket". This will notify the user that you are on your way! Once a ticket is claimed, you cannot claim another ticket unless you complete or reopen the ticket.
@@ -122,36 +117,30 @@ The feedback section is a feed of all mentor feedback, with star rating and a no
122
117
123
118
Settings allows you to adjust various settings in the queue. Right now, you can open/close the queue and set the time for when tickets expire.
124
119
125
-
126
-
Usage Data
127
-
----------
120
+
## Usage Data
128
121
129
122
We've used this at a bunch of hackathons and we have some data on them :)
130
123
131
-
| Hackathon | Date | Response time average | median | stddev | Completion Time average | median | stddev | Rating Average | Users | Mentors | Tickets|
When deploying to Heroku, you **must** set at least the `ROOT_URL` and `ADMIN_PASSWORD` environment variables.
157
146
@@ -170,8 +159,8 @@ Copy the `private/config.json.template` into `private/config.json`
170
159
meteor
171
160
```
172
161
173
-
Deploy
174
-
------
162
+
## Deploy
163
+
175
164
**IMPORTANT**
176
165
177
166
Without login configuration, you will only be able to login with the admin username and password specified in `private/config.json` (or the corresponding environment variables).
@@ -182,8 +171,7 @@ If you're not using Heroku, you can deploy with:
182
171
meteor deploy <your domain name>.meteor.com
183
172
```
184
173
185
-
Configuration
186
-
-------------
174
+
## Configuration
187
175
188
176
#### Login
189
177
@@ -205,17 +193,14 @@ To edit copy, edit `lib/constants.js`.
205
193
206
194
In this file, you will find a place where you can change various strings across the site, including the title of your app.
207
195
208
-
Orientation
209
-
-----------
196
+
## Orientation
210
197
211
198
The queue has been found to be most effective with an orientation with mentors and a tight integration with the way a hackathon/classroom manages mentorship. If you'd like to talk about how this could work for your hackathon/classroom, don't hesitate to email me at [[email protected]](mailto:[email protected])!
212
199
213
-
Feedback
214
-
--------
200
+
## Feedback
215
201
216
202
Have you used HELPq or are planning to use it at your hackathon? I'd love to hear how effective it was, what kinds of metrics you got, and what kinds of things people wanted. Don't hesitate to email me at [[email protected]](mailto:[email protected])!
217
203
218
-
Contributing
219
-
------------
204
+
## Contributing
220
205
221
206
I'd love to take pull requests! Please read the [Contributing Guide](CONTRIBUTING.md) first!
0 commit comments