Internal Preview Summary
Villa College
Digital Campus Rebuild
The Diagnosis
The 2021 platform established Villa College's digital presence. It did not establish institutional control over it. Faculty content routed through marketing. No structured approval existed. No unified API foundation existed for future digital systems. The institution outgrew its own system without a mechanism to correct it.
01What Changed
| Before | Now | |
| Content changes routed through marketing or IT | → | Faculty editors manage their own content directly |
| No approval mechanism before publishing | → | Structured Draft → Review → Approve → Publish workflow |
| Website and future systems built separately | → | Single API layer — all surfaces share one data source |
| No mobile architecture | → | Mobile-ready API foundation — student app connects directly |
| No role separation between faculty and institution | → | Faculties control content. The institution controls standards. |
02What Was Built
Faculty Layer
Content Governance
Faculty editors create, edit, and submit updates. Central editors review and approve. Publishers execute. Each role has an enforced boundary.
Architecture
API-First System
Presentation is separated from data. Website, mobile app, and future platforms all consume the same API. No surface holds its own data logic.
Workflow
Publishing Control
Content moves through defined states. Temporary preview links allow external review without system access. No content publishes without approval.
Public Surface
Rebuilt Website
Programme discovery, faculty pages, news, and events — all driven by the same data layer. Mobile-first. Structured around validated user priorities.
03The Digital Campus Model
Public
Website — course discovery, faculty pages, news, events. The institutional front door.
Student
MyVC + Moodle — existing systems connected via links. Not replaced. Extended.
Faculty
Content Dashboard — the missing layer. Faculty-owned, institution-governed. Built and ready to launch.
Admin
Governance Layer — central editorial control, approval queue, publishing authority.
04Publishing Workflow
1
Draft
›
2
Submit
›
3
Review
›
4
Approve
›
5
Publish
05Walkthroughs
06Production Foundation
Role-based access control
Supabase data layer
Comprehensive test coverage
TypeScript throughout
Mobile-first build
Protected API routes
Error boundaries
RLS enforced
—Current State
Status
Ready to Launch
Working prototype. Live at vc-demo.maldicore.com. Ready for institutional review.
Live Demos
Website
vc-demo.maldicore.comAdmin & Faculty Dashboard
vc-demo.maldicore.com/loginDemo accounts available for all five roles across the workflow.
What This Is Not
Not a proposal. Not a redesign request. Not a feature wishlist. This is a working system that solves the operational gap the 2021 platform left open. The next conversation is about institutional alignment and deployment readiness.