MERN Stack CMS

The challenge

Operators needed a documented CMS admin API and React dashboard for content entities—without overselling a full public site or aspirational security features that were never wired. Without a coherent wordpress-inspired cms admin (nestjs + mysql) foundation, MERN Stack CMS stakeholders faced fragmented tools, slow handoffs, and limited visibility—classic failure modes Tekvers designs against.

The solution

MERN Stack CMS: NestJS/TypeORM/MySQL + React CMS admin for posts, pages, menus, media, and comments—named “MERN,” implemented without Express/Mongo. Workable WP-like admin learning/portfolio CMS on NestJS/MySQL. Tekvers delivered a maintainable wordpress-inspired cms admin (nestjs + mysql) system for MERN Stack CMS using NestJS, TypeORM, MySQL, React, with phased rollout, operator workflows, and documentation suited to long-term ownership.

Approach

Deliverables

• ▸NestJS REST API with TypeORM/MySQL and JWT login/register/profile
• ▸React CRA CMS SPA + enhanced admin panel for admin role
• ▸Posts, pages, categories, media, comments, menus/menu-items CRUD
• ▸CMS dashboard stats and admin analytics page (some metrics mocked)
• ▸User CRUD with role field; Swagger `/api/docs`; `/health`
• ▸Dev database seeding (admin user + sample content)
• ▸Documented non-features: public blog theme, password reset, tags, SMTP, 2FA, durable admin settings, server-side RBAC guards

Outcomes

• ▸Workable WP-like admin learning/portfolio CMS on NestJS/MySQL
• ▸Dual admin UX paths for day-to-day CMS vs enhanced admin widgets
• ▸Accurate stack labeling for interviews (Nest + MySQL, not Express + Mongo)

Impact

Stakeholders get a real content back office to demo—without pretending the repo name equals the stack, and without claiming public SEO publishing or production-grade RBAC that source does not enforce.

Tech stack