Wedlii Portals Monorepo Overview: Apps, Architecture, and Workflow
A comprehensive overview of the Wedlii Portals monorepo: multi‑app Next.js architecture, shared packages, design system, workflows, tooling, and the content/feature ecosystem that powers bridal, vendor, venue, admin, and marketing experiences.

Technologies Used
Wedlii Portals Monorepo
Wedlii Portals is a scalable, multi‑app platform built on a Turborepo foundation to power every role in the wedding ecosystem. The monorepo contains multiple Next.js applications plus shared packages that maintain UI consistency and developer efficiency.
Why it matters: A unified codebase keeps the user experience cohesive while enabling each portal to evolve independently.
🏗 Monorepo at a Glance
- Shared Standards: Unified linting, formatting, and component patterns.
- Consistent UI: A reusable design system across all touchpoints.
- Fast Iteration: Powered by Turborepo + pnpm workspaces.
- Role‑Based Experiences: Dedicated environments for bridal, vendor, venue, admin, and public discovery.
📱 Apps (User‑Facing Portals)
| Portal | Purpose |
|---|---|
| Admin Portal | Operations, content review, and platform oversight. |
| Bridal Portal | Planning tools and wedding management. |
| Vendor Portal | Business management and lead tracking for vendors. |
| Venue Portal | Listing management and booking for venues. |
| Wedlii Frontend | Public marketing and discovery site. |
📦 Shared Packages
🎨 Design & UI
- Design system components (shadcn‑style primitives).
- Shared Tailwind config and design tokens.
🛠 Tooling
- Shared ESLint, Prettier, and Next.js configurations.
🧠 Reusable Logic
- Shared components package for cross-app business logic.
🛠 Architecture Overview
The system utilizes the Next.js App Router to organize features by route groups and views.
Data Flow:
- Server Rendering: Used for SEO and content-heavy pages.
- State Management: Client actions via Redux Toolkit (authenticated areas).
- Headless CMS: Strapi CMS serves as the primary content backbone.
"A shared architecture lets the team build faster while preserving a consistent Wedlii voice and visual language."
💻 Workflow & Developer Experience
Standardized Best Practices
- Standardized file naming conventions.
- Consistent import order (Prettier plugin).
- Optimized image workflows (WebP preferred).
Sample Code Usage
import { Button } from "@wedlii-portals/ui/button";
export default function CTA() {
return (
<Button variant="default" size="lg">
Get Started
</Button>
);
}
🚀 Content & Experience Layer
The public frontend serves as a gateway featuring:
- Vendor and venue directories.
- Inspiration galleries and AI‑assisted wedding visuals.
- Budgeting tools and submission flows.
✨ Quick Highlights
- Scale: Multiple apps + reusable packages.
- Tech Stack: Next.js, Tailwind CSS, Turborepo.
- Content: Strapi CMS integration.
- Quote: “One codebase, five experiences, one consistent brand.”
📋 Implementation Checklist
- Unified design system
- Multi‑app deployment strategy
- Shared configs for consistency
- Clear onboarding docs
Project Gallery
Interested in working together?
I'm always open to discussing new projects and opportunities.