EduCanvas

template

Theme-driven educational website and content-management starter built with Next.js

Role: Application architecture and full-stack engineering
Scope: Content architecture, authentication, and deployment
Status: Reusable project starter

Problem

Education organizations need familiar public information and publishing workflows, but cloning whole codebases per institution creates drift and costly maintenance.

Constraints

C1
Three institution types and multiple layouts must share behavior without content/theme leakage.
C2
MongoDB, Google OAuth/Drive, and Resend are optional/configured services.
C3
Public read-only defaults must remain usable when database-backed administration is absent.

Architecture

Next.js public/admin routes; feature-owned content/admission/media domain modules; centralized institution and visual-theme configuration/tokens; MongoDB/auth/Drive/email adapters with server-boundary enforcement.

Application shell

Next.js public/admin routes.

Content services

Feature-owned content/admission/media domain modules.

Integrations

Centralized institution and visual-theme configuration/tokens.

Quality

MongoDB/auth/Drive/email adapters with server-boundary enforcement.

Decisions

Split institution identity tokens from layout composition

Split institution identity tokens from layout composition so branding and structure vary independently.

Resolve both themes server-side

Resolve both themes server-side to prevent a fallback-theme flash.

Keep route and feature code shared

Keep route and feature code shared, accepting stronger configuration discipline to avoid forks.

Contribution

Built public education pages and admin publishing workflows.
Implemented institution/layout selection with named themes.
Added MongoDB content/admission storage, Google sign-in/Drive media, and email integration.
Created Playwright coverage, archived prototypes, SEO/social metadata, and deployment docs.

Outcomes

Developers can deploy one starter for three institution categories.
Administrators can publish content and manage enquiries.
Visitors get configured branding/layout on shared routes.
Deployments can fall back to read-only repository defaults where documented.

Product screenshot

Verified stack

Next.js
React
TypeScript
Tailwind CSS
MongoDB
Better Auth
Google Drive API
Resend
REST APIs
Radix UI
Playwright
System Design

Working through something similar?

Share your challenge, scope, and timeline to start a focused conversation.