Booth
Shop sites for the people behind folding tables at conventions and craft markets. One template, many tenants, static output.
joyfromtheheart.com is a real jewellery business with a real domain. Fetching it returns a 302 to an Etsy shop. That is the whole market in one observation: the vendor bought a domain, could not build anything behind it, and pointed it at a page where six competitors sit in the sidebar. Etsy owns the customer, the email address and the search ranking, her own domain accumulates no SEO because it serves no content, and there is nowhere to publish which conventions she will be at, which is the single most valuable thing a booth vendor can put on the internet.
The pitch is therefore not that her website is ugly. It is that she already paid for the domain and it is pointed at her competitors.
A client site is a config file, a product file and a folder of photos. Everything that differs between tenants lives in one directory, so customising a shop means editing data rather than forking a template, and the output is static, which is what keeps hosting at roughly nothing per vendor.
The vendor-facing half is a studio that runs in the browser: photos go in, backgrounds come off, and the catalogue it seeds from is a file the build emits. It does the work on the vendor's own machine, which matters because the alternative is uploading a hundred product photos over convention wifi.
Details worth knowing
- 01One template, many tenants, with everything tenant-specific in data rather than in a fork, so a fix reaches every shop at once.
- 02An in-browser studio that cuts products off their background locally, because the job that has to work is the one done on convention wifi.
- 03Static output, so a vendor's hosting cost is close to zero and there is no server for them to be responsible for.
- 04Built around the thing marketplaces cannot do for them: their own domain, their own customer list, and a page saying which conventions they will be at.