Assignment brief: student survival hub
All names, places, dates, source notes, and costs in this project pack are fictional teaching material. They are not real campus advice or research evidence.
The situation
New students at Example University struggle to find useful study information. Your group will publish a small, accessible hub that helps a student decide what to do next without hunting through multiple chats.
The deadline is Friday at 8 pm, not Thursday. This brief is authoritative when the meeting notes disagree.
Required outcome
- A MkDocs site published with GitHub Pages.
- A short campus-resource guide that clearly labels fictional information.
- A browser-side JavaScript study planner that allocates a chosen number of whole study minutes across unfinished tasks.
- Clear empty and invalid-input states, labelled controls, and keyboard access.
- A reviewed contribution and evidence of checks.
The starter divides time equally across a task count. Your coding contribution introduces named tasks and completion status. Minutes may differ by one to avoid losing time to rounding. All-completed input needs an explicit message, not an invalid calculation.
Constraints
- Use Markdown, MkDocs configuration, CSS, and plain JavaScript. No backend.
- No accounts, real student data, tracking, paid APIs, or new framework.
- No requirement to use a particular Copilot model or paid feature.
- Keep the working starter usable while improving it.
- Put decisions and review evidence in issues and pull requests.
Team
| Person | Responsibility | Availability |
|---|---|---|
| Alex | Planner implementation | Classes, then a 5-7 pm shift |
| Jo | Guide and content | Available at lunch |
| Riley | Budget recommendation | Available in the afternoon |
| Sam | Independent review | Available after 7 pm |
Participants can play more than one role in pairs.
Review criteria
| Criterion | Evidence |
|---|---|
| Useful | A new student can complete the intended task |
| Correct | Calculations and factual claims have explicit checks |
| Understandable | The author can explain their contribution |
| Accessible | Labels, keyboard use, readable text, and clear feedback |
| Collaborative | Issue, scoped changes, review, and handoff |
| Responsible | Fictional data labelled; AI assistance disclosed as required |
Stretch work, not required today
Priority-weighted allocation, additional resource categories, or improved styling. Do not let these delay a working reviewed contribution.