VS Code
Editor
TCE Website
The official website of Tontadarya College of Engineering.
Designed as a multi-owner publishing platform that allows departments and central administration to manage public content independently.
The Problem
College websites rarely fail because pages are missing.
They fail because content ownership is unclear.
Updates become bottlenecked.
Departments wait for changes.
Information becomes outdated.
The challenge was designing a system that allowed departments to operate independently without losing institutional consistency.
What I Owned
Information Architecture
Content Ownership Design
Publishing Workflows
System Design
Database Design
Backend
Frontend
Deployment
Tools I Used
The stack used to structure publishing ownership, content workflows, and the public delivery surface.
Git
Version control
GitHub
Repository hosting
npm
Packages
Firebase
Backend platform
Firebase Firestore
Document database
Firebase Storage
File storage
Firebase Auth
Authentication
shadcn/ui
shadcn/ui
UI foundation
Tailwind CSS
Styling
ChatGPT
AI assistant
The System That Interested Me Most
ComplexityHigh
Content Ownership Model
A college is not a single publishing team.
Departments need autonomy.
The institution needs consistency.
The system separates ownership into multiple publishing scopes.
Departments manage their own content.
Institutional structure remains centrally governed.
This allows content to stay current without sacrificing consistency.
College Admin
Department Admin
Faculty Contributors
Public Website
Visual Proof
Homepage
Institution-wide information and cross-department activity presented through a single public experience.
Main Admin Dashboard
Central governance of navigation, departments, users, documents, and public content.
Department Admin Dashboard
Independent publishing space for each department.
Faculty Ordering Interface
Presentation order treated as governed data rather than accidental data.
Document Explorer
A structured document system instead of a flat download page.
Department Homepage
Department-owned content rendered through a shared public structure.
Faculty Self Submission Flow
Decentralized contribution without decentralizing governance.
Systems Designed
ComplexityHigh
Content Ownership Model
Separating central governance from departmental autonomy.
ComplexityMedium
Dynamic Navigation Architecture
Navigation managed as content rather than code.
ComplexityHigh
Cross-Department Publishing
Local updates surfaced through institution-wide discovery.
ComplexityMedium
Document Library Architecture
Nested collections, breadcrumbs, and structured document discovery.
Project Snapshot
Multi-Owner Publishing Platform
Designed around:
Content Ownership
Department Administration
Publishing Workflows
Document Management
Public Discovery
Currently live at tce.ac.in
Next
Interested in operational software and governance systems?
Explore Adrenaline Systems or Hospital Manage.