How 99mini/voyage works
Overall Structure & Components
• Major tiers in the system:
• Frontend Applications: Several React/TypeScript apps (Home, Tool, Tech, Admin, Awesome, and Todo) each with their own subdirectories and distinct features. Note that “Tech” uses Docusaurus while “Home” also incorporates Remix.
• Backend Services: A “server” folder that splits into “Rest” (NestJS for REST API), “Functions” (serverless functions written in Node/TypeScript), and “Batch” (batch processing API – TODO).
• Shared Packages: Under “packages,” there are components like “api-client” (for making API calls), “pb-api” (integrating Pocketbase), and “VDS (Voyage Design System)” which standardizes UI components across the frontends.
• CLI: A command-line interface under the “apps/cli” directory that, while minimal now, forms a part of the ecosystem.
Architectural Relationships & Data Flow
• Frontend to Backend:
• The “api-client” package is a shared client library used by frontends to consume REST or Functions APIs.
• Backend Internals:
• “Batch” as a component that might interact with asynchronous processes.
• Shared Components & Design System:
• “VDS (Voyage Design System)” package as a common library that feeds UI consistency into the frontends.
• That the shared packages like “api-client” and “pb-api” are integrated both at the application level and possibly in backend services where needed.
Architectural Patterns/Design Principles
• Separation of Concerns: Clearly separate UI (frontend) from business logic and API logic (backend). Each application is self-contained yet uses shared libraries.
• Modular Design: With multiple distinct apps and packages, emphasize modularity. Each frontend app, backend service, and package can be visualized as modules that interact via well-defined interfaces (like API calls).
• Extensibility & Reusability: The shared packages (e.g., VDS and api-client) should be marked as reusable libraries that all apps depend on.