Paper structures
Fold, test and compare
Content system design
Eureka CMS
A curriculum workspace organised around reusable modules and smaller learning morsels, with programme assembly kept visible as content is selected.
- Focus
- Content architecture · CMS UI/UX · Interface study
- Status
- Design concept
01
Design around the unit people reuse.
The source records a shift from a generic hierarchy builder to a module-first workspace. That is the useful product decision: a teammate assembling a programme should be able to find a teaching module and understand its smaller morsels without navigating an abstract organisational tree first.
02
Programme → module → morsel.
Programme
The assembled learning experience: a selection of modules with delivery context such as track, dates and market.
Module
A reusable teaching unit with its own topic, status, ownership and supporting resources.
Morsel
A smaller activity within the module, where practical details and resource links can live.
03
Browse without losing the programme.
A module library and a persistent selection panel support the same task. Search narrows the available material; selected modules remain visible. Try adding and removing the illustrative modules below. On mobile the selection follows the library in normal page flow, avoiding nested scrolling and miniature desktop panels.
Program builder
1 selectedBuild from what works.
Light and shadow
Observe a changing outline
Patterns in nature
Find a rule, then test it
Design a small shelter
Build around a constraint
04
Make responsibility visible, without more clutter.
The documented product includes module ownership, track labels, status and programme history. Those details support different moments: finding material, understanding who maintains it and reviewing a past build. The design approach is to reveal them where they help a decision, rather than give every field equal weight on the dashboard.
05
The structure should disappear into the work.
A successful curriculum tool makes reuse easier than rebuilding from scratch. This study tests the browsing and assembly relationship; it does not replace the source CMS or prove a productivity gain. Validation should follow a real programme-building task, including duplicate content, incomplete resources and changes after a programme has been scheduled.