Back to .md Directory

MVP Overview

Defines the MVP scope, tech stack, and 44 completed tasks for a single-product e-commerce landing page generator built with Next.js and Supabase.

May 2, 2026
0 downloads
0 views
ai rag
View source

What this file does

Defines the MVP scope, tech stack, and 44 completed tasks for a single-product e-commerce landing page generator built with Next.js and Supabase.

When to use it

  • Starting a similar MVP for individual product pages without a catalog
  • Planning a Next.js + Supabase e-commerce project with JWT auth
  • Reviewing a completed task breakdown to estimate your own project
  • Understanding the feature set before forking or contributing

Assumes this stack

Next.jsTailwind CSSSupabaseJWTTypeScriptDocker

MVP Overview

This project is a simple e-commerce landing page generator for individual product sales. Sellers can create multiple standalone product pages, each with a "Buy Now" button leading to a universal order form. Products are not listed together in a catalog—they each live on their own unique link, allowing sellers to advertise and sell them individually.

Key Features:

  • Sellers can create and manage multiple independent products.
  • Each product has its own landing page with a chosen template.
  • Buyers fill out a standard form to place an order.
  • Sellers manage orders and update statuses via a dashboard. Always use pnpm

Always use pnpm

Development environment

-ubuntu 24.04 Always use pnpm

Tech Stack

Frontend:

  • Next.js (App Router) — React framework for routing and rendering
  • Tailwind CSS — Utility-first styling
  • Radix UI — Accessible UI primitives
  • Lucide Icons — Modern icon set
  • React Hook Form + Zod — Form management and validation
  • next-themes — Light/Dark theme support

Backend:

  • Next.js API Routes — Server-side logic and APIs
  • JWT Auth (with HttpOnly cookies) — Seller login and protected routes
  • Supabase — PostgreSQL Database, Auth, and optional file storage

Dev & Ops:

  • TypeScript — Strong typing for maintainability
  • ESLint & Prettier — Code quality and formatting
  • Docker — Local development & potential deployment
  • Vercel — For simple and fast frontend deployments

Tasks

Story PointsTaskRole
1 [x]Create basic frontend scaffold (Next.js + Tailwind)Frontend foundation
2 [x]Create basic backend scaffold (Express + JWT auth)Backend foundation
3 [x]Define database schema for Product and OrderData modeling
4 [x]Implement database migrationsData persistence
5 [x]Build Seller login page with form validationAuthentication
6 [x]Implement login API endpoint with JWTAuthentication
7 [x]Protect dashboard routes with auth middlewareSecurity
8 [x]Build Dashboard layout with nav links (Products, Orders)UI structure
9 [x]Create "Products" list component in dashboardProduct management UI
11 [x]Implement GET /api/products endpointProduct API
12 [x]Fetch and display products in dashboardProduct management data
13 [x]Create "Create Product" button and modal formProduct creation UI
14 [x]Implement POST /api/products to save new productProduct API
15 [x]Generate unique slug/ID for each productData modeling
16 [x]Build TemplateSelector component with 3 template previewsProduct creation UI
17 [x]Wire template choice into product creation flowProduct creation logic
18 [x]Implement product activate/deactivate toggleProduct management
19 [x]Create dynamic public route /p/[slug]Routing
20 [x]Fetch product data in public page (GET /api/products/:slug/public)Public product rendering
21 [x]Build three React template components for product pageUI components
22 [x]Add "Buy Now" button linking to /p/[slug]/orderBuyer flow
23 [x]Build Order form component with fields and validationBuyer flow form
24 [x]Implement POST /api/orders to save orderOrder API
25 [x]Show order confirmation pageBuyer feedback
26 [x]Create "Orders" list in dashboard per productOrder management UI
27 [x]Implement GET /api/orders?productId= endpointOrder API
28 [x]Display orders table with status and "View Details" buttonOrder management data
29 [x]Build OrderDetail component showing full form dataOrder management UI
30 [x]Implement PUT /api/orders/:id/status to update order statusOrder API
31 [x]Add status dropdown in OrderDetail and wire status updateOrder management interaction
32 [x]Configure Tailwind theme (colors, typography)Styling
33 [x]Write README with setup, env vars, run instructionsDocumentation
34 [x]Write database migration and seed scriptsDeployment prep
35 [x]Extend product DB schema to support multiple sizesData modeling
36 [x]Extend product DB schema to support multiple colorsData modeling
37 [x]Extend product DB schema to support multiple imagesData modeling
38 [x]Update product API endpoints to handle sizes, colors, imagesProduct API
39 [x]Update product creation/edit form to add/remove sizesProduct creation UI
40 [x]Update product creation/edit form to add/remove colorsProduct creation UI
41 [x]Update product creation/edit form to upload/manage multiple imagesProduct creation UI
42 [x]Update product page templates to display selectable sizesUI components
43 [x]Update product page templates to display selectable colorsUI components
44 [x]Update product page templates to display image galleryUI components
44 [x]Extend product DB schema to support QuantityData modeling
44 [x]Update product creation/edit form to QuantityProduct creation UI
44 [x]Update product page templates to calculate and show change order QuantityUI components

next tasks: -update the colors and sizes implementation ( The implementation of colors and sizes isn't appropriate Colors should be chosen from a color field or idk in the product creation and shown as colors in the product page Sizes can be different based on products like shoes and t-shirt not same size and all )

-add template library with deffrent product template layout colors and design of the page but same functionalities

What's inside

Overview, key features, tech stack table, and 44 task rows with story points and roles

Change this for your project

  • Replace devenryu/ECOMME with your own repository name
  • Replace pnpm references with your package manager if different
  • Replace ubuntu 24.04 with your development OS
  • Replace Vercel with your deployment platform if not using it

Where it goes

Keep it in your repository where the agent or team that needs it will read it.

Worth borrowing

  • Task table with story points and role labels for clear ownership
  • Separating product page templates from the order form flow
  • Using a universal order form linked from individual product pages

Related Documents