Mosaikasa

Purpose

mosaikasa is a storefront/theme repository in the Menzzo ecosystem. It contains presentation-layer assets and theme code for the Mosaikasa commerce experience.

Stack

• Theme assets with Liquid-style templates.
• JavaScript and CSS customizations.
• Storefront configuration and static assets.

Connected Projects

• Catalog and product data originate from the shared commerce ecosystem.
• Media/image tooling provides storefront assets.
• Magento/operations systems remain upstream for product, price, and stock truth where integrated.

Local Docs Submodule

When this repo consumes global docs, use:

cd docs
npm ci
npm start
npm run build

To Expand

• Theme development workflow.
• Deployment/publishing process.
• Deployed product data sync configuration, creation and category mapping.
• Storefront QA checklist.

Dependencies

The page documents a theme/storefront boundary and high-level product/media dependencies. The exact commerce backend and field-level sources are not verified.

Setup

Application setup is not established by this page. Follow the owning repository's README and setup instructions, and request the approved local access or environment you need. The shared documentation submodule and docs-site commands are described in the repository map and local development guide; they do not start this application.

Flows

Start with Central Meduse to Mosaikasa and Shopify for the source-traced targeted sync and its evidence boundaries. Shared stock/catalog context is in Stock and catalog. Storefront publishing and complete QA paths remain to be verified.

Diagnosis

For a displayed product mismatch, record the storefront URL and product identifier, then identify the first upstream state that differs. The product sync runbook identifies checkpoints and report statuses. Theme development, publishing, and complete storefront QA guidance remain missing.

Evidence and gaps

The stack and broad upstream relationship are documented only; source refs, setup, deployment, and field/stock contracts remain unknown.

Next evidence to add: source commit and file references for the owned boundary, then repository-specific setup and the relevant operations procedure. See the documentation coverage matrix for the system-wide gap record.