Question type coverage
Show every Storybook taxonomy code, plus flashcard, quiz, practice-exam, and LMS workflow extensions.
Teachers should be able to inspect subject, year level, Bloom coverage, question format, validation requirements, and delivery pathway before they trust AI-assisted assessment work.
Show every Storybook taxonomy code, plus flashcard, quiz, practice-exam, and LMS workflow extensions.
Use K-6, Years 7-10, and Years 11/12 examples so buyers see their own school context.
Expose answer checks, rubric requirements, accessibility notes, and curriculum caveats per item type.
This homepage section translates the Storybook question taxonomy into a buyer-facing product surface. It shows how teachers can choose a subject, grade band, and item type, then inspect Bloom coverage, example prompts, validation needs, and LMS-ready workflows.
Choose the best answer from four options.
Year 5 Science: Which material is the best insulator for a lunchbox?
Distractor quality, answer key, syllabus outcome, and reading load.
Objective answers can be checked directly while constructed responses should surface rubric suggestions for teacher approval, override, and annotation.
The public claim should stay bounded to evidence packs, cohort signals, coverage heatmaps, and export candidates until school-facing reports are route-proven.
Practice modes should inherit question taxonomy metadata, spaced-repetition timing, mastery confidence, and teacher release controls.
Exam assembly, course binding, LMS export, and gradebook write-back need separate proof rails before stronger deployment copy is used.
Promote this section with three proof rails: Storybook taxonomy parity, curriculum descriptor coverage, and route-level teacher approval for generated, graded, practised, and LMS-delivered items.
Similar education platforms sell activity breadth, AI prep, accommodations, and analytics. GoHiMark should compete by making those ideas inspectable: show the workflow, show the evidence, and show the boundary before a claim becomes a promise.
AI drafts and rubric suggestions stay behind teacher review, approval, override, and release decisions.
The public builder now maps to the Storybook question taxonomy and exposes question type, Bloom, grade, and validation detail.
ACARA and syllabus language is framed as an alignment workflow until descriptor-level coverage manifests are validated.
Course delivery, gradebook write-back, and reporting are shown as staged integration work with explicit proof gates.
Assessment and classroom platforms lead with many activity types.
GoHiMark should lead with taxonomy depth, validation controls, and teacher approval.
AI teacher tools focus on lesson prep, rubrics, reports, and question generation.
GoHiMark should show prep speed only when paired with review, provenance, and export readiness.
Mature school platforms make learner access and accommodations visible.
GoHiMark should expose accessibility checks per question type and per delivery mode.
LMS and assessment platforms sell insight, not raw charts.
GoHiMark should show evidence packs, intervention candidates, and confidence caveats.
Route buyers from proof center to builder, then from builder to a governed walkthrough request. The sequence is stronger than a generic demo CTA because it lets teachers and procurement inspect the product before a sales conversation.