Storefronts
Storefronts and themes
How each shop's public site is built and edited.
Every shop has a public storefront on <handle>.ostorya.store. It is rendered by Ostorya from the shop's published theme: no theme code to upload, which keeps every shop fast and safe.
Themes are data#
A theme is JSON: templates made of sections, sections made of blocks, and settings(colors, fonts, radius, texts, images). Ostorya ships the theme library; merchants edit by chatting with the theme assistant or by hand. Through the API you use themeCreate, themePublish, themeSettingsUpdate and themeTemplateUpsert; every value is checked against the theme's schema and refused with a userError if it doesn't fit.
Checkout#
The storefront checkout is a cash-on-delivery form on the product page. It saves abandoned checkouts once the phone number is valid, prices the cart on the server (offers, discounts, delivery) and creates the order with the same orderCreateas the API.
SEO#
Product pages carry schema.org Product data; each shop has its own sitemap.xml and robots.txt.
llms.txt for AI assistants
Every shop also publishes /llms.txt (the catalog as a Markdown list: products with price and stock, collections, pages) and /llms-full.txt (every product in full: options, variants, image, description), in the shop's language, so ChatGPT, Gemini, Perplexity and Claude can read and cite the shop. Both follow llmstxt.org and update with the catalog.
Indexing starts with the first product
A shop with no active product answers 404 on llms.txt, has an empty sitemap and a robots.txt that asks crawlers to wait. Everything opens by itself when the merchant activates their first product, so search engines and assistants meet the shop with real products, not an empty page.
Not available yet
A public Storefront API (for headless shops) and custom theme code. Custom domains per shop are planned.