Magic of Skills
Student skills platform for workshops and courses — catalogue, carts, certificates, calendars, and backend operations for Magic of Skills.
Learning commerce flow
Discover → enrol → attend → certify — workshops as a full product loop.
- Discover Catalogue energy
- Cart Enrolment
- Calendar Schedules
- Attend Workshop ops
- Certify Credentials
- Ops Catalogue backend
The challenge
Skill workshops fail digitally when catalogue, enrolment, payments, and certificates are disconnected. Students need inspiration; operators need attendance and credentialing.
Magic of Skills required a lively learning storefront with real backend control — CLIP/certificate pipelines included.
Without certificate credibility, workshops feel temporary; without catalogue ops, teams cannot ship new programmes quickly.
What we built
We built the MOS PHP platform: courses/workshops catalogue, cart, calendar, certificates, blogs, and backend/controller architecture for ongoing catalogue ops.
Brand logo marks keep the student-facing experience distinctive.
Certificates were treated as products — visual credibility for students and schools.
Platform architecture
Storefront, cart, calendar, certificates, and catalogue ops.
Storefront
Courses and workshops with student-first discovery.
Commerce
Cart and calendar enrolment journeys.
Certificates
Credential visuals treated as product outputs.
Catalogue ops
Backend controllers for continuous programme shipping.
Skills platform diagram
How discovery, enrolment, and credentials share one learning commerce graph.
Student
Ops
AI ready
Certificates stay rule-based; AI personalizes the message around achievement.
Design principles
Student emotion sells discovery; operators still need attendance and credentials.
Emotion sells discovery
Students enrol when the site feels inspiring, not bureaucratic.
Certificates are product
Credentials carry brand weight — treat them that way.
Ops velocity
Catalogue teams must ship workshops without engineering tickets each time.
Deterministic credentials
AI may personalize messages; issuance stays rule-based.
How we approached it
Student emotion matters: the site sells discovery of talent, not bureaucratic enrolment forms.
Operationally we kept controllers/backend conventional so content teams can ship new workshops quickly.
Certificates were treated as products — visual credibility for students and schools.
MOS sits beside QUEST/Campus Coach in EDUACE, so information architecture leaves room for cross-links later.
Calendar and cart were designed as one enrolment story, not disconnected plugins.
Where AI enters — and where it must not
Recommendation potential comes from clean course metadata + attempt/progress records.
Workshop bots and assistants can be grounded on MOS lesson outlines once content is canonical.
Certificate issuance stays deterministic; AI can help personalize messages around achievements.
Analytics on course demand inform which AI-era skills to schedule next.
Technical notes from production
Details that only show up once the season is real.
- Certificates are productized outputs — not afterthought PDFs bolted onto enrolment.
- Conventional PHP controllers keep catalogue velocity high for content teams.
- Cart + calendar share one enrolment narrative to avoid plugin fragmentation.
- IA leaves deliberate room for QUEST / Campus Coach cross-links inside EDUACE.
Delivery & systems
PHP/MySQL learning commerce site with certificate and calendar modules.
Deployment notes for production releases.
Backend controllers tuned for catalogue teams shipping workshops continuously.
Stack
Click a layer — each one maps to a real season responsibility.
Learning commerce
PHP
Courses, workshops, and enrolment storefront.
Brand assets from the live product
Primary mark pulled from the Olympiad codebase — shown once, on the surface it was built for.
Outcomes
- Workshop/course storefront
- Cart and calendar flows
- Certificate experiences
- Backend ops for catalogue teams
- EDUACE-ready cross-link architecture