Platform Boundary and Navigation
Understand which layer owns each screen before changing templates or routes.
Public website
This theme owns marketing, pricing, help, documentation, contact, demo, and public legal pages.
Authenticated product
Enterprise Academic Platform owns login, registration, portal routing, dashboards, classroom, reader, replay, incidents, and role authorization. The public theme deliberately does not wrap those screens in a second dashboard shell.
Safe account entry
Start from the generated login or dashboard URL. The plugin resolves the approved role and institution context before rendering the requested workspace.
Sign in to open the relevant workspaceAccount and Membership Onboarding
Registration, email verification, approval, institution mapping, and activation.
Use the correct registration form
Institution administrators, teachers, and students create accounts from the single secure /login/ page and choose their role during registration. Do not reuse one role form for another role.
Separate account creation from membership approval
A WordPress user record and verified email do not by themselves grant institution access. Teacher and student membership requests must be written successfully and approved by an authorized institution administrator.
Diagnose approval failures
Check the active institution administrator assignment, membership table/schema, requested role, institution identifier, license capacity, nonce, capability, and the exact diagnostic record before retrying.
Sign in to open the relevant workspaceInstitution Administrator Operations
Academic structure, people, schedules, content, operations, costs, and governance.
Build academic structure first
Create or verify academic years, classes, groups, subjects, teacher ownership, rosters, and institution-scoped assignments before expecting downstream sessions or content to appear.
Sign in to open the relevant workspaceOperate schedules deliberately
Verify timezone, dates, class, subject, teacher, substitutions, and publication state before relying on timetables, calendars, or live-session discovery.
Sign in to open the relevant workspaceReview controlled operations
Use content review, release controls, cost controls, guardians, support incidents, and data governance only with the institution and permissions intended for the current administrator.
Sign in to open the relevant workspaceTeacher Workflow
Prepare, teach, review, publish, replay, and support learners.
Prepare the session
Confirm the assigned class and subject, scheduled time, teacher ownership, language requirements, content, microphone permission, and provider readiness.
Sign in to open the relevant workspaceUse the teacher live-class route
The canonical teacher navigation uses Live Classes and Sessions. Do not substitute the student Live Classroom route in teacher links or acceptance tests.
Sign in to open the relevant workspacePublish with review evidence
Review source material, summaries, MCQs, assignments, replay visibility, and learner access before treating generated or recorded material as released.
Sign in to open the relevant workspaceStudent and Guardian Access
Role-scoped learning, calendar, replay, support, and progress views.
Student learning routes
Students use the Live Classroom, Content Library, Summaries, MCQs, Questions, Calendar, Replay Library, Support Centre, Support Incidents, and Profile routes permitted by the plugin.
Sign in to open the relevant workspaceMissing content is not always a routing error
Check approval, institution mapping, class assignment, publication, date, replay generation, content audience, and license state before treating an empty view as a broken page.
Sign in to open the relevant workspaceGuardian isolation
Guardians should see only linked learners and the progress, calendar, replay, and incident information permitted by policy. Test unrelated learner and institution access explicitly.
Sign in to open the relevant workspaceLanguages and Live Classroom
Configuration, functional health, consent, browser permissions, and recovery.
Configuration is not functional health
Credentials or settings can exist while a service is unavailable, unauthorized, rate-limited, or returning an empty response. Use authenticated functional probes and record the exact provider evidence.
Sign in to open the relevant workspaceTest the complete path
Validate microphone input, speech capture, transcript, translation, text-to-speech, student playback, consent, selected language codes, reconnect behavior, and the provider fallback independently.
Sign in to open the relevant workspaceCapture reproducible failures
Record role, route, session, institution, browser, device, permission state, provider status, timestamp, expected result, actual result, console error, and network response.
Sign in to open the relevant workspaceBook Conversion and Publishing
Prerequisites, upload, progress, recovery, review, and assignment.
Confirm prerequisites
Verify permission to use the source, supported file type, WordPress and server upload limits, storage, extraction/OCR services, background processing, institution mapping, and the user capability before uploading.
Sign in to open the relevant workspaceExpect visible job states
A conversion should expose meaningful upload, queue, extraction, OCR, structuring, review, completion, and failure states. A silent button or static HTML response requires JavaScript, request, nonce, permission, REST/AJAX, queue, and server-log inspection.
Review before students receive it
Check page and chapter structure, extracted text, formulas and images, language edition, summaries, questions, accessibility, source comparison, publication, and assignment with a real student account.
Sign in to open the relevant workspaceSupport and Release Readiness
Incident evidence, cache discipline, backups, role testing, and acceptance.
Do not debug from a generic administrator account
Use dedicated Institution, Teacher, Student, Guardian, and Super Administrator test accounts. Confirm both permitted and denied routes with clean sessions.
Control caches during release testing
Deploy one theme and one plugin copy, clear WordPress, object, server, CDN, browser, and PHP OPcache layers, save permalinks once, and record the exact versions tested.
Evidence before readiness claims
Static linting cannot prove database writes, email delivery, provider behavior, tenant isolation, live media, background jobs, mobile rendering, accessibility, or Core Web Vitals. Complete the supplied production acceptance matrix.
Sign in to open the relevant workspace