Monorepo Architecture

VeriWorkly utilizes a monorepo structure to manage multiple integrated applications and shared packages within a single repository. This approach ensures consistent dependency management and facilitates the sharing of design tokens and core logic.

[!NOTE] The full repository structure and configuration can be explored directly on GitHub.

Application Architecture

The platform is composed of several primary applications, each with a distinct operational scope.

1. Marketing Site (apps/site)

• Port: 3000
• Framework: Next.js (App Router)
• Scope: Landing page, feature showcases, and public marketing content.
• Key Features: SEO-optimized pages, interactive demos, and conversion funnels.

2. Resume Studio (apps/studio)

• Port: 3001
• Framework: Next.js (App Router)
• Scope: Primary user interface for resume construction, management, and local-first editing.
• Key Features: Dual-engine rendering (Web/PDF), Zustand-based state persistence, and real-time template customization.

3. API Server (apps/server)

• Port: 8080
• Framework: Node.js / Express
• Scope: Core backend services including authentication, data synchronization, and administrative tasks.
• Key Features: Prisma ORM integration, Better-Auth security layer, and GitHub data bridge.

4. Documentation Platform (apps/docs-platform)

• Port: 3002
• Framework: Next.js / Fumadocs
• Scope: Technical and user documentation.
• Key Features: MDX-based content management and automated API reference generation.

5. Blog Platform (apps/blog-platform)

• Port: 3003
• Framework: Next.js / Fumadocs
• Scope: Product updates, career-oriented content, and official guides.

---

Shared Infrastructure (packages/ui)

The @veriworkly/ui package serves as the centralized design system for the entire monorepo. It provides:

• Reusable React primitives and components.
• Standardized layout utilities.
• Centralized Tailwind CSS 4 theme configurations and design tokens.

---

Repository Structure

VeriWorkly utilizes standardized monorepo conventions to organize its services and shared logic.

---

Operational Advantages

• Service Isolation: Each application maintains independent operational boundaries and deployment lifecycles.
• Resource Efficiency: Shared packages minimize redundant code and ensure visual consistency across all platforms.
• Scalability: Backend services can be scaled independently of the frontend applications.