The demo environment you have access to reflects a major upcoming update to the Constructor platform.
This document explains the key changes you'll encounter — what's different, why it changed, and what it means for your day-to-day use.
Navigation & interface
| Before | After |
|---|---|
| Separate entry points per application (/learn, /teach, /portal) | Single unified entry point for all modules |
| Inconsistent UI and navigation across apps | One consistent interface across all roles |
| Different experience on web and mobile | Aligned experience across web and mobile |
What this means for you: You spend less time finding where to go and more time doing the work.
User management & administration
| Before | After |
|---|---|
| Settings spread across separate modules | All admin settings in one consolidated Settings area |
| Inconsistent experience across admin workflows | Consistent experience across user management, org structure, and platform settings |
| Multiple page transitions for actions like user creation | Faster manual actions — no page transitions |
What this means for you: Managing users, permissions, and organisation settings is faster and easier to navigate. The underlying logic hasn't changed.
Authoring (Prism): workspace
| Before | After |
|---|---|
| Content editing spread across multiple pages and tabs | Editing in a single, continuous workspace |
| Navigation required between steps | No page switching — structure and content visible together |
| Limited visibility of full course structure during editing | Full structure visible at all times |
What this means for you: Building and editing courses requires fewer steps and less back-and-forth.
Authoring (Prism): content creation model
| Before | After |
|---|---|
| All content created in a shared library by default | Content created directly within courses |
| Every asset required a shared library entry | Courses act as the main workspace — content lives where it's created |
| Content visible to other authors automatically | Authors control when and whether content is shared |
What this means for you: Your library stays organised. Content you create for a specific course stays there unless you choose to share it.
Authoring (Prism): content management & reuse
| Before | After |
|---|---|
| All content automatically shared to the library | Content can stay within a course or be explicitly shared |
| Library became cluttered quickly | Easier navigation and filtering |
| Hard to see where content was being used | Track where content is used across courses |
What this means for you: Reusable content stays reusable. Course-specific content stays contained.
Practice (IT & Software / Coding)
| Before | After |
|---|---|
| Separate legacy interfaces for author, admin, and learner | Author, admin, and learner experiences aligned in unified UI |
| Inconsistent experience across roles | Consistent navigation and interaction patterns |
Note: Practice Science Labs and Practice Schools are not included in this demo.
Schedule
| Before | After |
|---|---|
| Legacy interface, separate from other applications | UI aligned with the unified platform |
| Multi-step interactions with manual save | Autosave in settings — no manual save needed |
| Required selecting the term on each screen | Term selection no longer required per screen |
What this means for you: Scheduling workflows are faster and less repetitive.
What isn't changing
Core learning experience — course access and navigation for learners remains familiar
Assessment workflows continue to work as expected
Groups, Practice Schools, and Practice Science Labs are unchanged
All existing content is migrated automatically — no data loss
Questions about what you see in the demo?
Request a walkthrough:
Reply to your onboarding email or contact your Account Owner directly.
Found an issue?
Report it via the Customer Support Portal or by replying to your email thread.
