Studio · ops

Listings module (Studio)

How you enable, seed, and support real-estate listings for brands like Leonardo Armas.

Studio only Phase 1–3

Full product how-to (owner + studio): 34-product-listings. Owner brand guide: 15-owner-leonardo-armas.

Enable on a brand

Studio Modules → listings: true for the site.
Or desk IT / POST /api/business/listings/feature with on: true.
Reload Portal after code deploys so routes exist.

Leonardo Armas (live build)

Slug: leonardo-armas
Site root: Documents\nginx-1.31.2\html\clients\leonardo-armas\
Nginx: conf\sites\leonardo-armas.conf → :8088
Seed: node portal-app/scripts/seed-leonardo-armas.js
Owner desk: /portal/business.html?site=leonardo-armas

Code map

lib/listings.js — DB, CRUD, agents, CSV
server.js — public + business routes
public/js/listings-desk.js + business.html Listings panel
Template public pages: clients/_template/listings.html, listing.html

When the client asks for help

Point them to desk → Help → Listings how-to + their brand guide.
Verify module on + portal health + nginx proxy /portal/.
Photos fail → size/type/disk; CSV → headers + mls_id.

Do not

Put houses in Shop inventory.
Promise live IDX without a separate product decision.
Share other brands’ vault intakes in owner Files by default.