Ameubleo

Purpose

ameubleo is a storefront implementation in the Menzzo ecosystem. It contains WordPress/WooCommerce theme and integration work for the Ameubleo commerce site.

Stack

• WordPress and WooCommerce.
• PHP 8.1-oriented theme/plugin work.
• Razzi child-theme customizations.
• Composer-based quality tooling where configured.

Connected Projects

• Menzzo Magento and catalog sync remain upstream product sources.
• Pricing, stock, and catalog behavior connect back to operational data from Logidav and catalog services.
• Storefront incidents may require checking Magento, catalog, and WordPress layers together.

Local Docs Submodule

When this repo consumes global docs, use:

cd docs
npm ci
npm start
npm run build

To Expand

• Local WordPress setup.
• Theme customization boundaries.
• Product/price sync path.
• Checkout and payment troubleshooting.

Dependencies

This page documents links to Magento/catalog and media inputs at a high level. The exact product, price, stock, image, and checkout contracts are not recorded here.

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

Stock and catalog describes shared product-data ownership. No Ameubleo-specific checkout or publishing flow is source-mapped yet.

Diagnosis

For a storefront mismatch, first record the affected page and product identifier, then separate theme rendering from upstream product data. A repo-specific local setup and incident runbook are missing here; do not infer either from the docs-site commands above.

Evidence and gaps

The page has a stack summary and documented relationships, but no source commits, local WordPress setup, theme boundaries, checkout contract, or deployment runbook.

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.