CMS with admin dashboard
Punjab AC
Punjab Car AC—Next.js catalog site, React CMS admin, and Express/MongoDB API for automotive AC products, services, and content.
Background & Context
Punjab AC (public brand Punjab Car AC, Lahore) is a three-package platform: Next.js 14 marketing/catalog (punjabac-web), React CRA admin (punjabac-admin/client), and Express/MongoDB API (punjabac-admin/server). Scope covers products, services, blogs, categories, brands, benefits, auto companies, and inbound messaging—not e-commerce checkout.
Corrections vs older marketing copy: sitemap/robots/Open Graph generators were not found in web src/; sub-dealers, company profile, team, and clients pages are largely static; JWT protects blog mutations and /auth/me, but many catalog mutating routes lack auth middleware; public GetAQueryForm emails via /api/contact and does not create Mongo Query records that admin Messages reads. Lighthouse 85+ appears as an order-brief goal, not an in-repo report.
The Challenge
An automotive AC retailer/service business needed a public catalog and company presence plus a back office for products, services, blogs, brands, and inquiries—without building payments/cart. Without a coherent cms with admin dashboard foundation, Punjab AC stakeholders faced fragmented tools, slow handoffs, and limited visibility—classic failure modes Tekvers designs against.
The Solution
Punjab AC: Punjab Car AC—Next.js catalog site, React CMS admin, and Express/MongoDB API for automotive AC products, services, and content. Staff can manage catalog and blog content from the admin SPA. Tekvers delivered a maintainable cms with admin dashboard system for Punjab AC using Next.js 14, React, Express, MongoDB, with phased rollout, operator workflows, and documentation suited to long-term ownership.
Our Approach
Catalog domain model
Products link to brands, categories, benefits, and vehicle auto companies; services and blogs are first-class with slug patterns (`title-id` on the client).
Three-package delivery
Independent installs for web, admin UI, and API; production API host `punjabac-admin.vercel.app`; SMTP `mail.punjabac.com` / `info@punjabac.com`.
Document mismatches
Case differences on auto-companies paths, PUT vs PATCH on queries, Multer vs body image paths—called out in docs so operators know what still needs hardening.
What We Delivered
- Next.js public site: home, services, products, blogs, brands, contact, get-quote, static company/team/clients/sub-dealers
- React admin CRUD: blogs, products, categories, brands, benefits, services, auto companies, messages
- Express APIs for auth, blogs, products, services, queries, benefits, contact, categories, brands, autocompanies
- JWT for register/login/me and blog write ops; Swagger in non-production
- Contact email path via Nodemailer
- Explicit non-features: cart/payments, users admin UI, sitemap/robots/OG generators, guaranteed Query persistence from public contact form
Outcomes & Impact
- Staff can manage catalog and blog content from the admin SPA
- Public filters for category/brand/auto company/benefit/search
- Honest SEO baseline: root metadata title present; advanced SEO artifacts not in source
Punjab Car AC publishes automotive AC offerings from a real three-tier stack—without Tekvers inventing dealer CMS, Lighthouse scores, or sitemap features the repository does not contain.
Technology Stack
Services Delivered
Related Case Studies
Guides & articles from this niche
Planning a similar platform? Share your scope and we will map architecture, delivery phases, and a realistic timeline.