Glemor Fragrance · Documentation

How the shop is run, and how it is built.

Three sections for three different readers. Everything here is written from what is actually in the repository — if a fact is not in the code, it is not on this site.

Products
15 products
Deployed apps
5
Admin edit goes live in
5 minutes
01

Team guide

For Glemor's own team

Adding and editing a product, real photography, correcting scent notes, where orders go, and how long a change takes to reach the shop. No code, no jargon.

02

Engineering

For developers

The architecture, the monorepo and the native Medusa commerce workspace, local development, the three gates, the seed script and both deployments.

03

Changelog

For everyone

What's New in plain language, and the technical log beside it. Both are generated from commit messages — neither is ever written by hand.

Live right now

One catalogue, several surfaces.

The web app reads its products from the native commerce console. Platform, documentation, and API links are kept together so the team can move from account administration to product operations without losing the shared context.

Where to change things

Two platforms, on purpose

Vercel runs the web, platform and documentation apps; Railway runs the API and everything that needs a disk or a long-lived socket — the Medusa server, Postgres, Redis, ClickHouse and Plausible. Neither dashboard can list the other’s services, so this page is the index.