A starter kit to quickly make your own directory listing website using Nextjs, Supabase and Stripe
This blog tells the story about ToolDir, the directory listing website template built using Nextjs, Supabase and Stripe, a full-stack template to quickly build your directory listing website platform that can earn online.
Directory listing websites are boring, but in 2026, we got tonnes of SaaS submission websites, AI tool listing websites, prompt directories, Design md directories, and even React frontend UI directories.
Each directory has almost the same pattern of building, and every time we do the same process as defined
- Create a frontend landing page
- Each product page and all product listings pages with filters and search
- Login page for authentication
- Submit page for submitting tools/prompts/designs based on the directory website
Below is our ToolDir LLM.txt for the directory template. Copy the text and paste it into Claude to get more details about our listing directory template, its features, and how to create one on your own.
# ToolDir — LLM context file
# Purpose: help coding agents understand this repo quickly without exploratory scanning.
# Last cleaned for launch template readiness.
## Product
ToolDir is a Next.js 15 (Pages Router) AI tool directory boilerplate.
Buyers launch a public directory site, accept tool submissions, sell launch slots,
publish a blog, and manage everything from `/admin`.
This is NOT a generic multi-tenant SaaS CMS. Older SaaS modules (email campaigns,
waitlist, kanban, products catalog, forms builder, cron, codegen) were removed.
## Tech stack
- Next.js 15 Pages Router (`pages/`), React 18, Tailwind, shadcn/ui
- Supabase (Auth + Postgres + Storage)
- TanStack React Query for server state
- Redux Toolkit only for subscription/customer client state
- TipTap for blog CMS
- Stripe **one-time** Checkout for launch slots (server builds `price_data`; no Price ID catalog required)
- Set `STRIPE_TEST_ZERO=true` (+ `NEXT_PUBLIC_STRIPE_TEST_ZERO`) to force $0 checkout while wiring webhooks/admin
- Resend for optional slot-payment receipt (`sendSlotPaymentEmail`)
- Framer Motion for marketing motion
## Critical architecture note
`app/` is NOT the App Router.
- `pages/` = real Next.js routes and API handlers
- `app/admin/` = admin UI components
- `app/frontend/` = marketing site components (Navbar, Footer, directory UI)
- `components/ui/` = shadcn primitives
- `lib/` = APIs, hooks, config, data seeds, store, utils
## Public routes (keep)
| Route | File | Role |
|-------|------|------|
| `/` | `pages/index.js` | Directory home |
| `/tool/[slug]` | `pages/tool/[slug].js` | Tool detail |
| `/categories/[slug]` | `pages/categories/[slug].js` | Category filter |
| `/submit` | `pages/submit.js` | Multi-step submission |
| `/pricing` | `pages/pricing.js` | Launch slot calendar |
| `/dashboard` | `pages/dashboard.js` | User submissions |
| `/blog`, `/blog/[slug]` | `pages/blog*.js` | Public blog |
| `/contact`, `/privacy`, `/terms-and-conditions` | legal |
| `/auth/callback` | Supabase OAuth |
| `/robots.txt`, `/sitemap.xml` | SEO |
## Admin routes (keep)
| Route | Role |
|-------|------|
| `/admin` | Shell + tabs |
| `/admin/blogs/new`, `/admin/blogs/[id]` | Nested blog editor |
| `/admin/editor/blog` | Legacy redirect into nested editor |
Admin tabs (sidebar): analytics, users, submissions, payments, invoices, pricing-slots, blogs.
Tab id `forms` was renamed to `submissions` (legacy `forms` still opens SubmissionsTab).
## API routes (keep)
- `/api/directory-tools/publish` — approve submission → listing
- `/api/directory-tools/seed` — seed from `lib/data/tools.js`
- `/api/tool-submissions/create` — public submit
- `/api/pricing-slots/upsert` — admin slot CRUD
- `/api/storage/upload-image` — Supabase Storage uploads
- `/api/messages/create` — contact form
- `/api/stripe/checkout` — one-time Checkout for launch slot (`price_data`, optional `$0` via `STRIPE_TEST_ZERO`)
- `/api/stripe/webhook` — marks submission paid, upserts `payments` / `customers` / `users`, sends Resend receipt
Removed: `/api/stripe/cancel-subscription` (no SaaS subscriptions).
## Core modules (do not delete)
lib/api/directoryTools.js
lib/api/toolSubmissions.js
lib/api/pricingSlots.js
lib/api/blog.js
lib/api/storage.js
lib/api/auth.js
lib/hooks/useDirectoryTools.js
lib/hooks/useBlogs.js
lib/hooks/usePricingSlots.js
lib/data/tools.js
lib/data/pricing-slots.js
lib/data/testimonials.js
app/frontend/marketing/*
app/admin/components/SubmissionsTab.jsx
app/admin/components/PricingSlotsTab.jsx
app/admin/components/BlogTab.jsx
app/admin/components/BlogTiptapEditor.jsx
app/admin/views/BlogEditorView.jsx
## Data model (Supabase)
Primary tables: `directory_tools`, `tool_submissions`, `pricing_slots`, `blogs`
Billing/admin: `users`, `customers`, `payments`, `checkouts`, `invoices`, `messages`, `app_analytics`
Storage bucket: `saas-starter-storage` (name kept for compatibility)
See `supabase-migrations.sql` (single file: tables + payment columns + Storage bucket).
When Supabase is empty / unset, directory listing can fall back to mock data in `lib/data/tools.js`.
## Supabase Storage
Bucket name: **`saas-starter-storage`** (constant `STORAGE_BUCKET` in `lib/api/storage.js`).
TipTap editors call `uploadBlogEditorImage` → direct Storage upload, fallback `POST /api/storage/upload-image`.
Paths: `blogs/content/`, `blogs/{id}/content/`, `blogs/banners/`, `blogs/{id}/banner-*`.
SQL: run `supabase-migrations.sql` once (includes Storage bucket `saas-starter-storage`).
## Environment variables
Required for core:
- `NEXT_PUBLIC_SITE_URL`
- `NEXT_PUBLIC_SUPABASE_URL`
- `NEXT_PUBLIC_SUPABASE_KEY`
Payments:
- `STRIPE_SECRET_KEY`
- `STRIPE_WEBHOOK_SECRET`
- `NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY` (optional if you only start checkout server-side)
- `STRIPE_TEST_ZERO=true` — charge $0 in Checkout for local testing
- `NEXT_PUBLIC_STRIPE_TEST_ZERO=true` — show $0 copy on submit UI
Optional:
- `RESEND_API_KEY`, `RESEND_FROM_EMAIL`
- `NEXT_PUBLIC_POSTHOG_KEY`, `NEXT_PUBLIC_POSTHOG_HOST`
- `NEXT_PUBLIC_APP_URL` (legacy Stripe fallback; prefer SITE_URL)
Use `.env.local` locally. `.env*` is gitignored.
## Intentional dual editors
- `BlogTiptapEditor.jsx` — canonical nested route editor (`/admin/blogs/*`)
- `TiptapEditor.jsx` — still used by BlogTab modal list workflow
Do not delete either without consolidating BlogTab first.
## What was removed for launch
Do not reintroduce these without a product need:
- Forms builder (`FormsTab`, `/api/forms/*`, `forms` / `form_submissions` tables)
- Email campaigns, subscribers, waitlist, kanban/tasks, idea DB, changelog, cron, assets CMS
- Builder zip/AST APIs, roles-config codegen (`modules-config`, generate-*)
- Unused deps: octokit, archiver, simple-git, nginx, react-toastify, @vercel/analytics, @stripe/stripe-js, unused Radix accordion/checkbox/avatar/tabs/tooltip/switch/scroll-area
## Conventions for agents
1. Prefer Pages Router for new pages under `pages/`.
2. Put reusable marketing UI in `app/frontend/marketing/`.
3. Put Supabase access in `lib/api/*`; use React Query hooks in `lib/hooks/*`.
4. Do not change visual theme / CSS / layout unless the task is design work.
5. Do not commit `.env` files.
6. Keep packaging lean — delete orphan modules instead of leaving stubs.
7. Brand copy is ToolDir, not "SAAS Starter".
## Local commands
bash
npm install
npm run dev # http://localhost:3002
npm run build
npm run lint
npm run pack # clean buyer zip → dist/tooldir.zip
When I was building this boilerplate, I wrote the LLM text to help everyone ask questions related to the boilerplate on Claude or chatgpt.
Once done, check the demo
Once checked, buy the template 😃
Let me explain what this template contains
How to build your Directory website in seconds?
- You will get the zip file
- Unzip it and run some commands (All details are in the Readme.md file in the zip)
- Once run, add the supabase migration SQL in supabase SQL editor to create the database tables
- For authentication, simply enable supabase Google and Email as a sign-in provider and add Google Cloud Console credentials, such as Client ID and Client secret, along with the OAuth callback URL (Details are in the readme file)
- Add the Stripe secret key from the Stripe dashboard to enable payment for the early submission booking slot
- Change and customise the pricing, landing page and blogs as per your project needs
- Deploy the app and put the env keys containing supabase key and the Stripe key on the deployment server
7 steps and your directory website is ready with database, authentication and payment integrated.
Admin Panel to Manage Directory Website Business
That is not enough
Inside the zip folder, you can find app/admin folder, this contains the admin panel to write blog, review submissions, check payments and website analytics and update pricing for each slot, all reflects directly on the website within the admin panel.
https://tooldir.buildsaas.dev/admin
This makes it easy for you to run the entire directory website content, manage users and view analytics without touching code.
Tech Stack
The template is built using the latest technology stack
- Nextjs
- Shadcn for UI components
- Tailwind for styling
- framer motion for animation
- Lucide React for icons
- Supabase for the database
- Supabase storage for images
- Stripe for payment
- Resend for emailing
All tech stacks are universally accepted and open-source, making it robust by nature.
Conclusion
Directory listing websites are in trend, and making one is a good way for you to earn money online. ToolDir ease the pain in making the entire website and saved almost $2k as a developer's costs; it works well with AI agents like Cursor, v0 or Lovable or Bolt.
Cheers
Shrey
If needed, custom template, shoot me an email at shreyvijayvargiya26@gmail.com
Top comments (0)