MomsOne

MomsOne brings moms together through curated events, community experiences, workshops, meetups, and support spaces designed to help mothers connect, learn, and feel supported.

This repository contains the MomsOne MVP package: a NestJS backend API, a React admin dashboard, design documentation, product blueprints, and production-readiness artifacts for continued development.

Product Overview

MomsOne is a community and activity marketplace for mothers. The platform is designed to support:

• Curated community events and workshops
• Local meetups, circles, and support spaces
• Host, venue, coach, and activity management
• Trust, safety, reporting, and verification workflows
• Admin operations for reviewing users, content, payments, and platform health

Repository Contents

Path	Purpose
00_HANDOFF.md	Primary handoff document for developers and agents continuing the project
01_BLUEPRINTS/	Product strategy, deployment blueprint, API contracts, data flow, and database planning
02_FRAMEWORK_ADDENDUMS/	Backend, security, and non-conflicting implementation frameworks
03_PRODUCTION_ARTIFACTS/	API specification, backend framework, security framework, and readiness scorecards
04_DESIGN_SYSTEM/	Page-level design system documentation for the admin experience
05_BACKEND_SOURCE/	NestJS, Prisma, and PostgreSQL backend API
06_FRONTEND_ADMIN/	React, Vite, Tailwind, and shadcn/ui admin dashboard
manifest.json	Machine-readable inventory of package artifacts and readiness scores

Tech Stack

Backend

• NestJS 10
• TypeScript
• Prisma ORM
• PostgreSQL 15+
• Passport JWT authentication
• Stripe integration scaffolding
• Docker and Docker Compose support

Frontend Admin

• React 19
• Vite 7
• TypeScript
• Tailwind CSS
• shadcn/ui and Radix UI
• Recharts
• React Router

Backend Features

The backend API includes modules for:

• Authentication and OTP-based access
• User profiles
• Community circles
• Events and RSVP workflows
• Host verification
• Venues
• Coaches
• Activities and bookings
• Payments
• Reviews
• Reports and moderation
• Trust scores
• Notifications
• Health allies
• Admin operations
• Health checks

Admin Dashboard Features

The admin dashboard includes pages for:

• Login
• Dashboard KPIs and activity
• Users
• Circles
• Events
• Venues
• Host verifications
• Coaches
• Payments
• Reports
• Trust scores
• Notifications
• Settings

Getting Started

Prerequisites

• Node.js 20+
• npm
• PostgreSQL 15+
• Docker, optional but recommended for local backend services

Backend Setup

cd 05_BACKEND_SOURCE
cp .env.example .env
npm install
npx prisma generate
npm run start:dev

The backend defaults to port 3000. Configure database, JWT, Stripe, SMTP, and admin values in 05_BACKEND_SOURCE/.env.

To start the backend and database with Docker:

cd 05_BACKEND_SOURCE
docker compose up --build

Frontend Admin Setup

cd 06_FRONTEND_ADMIN
npm install
npm run dev

The Vite dev server will print the local admin dashboard URL, usually http://localhost:5173.

Environment Variables

Backend variables are documented in:

05_BACKEND_SOURCE/.env.example

Important variables include:

• DATABASE_URL
• JWT_SECRET
• JWT_REFRESH_SECRET
• STRIPE_SECRET_KEY
• STRIPE_WEBHOOK_SECRET
• SMTP_HOST
• SMTP_USER
• SMTP_PASS
• FRONTEND_URL
• ADMIN_API_KEY

Never commit real secrets to this repository.

Useful Commands

Backend

cd 05_BACKEND_SOURCE
npm run build
npm run lint
npm test
npm run test:e2e
npm run prisma:generate
npm run prisma:migrate

Frontend Admin

cd 06_FRONTEND_ADMIN
npm run build
npm run lint
npm run preview

Project Status

This is an MVP handoff package, not a final production release. The included readiness artifacts currently identify the platform as assembled and functional, with follow-up work required before production launch.

Priority hardening areas include:

• Expanding automated test coverage
• Implementing audit log writes across mutation services
• Replacing mocked external integrations with production-ready providers
• Adding Redis-backed OTP/session support
• Adding frontend route guards
• Completing production deployment, observability, and monitoring

For the full gap register and sprint plan, start with:

00_HANDOFF.md
03_PRODUCTION_ARTIFACTS/MOMSONE_UNIFIED_MASTER_SCORECARD.md
03_PRODUCTION_ARTIFACTS/backend_framework.md
03_PRODUCTION_ARTIFACTS/security_framework.md

Development Notes

• Treat 00_HANDOFF.md as the first read for any new developer or agent.
• Keep backend and frontend dependency installs scoped to their respective folders.
• Keep generated build outputs, local environment files, and OS artifacts out of version control.
• Use the production artifacts as the source of truth for API contracts, security expectations, and remaining hardening work.

License

License information has not been finalized yet.