Admin Panel / Headless CMS
Ali Haider Portfolio — Admin CMS
A schema-driven admin CMS for a dynamic portfolio — 25+ content types, rich text, media library, drafts with autosave, drag-to-reorder and a resume builder.
- React 18
- Vite
- TypeScript
- Tailwind CSS
- TanStack React Query
- TipTap
- React Hook Form
- Zod
- dnd-kit
- NestJS 11
- MongoDB
- JWT

- Client
- Personal project
- Duration
- Jul 2026 — Nov 2026
- Category
- Admin Panel / Headless CMS
The admin side of the portfolio system: a React + Vite CMS that manages every section of the public site. Forms are not hand-built per section — they are generated from a shared definition package, so adding a field to a content type updates the API validation and the admin form together.
Content moves through draft and published states, with fields that are only required at publish time, a draft autosaved every minute, and on-demand revalidation of the public site the moment something is published.
Alongside content it handles a media library, a section manager for ordering and toggling sections, site settings, and a resume builder.
Key features
Forms generated from shared section definitions — one schema drives admin UI and API validation
25+ content types: singletons and collections, repeaters, references, tags, dates, media
TipTap rich text editor with tables, code blocks, highlights, alignment and YouTube embeds
Draft / publish workflow with publish-only required fields and one-minute autosave
Media library with image, video and PDF uploads and alt-text management
Drag-and-drop ordering for records and sections, duplicate and soft delete
Resume builder, site settings and JWT auth with httpOnly cookies and refresh rotation
My role
Sole developer — admin frontend and the NestJS API behind it.
Built the definition-driven form engine and the field components it renders
Integrated TipTap with custom toolbar, tables, code highlighting and media insertion
Built the NestJS content, media, auth and revalidation modules on MongoDB
Implemented cookie-based JWT auth with refresh-token rotation
Challenges & solutions
One schema, two consumers. Keeping admin forms and server validation in sync by hand drifts fast. Both read the same section definitions from a shared package, so a field change is made once.
Draft vs publish rules. Some fields are optional while drafting but required to publish; the validator takes the target status into account so drafts can be saved incomplete.
Safe sessions in the browser. Access and refresh tokens live in httpOnly cookies, and the client silently refreshes on a 401 instead of storing tokens in JavaScript.
متعلقہ پروجیکٹس
Portfolio / Headless CMSAli Haider Portfolio — CMS-Driven Public Website
A fully dynamic personal portfolio on Next.js 16 — every section, menu item and setting comes from a headless CMS, statically generated and revalidated on publish.
- Next.js 16
- React 18
- TypeScript
- Tailwind CSS
- +6