CourseUp design guidelines
- Non-programming language features must be usable by non-programmers
- Output must be structured and parsable by screen readers
- Language must be portable and independent of underlying implementation
- Dependencies must be supplied or have long-term API support
CourseUp planned features
- Define date format handling
- Improve condition and variable handling
- Improve handling of math-mode guards
- Add styling support for calendar
- Mark breaks
- Show weeks
- Use calendar grid
- Highlight due dates
- Update database backend
- Calendar as datasource
- Automatic homework solution reveal
- Support queries from nearby pages
- Define roster API
- Add support for LDAP/AD roster queries
- Add support for custom roster updates
- Add support for input from students
- HTML forms
- Datastore backend
- Enable coursewide messaging
- Datastore backend
- Support threads?
- Support linking to page elements
- Fade inactive messages
- Add gradebook capabilities
- Automatically add assignments to gradebook
- Allow instructors to assign grade
- Add support for rubrics