RMCL Official Platform

RMCL needed a professional organizational website that could present services, practice areas, team information, insights, and institutional positioning while allowing internal users to manage selected dynamic content through a controlled admin interface.

The project required both a public-facing marketing layer and a secure CMS-backed content workflow.

The platform was developed as a full-stack Next.js application with a structured public website, database-backed content sections, and an internal admin dashboard.

It uses PostgreSQL with Prisma ORM, server-side validation, authentication workflows, protected mutation routes, and caching strategies to improve maintainability and page performance.

• Public Website

  Service lines, practice areas, team, insights, contact, and institutional profile.

• Admin CMS

  Internal dashboard for managing About and Insights content.

• Authentication

  Cookie-based session authentication with server-side controls.

• Validation

  Zod/schema-based input validation for protected operations.

• Caching

  ISR and database-layer caching to reduce repeated public-page queries.

• Asset Upload

  Controlled upload workflow with MIME filtering, filename sanitization, and path safety.

• Session authentication with controlled admin access
• CSRF-aware mutating routes
• Zod schema validation for input and route payloads
• Defensive input handling and server-side environment configuration
• Asset upload safeguards with MIME filtering
• Path traversal protection and filename sanitization
• Production-oriented safeguards across CMS and public routes

The platform implemented ISR and database-layer caching to reduce repeated database queries for public pages. Public homepage database queries were reduced to a maximum of once every 60 seconds under the caching and revalidation strategy.

• 60s cache revalidation strategy

• Used Next.js App Router for structured routing and server rendering
• Used PostgreSQL and Prisma ORM for CMS-managed content
• Used Zod validation to protect API inputs
• Used session-based authentication for admin access
• Used caching/revalidation to reduce repeated database calls
• Used upload filtering and sanitization for safer asset handling
• Documented deployment and environment variable setup

This project demonstrates practical full-stack development, CMS architecture, database-backed content management, authentication, validation, caching, secure file handling, and production deployment awareness.

• Role-based user management could be expanded
• More automated tests could be added
• CMS audit logs could improve traceability
• Image storage could be moved to object storage for larger-scale deployment
• Monitoring and error tracking could be strengthened