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
13 SKUs
Deployed apps
2
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 one app that is deliberately not a 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

Two services, one catalogue.

The storefront reads its products from the Medusa admin. A price changed in the admin changes what the shop shows and what a customer is charged, because the checkout looks every price up from the same catalogue.

Where to change things

Two platforms, on purpose

Vercel runs the edge-rendered frontends; Railway runs 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.