forked from ieb/timetables
-
Notifications
You must be signed in to change notification settings - Fork 0
Roadmap
h4l edited this page Dec 19, 2011
·
2 revisions
This needs to be thought about.
I think a clear description of exactly what we're aiming to achieve with this project is necessary. The currently implied (but not specified) goals seem to be:
- To allow students to access their lecture timetable online
- Through a dedicated website
- Including a view like the printed reporter lecture list
- Through other calendar products they use day to day, e.g. Google Calendar
- To allow students to discover lectures they might be interested in attending, but are not mandatory
(Cambridge rules allowing students to attend any lecture they like, assuming there's sufficient room).
- This is something that sets this apart from most other University timetable projects which would not be concerned with helping people find other lectures.
- To allow staff to manage their own lecture data easily
Perhaps we should write a proposal doc outlining the project?
How long do we have to implement what?
- How much are we going to refactor vs rewrite?
- Should we drop the PHP front end and just have a Python codebase?
- Should we drop the non-js version of the site and rely on progressive enhancement instead?
I (Hal) think we should be wary of being overly JS heavy. It's my view that unless it's done really well, the experience of using the site can suffer. Particularly if it's used for navigation.