Next.js Content Admin Dashboard Build
Budget / Salary₹1,500–12,500
TypeFreelance project
LocationRemote
Posted2 hours ago
I need a full-stack developer to spin up a clean, well-structured admin dashboard that lets my team manage site content with ease. The stack is already decided: Next.js (app router), TypeScript, PostgreSQL, Prisma for the ORM layer, and NextAuth to handle secure sign-in.
Here’s what matters most:
• The dashboard’s core job is content management—adding, editing, publishing, archiving, and searching through our various entries.
• Two role levels must be respected: Administrators can do everything; Viewers log in only to browse read-only versions of the same data.
• Authentication flows and role-based authorization must be wired end-to-end, ideally using NextAuth’s credentials or OAuth providers.
• Prisma schema should mirror the content models and user tables in PostgreSQL, with sensible relations and migrations checked in.
• A simple, intuitive UI is key; feel free to bring your favourite component library or Tailwind if it speeds things up, but keep the codebase modular and typed.
Deliverables
1. GitHub repo (or similar) containing the Next.js project, fully typed, lint-clean, and ready to deploy.
2. SQL migration scripts generated through Prisma Migrate.
3. Clear README with env variables, setup steps, and a short loom/screencast that shows an Admin and a Viewer journey through the dashboard.
I’ll review by pulling the repo, running yarn install && prisma migrate dev and verifying that both roles function exactly as described. If that test passes and the UI feels responsive, the job is complete.
Here’s what matters most:
• The dashboard’s core job is content management—adding, editing, publishing, archiving, and searching through our various entries.
• Two role levels must be respected: Administrators can do everything; Viewers log in only to browse read-only versions of the same data.
• Authentication flows and role-based authorization must be wired end-to-end, ideally using NextAuth’s credentials or OAuth providers.
• Prisma schema should mirror the content models and user tables in PostgreSQL, with sensible relations and migrations checked in.
• A simple, intuitive UI is key; feel free to bring your favourite component library or Tailwind if it speeds things up, but keep the codebase modular and typed.
Deliverables
1. GitHub repo (or similar) containing the Next.js project, fully typed, lint-clean, and ready to deploy.
2. SQL migration scripts generated through Prisma Migrate.
3. Clear README with env variables, setup steps, and a short loom/screencast that shows an Admin and a Viewer journey through the dashboard.
I’ll review by pulling the repo, running yarn install && prisma migrate dev and verifying that both roles function exactly as described. If that test passes and the UI feels responsive, the job is complete.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.