Malda Portal
62-page institutional web portal for Malda College — academics, administration, facilities — with zero runtime framework overhead.
Counted 2026-09-13 via filesystem: 31 root *.html + 6 cells/* + 5 facilities/* + 20 subjects/* = 62 pages. Older README copy says 50; the filesystem count (62) is authoritative.
01 — Problem
Institutional information scattered across outdated pages with no coherent navigation — courses, faculty, cells, facilities and notices each living in a different visual language.
02 — Solution & Architecture
One information architecture across 62 static pages: 31 root institutional pages (home, admissions, faculty, notices, NAAC/NIRF…), 19 academic subject departments, 6 administrative cells, 5 campus facilities. Pure HTML5 + modern CSS Grid + vanilla JS; token-based CSS custom properties for instant dark/light theming; Nginx, Vercel and Docker packaging.
./ — 31 root pages (index, admissions, faculty, notice-board, naac-iqac, …)
cells/ — 6 (anti-ragging, grievance, internal-complaint, minority, obc, sc-st)
facilities/ — 5 (academic, administrative, digital, human-resource, physical)
subjects/ — 20 (arabic, bca, bengali, botany, …)
assets/ · robots.txt · sitemap.xml · serve.sh03 — Engineering decisions
Why no framework for 62 pages?
Content pages don't need hydration. Static HTML keeps hosting trivial, renders fast on low-end phones, and removes an entire class of runtime failure.
How is theming consistent at this scale?
A CSS custom-properties token hierarchy — one variable change propagates across all 62 pages without rebuilding per-page bundles.
How does it deploy anywhere?
Dual Docker alpine + Nginx configs with gzip and static-asset caching headers — the same directory serves from any static host.
04 — Result
A complete institutional portal a college can actually host: coherent IA, themed design system, sitemap + robots, multi-target deployment. The page count is verifiable with one find command.