How nntan2002/sventure works
Main components
• Frontend Client: Represented by the Nuxt/Vue application. This component handles UI rendering, user interactions, and communicates with the backend APIs.
• Backend CMS: Built on Strapi, this contains the API endpoints. Note the multiple API modules (e.g., building, category-service, contact, header, page-home, etc.) that follow typical MVC patterns (with controllers, routes, and services).
• Database: While not separately visible as a dedicated “database” folder, the CMS/config/database.js and migrations components hint at a persistent storage layer (whether it's PostgreSQL, MongoDB, etc.) that supports the Strapi CMS.
• External Services/Configurations: There are configuration files for deployment (ecosystem.config.js on both frontend and backend), environment files (.env), and files for proper code styling and linting. These indicate integration with CI/CD pipelines and other deployment tools.
Important architectural patterns/principles
• MVC Pattern in Strapi CMS: As seen in the cms/src/api/* directories, each API follows a pattern with content types, controllers, routes, and services.
• Separation of Concerns: The clear division between frontend (presentation/UI layer) and backend (data layer and API logic).
• Modular organization: Each API endpoint (for building, contact, header, etc.) is separated into self-contained modules.
• Environment-based configuration: With files like .env.example and various config files, the deployment setup is designed to easily switch contexts.
Relevant technologies and frameworks
• Frontend: Nuxt.js and Vue.js, along with Bootstrap for styling.
• Backend: Strapi as the headless CMS, using Node.js and likely employing various npm packages listed in package.json.
• Additional tools: ESLint, EditorConfig, and ecosystem configuration for process management.
• Clear labels for each major component: “Frontend (Nuxt/Vue)” and “Backend (Strapi CMS)” with further sub-labels to denote API modules if desired.
• A distinct “Database” component showing persistent storage.
• Annotations or brief descriptions on critical connections such as “API calls,” “data retrieval,” or “configuration management (CI/CD).”