Each feature should basically be seen as one task, and we should focus on one task at a time. The sub tasks below each feature are just there to explain total work associated with it.
These are in no particular order.
Flesh out all the necessary functionality to make Alex's job easier.
ETA: 1 day
- Users Panel: More advanced sorting, more advanced searching, match information displayed on old dashboard.
This basically applies to any section under the /members/mock_interviews
module.
ETA: ~3 days
- Ensure an in-progress interview starts back up at the correct question.
- Extract a reusable
FlashPlayerJavascript module. - Refactor the Javascript (pretty close to a re-write of the whole thing).
ETA: ~1 day
- Load
Other Videossection without reload the page. - Improve comments display.
- Add emails alerts for commenters.
This is a lot of stuff rolled into one but they're all related to each other.
ETA: ~4 days (don't know though really)
-
Account Management: Includes adding functionality like renewing subscriptions, editing billing info and deleting their account from their account page.
-
Authorization: The basic premise is that we require a user to have access to the site, either as a free plan or as a user who is paid through a certain date. Users whose access has expired (maybe a subscription wasn't paid in full), would not be allowed access and would be taken straight to their billing/subscription page. Other things:
-
Billing Info: Allow users access to view previous invoices, refunds, etc. we would track all billing activity and show it to them. I think this was done in the first version but never displayed to the user. Not sure.
Either keen.io or kissmetrics.
My thoughts are that keen.io would be the best way to go for tracking custom, internal events for users like reading an article, watching or recording a video, whether the user had a paid or free account, etc. The ability to get customized reports is much more advance on that service. KISSmetrics seems more like a tool to track marketing results... but both could be implemented I think.
ETA: 1/2 day
Ensures that the signup page never has to be reloaded and is essentially one form. This would also include possibly designing a responsive signup form and adding some new Javascsript.
ETA: ~1 day
This would save resources on the current application server and make it easier to manage changes to the blog without having to worry about affects on the Big Interview application.
ETA ~1 day
Includes saving information like User A logged in on 7/31/14 or Admin B refunded User C. This may not be necessary for users but we may want this for
new admins you hire. The need for this could also be replaced by custom analytics.
ETA: ~1 days
Filters out what an administrator with access to biginterview.com/admin can or
can't do.
ETA: ~2 days