Appearance
Repository Map
| Repository | Purpose |
|---|---|
axelites/menzzo-docs | Global documentation site and submodule source. |
axelites/logidav | Logistics middleware and operational integration layer. |
axelites/menzzo | Magento ecommerce application. |
axelites/menzzo-chatbot-ui | Customer-facing chat UI and Dify integration. |
axelites/menzzo-chatbot-backend | Business APIs for chatbot and customer-support workflows. |
axelites/menzzo-chatbot-logs | API for querying Dify conversation, message, and workflow records. |
axelites/menzzo-meduse-front | Meduse Vue application: screens, navigation and API consumers. |
axelites/menzzo-meduse | Meduse Laravel backend: catalog APIs, connectors, schedules and jobs. |
menzzo-media-app / menzzo-media-app-sass | Media-generation and productization work. |
menzzo-chatbot-wrapper may still appear as a local checkout name for the backend. Use the canonical repository names above when linking code. See Menzzo Chatbot for component connections.
The Meduse section pins both the frontend and backend source revisions and explains how they connect.
Documentation Submodules
Application repositories mount axelites/menzzo-docs at the paths declared in their .gitmodules files:
| Repository | Docs path from repository root | Source |
|---|---|---|
axelites/menzzo | docs/ | .gitmodules |
axelites/logidav | docs/ | .gitmodules |
axelites/menzzo-chatbot-ui | docs/ | .gitmodules |
axelites/menzzo-chatbot-backend | global-docs/ | .gitmodules |
axelites/menzzo-meduse | docs/ | .gitmodules |
axelites/menzzo-chatbot-logs | docs/ | .gitmodules |
The VitePress app is at the root of the docs checkout, with documentation in content/. Initialize the submodule before entering the path for your repository; the checked-out docs revision is determined by that repository's submodule pin.
Scope and evidence
The first table lists canonical repositories currently named in the shared docs. The submodule table records pinned docs mounts at the commits linked in its Source column. Together they are not a complete inventory of every project area, deployment, environment, or active integration; see the project directory and coverage matrix for those views.
When a local folder name differs from its canonical repository identity, use the canonical name in documentation links. A docs submodule pin only identifies which docs revision a host repository checks out; it says nothing about the host application's deployed revision or runtime configuration.