Theme / UX Customizer & Mega Menu

主な機能

Drag-and-drop mega menu builder in the Magento admin, gated by a dedicated ACL resource and persisted via declarative db_schema.xml (no core menu tables touched)

Per-top-level-category menu composition: category trees, CMS blocks, banners, featured-product widgets, and custom links arranged in configurable columns

Header and footer layout controls exposed through system.xml configuration and layout-XML handles (sticky, transparent, and multi-column variants) — no PHTML editing required

Rule-based product label and badge widgets ('New', 'Sale', 'Bestseller', custom) injected via a catalog_product_list plugin/interceptor declared in di.xml plus a collection-load observer

Quick view modal built as a RequireJS UI component that loads product data over Magento's native GraphQL/REST without a full page reload

Sticky add-to-cart bar reusing core add-to-cart service contracts, so cart, MSI stock, and configurable/bundle options behave exactly like the native flow

Mobile UX optimizations: off-canvas menu, tap-target sizing, and lazy-rendered menu panels tuned for Core Web Vitals

Full-page-cache compatible — personalized or rule-driven blocks use hole-punching/ESI so caching stays intact on Open Source and Adobe Commerce

Cron job for scheduled badge/label rule recalculation (e.g., sale windows) so labels appear and expire automatically

Theme-fallback-safe templates and Less so your existing theme styling is inherited, not overridden, and Hyvä/Luma layouts are accommodated per build

Admin store-view scoping so menus, labels, and layout options can differ per website/store view in multi-store setups

i18n-ready strings via standard Magento translation (i18n/en_US.csv) for multilingual storefronts

受注生産、すべておまかせ

自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。

ご注文

一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。

構築とインストール

ECOSIRE がお客様の Magento 2 上で構築・設定・インストールします。

本番稼働 + サポート

約2〜4週間で稼働し、リリース後のサポート期間が付きます。

この製品について

This is not an instant Adobe Commerce Marketplace download. ECOSIRE builds, installs, and supports this Magento 2 / Adobe Commerce extension for your specific store, theme, and category structure, then hands over a clean, upgrade-safe module under app/code/Ecosire/ThemeUxCustomizer.

The extension layers conversion-focused UX onto your existing storefront without a full redesign. A drag-and-drop mega menu builder is exposed in the Magento admin under a dedicated menu node with its own ACL resource (Ecosire_ThemeUxCustomizer::menu_manage), persisting layouts to custom EAV-independent tables via declarative schema (db_schema.xml). The menu renders through a layout-XML block and KnockoutJS/Less templates that respect your theme's fallback, so category trees, CMS blocks, banners, and featured products can be composed per top-level category.

Header and footer layout controls are delivered as system configuration (system.xml, config.xml) plus layout-XML handles, letting you switch sticky/transparent headers and multi-column footers without editing PHTML. Product label and badge widgets attach via a catalog_product_list plugin (interceptor declared in di.xml) and an observer on product collection load, so "New", "Sale", and custom rule-based badges appear on listing and product pages. Quick view and sticky add-to-cart ship as RequireJS UI components hitting Magento's native GraphQL and REST endpoints — no page reload, full reuse of the core add-to-cart service contracts.

Everything is cron-aware where it matters (badge rule recalculation), cache-friendly (full-page cache hole-punching for personalized blocks), and works on both Open Source and Adobe Commerce. ECOSIRE delivers source, a deploy runbook, and post-launch support.

得られるもの

A clean, namespaced Magento 2 module delivered under app/code/Ecosire/ThemeUxCustomizer with full source code (composer-installable package available on request)

Installation and deployment on your environment: setup:upgrade, di:compile, setup:static-content:deploy, and cache flush, validated on staging before production

A configured first mega menu, header/footer layout, and an initial set of product label rules wired to your real category and attribute structure

Admin user guide plus a deploy runbook covering upgrade-safe redeploy, cache flushing, and rollback steps

ACL roles configured so menu, label, and layout management can be delegated to specific admin user roles

30 days of post-launch support covering bug fixes and configuration adjustments, with optional ongoing support and Magento-version compatibility plans

これは誰のためのものですか

Merchant improving navigation without a redesign

A store owner whose catalog has outgrown Magento's flat top menu and wants a real mega menu plus conversion widgets, but isn't ready to fund a full re-theme or rebuild.

Marketing / merchandising manager

Owns promotions and category presentation; needs rule-based 'Sale'/'New' badges, banner-rich menus, and quick view to lift conversion — all editable from the admin without a developer in the loop for every change.

Agency or in-house developer inheriting the store

Wants a properly namespaced, di.xml/plugin-based module that respects theme fallback and full-page cache, instead of theme-file hacks that break on the next Magento upgrade.

Theme / UX Customizer & Mega Menu の比較方法

基準	エコシエール	カスタムビルド	競合他社	Magento 2 標準機能
Built specifically for your theme, category tree, and Magento edition	付属	付属	部分的なサポート	含まれていない
Drag-and-drop mega menu builder with banners, CMS blocks, and featured products	付属	部分的なサポート	付属	含まれていない
Rule-based product label/badge widgets via di.xml plugins and observers	付属	部分的なサポート	部分的なサポート	含まれていない
Quick view and sticky add-to-cart reusing native service contracts / GraphQL	付属	部分的なサポート	部分的なサポート	含まれていない
Upgrade-safe (namespaced module, no core file edits, full-page-cache compatible)	付属	部分的なサポート	部分的なサポート	付属
Professional installation, deploy runbook, and post-launch support included	付属	含まれていない	含まれていない	含まれていない
Per-store-view scoping and ACL-delegated admin management out of the box	付属	部分的なサポート	部分的なサポート	部分的なサポート

Theme / UX Customizer & Mega Menu に関するよくある質問

How long does delivery take, since this is build-to-order?

This extension is custom-built, installed, and supported by ECOSIRE — it is not an instant Adobe Commerce Marketplace download. Typical delivery is about 1 to 2 weeks after we confirm your Magento version (Open Source or Adobe Commerce), theme (Luma, Hyvä, or custom), category structure, and any per-store-view requirements. We build and validate on a staging environment first, then deploy to production with you. Tighter timelines can usually be accommodated on request.

What happens with ongoing support and Magento updates?

Every build includes 30 days of post-launch support for bug fixes and configuration adjustments. Because the module is namespaced under app/code/Ecosire/ThemeUxCustomizer and uses di.xml plugins, layout XML, and declarative schema (never core file edits), it survives standard Magento minor upgrades cleanly. For major version jumps (for example a 2.4.x to a future 2.5) or new feature work, we offer optional ongoing support and compatibility plans so the extension is re-tested and re-deployed against the new release.

Does it work on both Magento Open Source and Adobe Commerce?

Yes. The module is built against standard Magento 2 framework APIs — service contracts, plugins/interceptors, observers, layout XML, system configuration, GraphQL and REST — so it runs on both Magento Open Source and Adobe Commerce. Where Adobe Commerce-only features are relevant (such as B2B shared catalogs or page builder content in menu slots), we wire those in during the build for Adobe Commerce environments.

Will it slow down my storefront or break full-page cache?

No. Menus and static layout render through cacheable layout-XML blocks, and any personalized or rule-driven content uses full-page-cache hole-punching/ESI so the FPC stays effective. Quick view and sticky add-to-cart are lazy-loaded RequireJS UI components that call native endpoints, and the mobile menu panels are lazy-rendered. We benchmark Core Web Vitals on staging and tune before handover.

Can the mega menu, labels, and layout differ per store view or website?

Yes. Configuration is store-view scoped using Magento's standard scope system, so a multi-website or multi-language setup can have different menus, different header/footer layouts, and different label rules per scope. ACL resources let you delegate menu, label, and layout management to specific admin roles without giving full system access.