File architecture
You don’t need to edit code to run Masa. This map shows how Masa’s `masa-*` files are structured under the hood.
- masatheme/
Folder
templates/
JSON blueprints for every page type — including `collection.map.json` for room/stage merchandising and `page.contact.json`.
How often you’ll touch it: Through the Theme Editor
01templates/index.json02templates/product.json03templates/collection.json04templates/collection.map.json05templates/page.contact.json
layout/
Outer shells (`theme.liquid` and `password.liquid`) that wrap every page with the header, footer and cart drawer.
templates/
JSON blueprints for every page type — including `collection.map.json` for room/stage merchandising and `page.contact.json`.
sections/
The 32 modular `masa-*.liquid` sections (Campaign hero, Category stories, Ages, Doorframe, Size chart, Product, Collection).
snippets/
Reusable Liquid partials powering size-stage mapping (`masa-size-map`, `masa-size-age`), height check (`masa-product-jamb`), cards and filters.
assets/
Scoped CSS (`masa.css`, `masa-styles.css`, `masa-studio.css`) and modular JS (`masa-stage.js`, `masa-height.js`, `masa-cart.js`, `masa-quick.js`).
config/
`settings_schema.json` defines all 4 composition options and 14 color tokens; `settings_data.json` stores the 4 presets.
locales/
Merchant-editable storefront text and Theme Editor schema labels (`en.default.json`, `en.default.schema.json`).