MaestroMaestro Overview — contents
Reference
Open Questions
The questions the development brief left open for release one. The current direction is recorded here; treat these as confirmed working assumptions unless HBMSU or the-code revise them.
| Question | Current direction |
|---|---|
| Language — English only, or Arabic and English? | English first, Arabic later. Build English for the January release and architect for Arabic/bilingual as a later phase. |
| Accessibility — which standard (e.g. a WCAG level)? | No formal conformance target for release one. Follow good accessibility practice; a formal WCAG target can be adopted later. |
| Devices — must it work on mobile and tablet as well as desktop? | Desktop and tablet for release one. Phone support comes later; design responsively so it isn't a rebuild. |
| Scale — just the January 200–300 cohort, or the whole university? | Engineer to scale university-wide. Build the January cohort on foundations engineered to scale — consistent with the system-of-record-from-day-one direction. |
Note
These four were the explicitly open items in the brief; the answers above reflect the direction confirmed for the documentation. Other items marked "open" elsewhere in these topics — the five Published Course Package items and the Companion's real-time API choice — are tracked in their own topics and will be resolved before the build depends on them.