Sites
A folder in sites/ is one Site, its Pages, navigation and Brand, served on its Domains.
A folder in sites/ is one Site: its Pages, navigation and Brand, served on its Domains. It implements the Site product.
sites/www/site.mdxDomains, navigation, themelayout.mdxwraps every Page belowpage.mdx/pricing/page.mdx/pricingblog/[post]/page.mdx/blog/:postnot-found.mdxunmatched paths
Reference
A Site is always a folder, even when the Startup has one. site.mdx is frontmatter only.
| Key | Type | Holds |
|---|---|---|
domains | hostnames | Where it serves; the first is canonical |
nav | list | Navigation: label and path |
theme | path | A Theme in brand/; the Brand's by default |
extends | Template id | The site Template it starts from |
Examples
Minimal
---
domains: [leaseline.com]
---Leaseline
---
domains: [leaseline.com, www.leaseline.com]
nav:
- { label: Pricing, path: /pricing }
- { label: Blog, path: /blog }
- { label: Sign in, path: /app }
---What it builds
The SiteBuilder compiles the folder and publishes it with Site.publish.
- a
Site, aPageperpage.mdx, and one Page per member under a[key]folder - a Markdown twin of every Page, and
/llms.txt,/agents.jsonand/sitemap.xml - generated
/termsand/privacy - the Event
Site.published
Routing
A folder is a URL segment and page.mdx makes it public. route segments covers groups, keys, private folders and Variants.
Good to know
- Every Site reads the pricing section from published Offers.
- The storefront and portal are Pages of the same Site; see storefront.