Menzzo Meduse

Purpose

Meduse is the catalog workspace where teams maintain products, attributes, families, categories, menus and media, then exchange data with connected commerce and operations systems. Start with the screen you are changing, follow its API call, and then follow any job or connector it triggers. A saved product, a completed background job and a published storefront change are different checkpoints.

Follow a task from screen to destination

Start with the outcome you need, then use the interface and API inventories to locate the exact implementation.

Outcome	Journey guide
Follow a new SKU from Logidav's Publish button through Magento and back	Complete publication journey, then Meduse's part
Edit one product or save many rows from the spreadsheet grid	Product editing and bulk updates
Change an attribute, family, category tree or storefront menu	Catalog structure and menus
Upload, reorder or remove product media, attach files, or synchronize Vimeo stories	Images, files and Vimeo
Understand how Logidav data enriches the Mosaikasa catalog	Logidav catalog enrichment
Trace family, attribute and ASIR mapping files into Logidav	Reference-data handoffs
Follow publication to Magento, Shopify, a feed or Logidav	Integration workflows
Follow reviewed central product changes to the Mosaikasa tenant and Shopify	Mosaikasa product sync
Investigate work that has not finished	Queues and job state, then the relevant journey's failure checkpoints

Each guide follows the trigger, request, stored data, processing step and destination boundary. Begin with a development fixture and confirm tenant, channel and locale before following an example. These are source-based walkthroughs, not records of live acceptance tests.

Start from an interface

Your task	Read next
Find a screen, its Vue component and the API it calls	Interface map
Change navigation, a form, a grid or request handling	Vue frontend
Change a request, validation or stored catalog data	Backend request flow and API endpoint inventory
Trace a product, image, category or menu through the system	Workflows
Understand the connection to Logidav, Magento or another channel	Connectors
Find what starts an import/export automatically	Scheduled jobs
Find which worker consumes pending work and how failures appear	Queues and job processing
Understand the frontend/backend/process boundaries	Architecture

Stack

Component	Canonical source	Source-declared stack
Application frontend	axelites/menzzo-meduse-front	Vue 3, Vue Router 4, Vuex 4, PrimeVue, TypeScript and Vue CLI.
Backend, API, jobs and connectors	axelites/menzzo-meduse	PHP ^8.2, Laravel ^8.75, Sanctum, Stancl tenancy and Nwidart modules.

These are package manifest constraints at the linked revisions, not a statement of the installed versions in an environment. The backend also contains a Laravel Mix/Vue 2 scaffold; it is not the separately maintained Vue 3 application above.

Connected Projects

View diagram source

C4Context
  title Meduse in the catalog workflow
  Person(editor, "Catalog editor", "Maintains products and media")
  System(meduse, "Meduse", "Catalog UI, API and processing")
  System_Ext(logidav, "Logidav", "Operational product, stock and price data")
  Rel(editor, meduse, "Edits catalog")
  Rel(logidav, meduse, "Supplies product, stock and price files", "FTP")
  UpdateRelStyle(editor, meduse, $offsetX="-45", $offsetY="-40")
  UpdateLayoutConfig($c4ShapeInRow="2", $c4BoundaryInRow="1")

Diagram

This context view highlights the source-verified inbound operational-data edge. The connector map covers other destinations and the caveat on Meduse's reverse product-export path.

The frontend sends requests to the configured API base URL with a bearer token and, when selected, an AX-Tenant header. The backend owns catalog persistence and the connector/command implementations. Connectors separates Logidav synchronization, Magento file/export processing, and other channel-specific paths instead of treating all of them as one queue.

For changes on the Logidav side, start from its menu and interface map and the Meduse integration contract. Use the workflow pages to identify where data crosses the application boundary.

Local Docs Submodule

The backend declares the shared documentation repository at docs/. Commands for building that submodule are in Local Development; they build this documentation site, not Meduse.

To Expand

The interface, backend and asynchronous processing maps below are source-backed. Environment provisioning, deployed revision, worker supervision, live connector enablement and end-to-end acceptance still need environment-specific evidence.

Dependencies

There are three different scopes to preserve when tracing data: the selected tenant, catalog channel/locale, and connector destination. Do not substitute one for another. See Backend, Connectors and Queues for their implementation boundaries.

Setup

Obtain the assigned development environment and its matching frontend/API URLs from the owning team. Devbox Access applies when that environment is hosted in Devbox; it does not establish that every Meduse deployment is provisioned there.

The frontend's package.json defines serve, build, test:unit and lint scripts. Backend dependencies and scripts are defined in composer.json. Configure only an approved development API and its required tenant before starting the frontend: a local browser can still call a remote backend. This source review did not install or start either application, import a database, invoke Artisan or verify an environment's setup procedure.

Flows

Begin with Meduse workflows for screen/API-to-connector journeys. Stock and catalog covers the adjacent Logidav/Magento flow; its evidence boundary is separate from Meduse's export paths.

Diagnosis

Record the affected screen and action, tenant, channel, product identifier, request endpoint and returned job identifier/status where available. Follow the same operation through API endpoints, jobs, and the connector. A worker exit or successful HTTP response alone does not prove the destination imported or displayed the data.

Evidence and gaps

Important source findings to read before changing these flows:

• Frontend mismatches identify registered screens and helpers that do not reach the expected backend behavior.
• The reverse Logidav product feed has a stopped consumer in the reviewed Logidav revision.
• Queue execution depends on the configured connection; the source default is synchronous, and the kernel's worker examples are commented out.

The pages in this section cite immutable frontend and backend revisions and distinguish active source declarations from commented or legacy examples. They establish code paths, not production process state. No portal login, production command, database inspection, provider request, queue replay or application deployment was performed for this documentation.

Source entry points: frontend manifest, API transport, backend manifest, catalog model, schedule kernel, docs mount.