A Website is pages written as Liquid templates and the files they use, published to the web when you choose. A Domains resource holds domain names and their DNS.
Add either from Add in a project. A new website starts with a layout, a header snippet, a home page and a /404 page, ready to publish.
At a glance
tensorsites.netWebsites
A website's page lists its templates by kind, then its assets. Choose one to edit it in a pane beside the list; the + beside a kind makes a new one.
| Kind | Named by | What it is |
|---|---|---|
| Page | Its route, such as /about | What the site answers at that address. |
| Layout | A name, such as default | The frame pages that name it are drawn in ({% layout %}), its {% block %}s filled by them. |
| Snippet | A name, such as header | A piece any template draws in with {% render %}. |
| Data | A name, such as posts | JSON every template reads as site.data.posts. |
Names are lowercase letters, digits, - and _, and may sit in folders (partials/nav). What you type and haven't saved stays with the template in this tab, marked in the list, and the tab asks before closing with anything unsaved.
{% layout 'default', title: 'Home' %}
{% block content %}
<h1>Welcome to {{ site.name }}</h1>
<p>Edit this page, add pages, layouts and snippets, …</p>
{% endblock %}Websites
/ and /about answer those addresses alone./blog/:slug answers /blog/hello and any other one segment there, read as route.params.slug./files/*path, last in a route, takes everything after it: /files/a/b.txt gives route.params.path a/b.txt./404 answers whatever nothing else does.Of several routes that match, the closest wins: a name over a :param over a *rest, from the first segment on. A route ending in an extension answers as that type: /feed.xml as XML, /robots.txt as text, anything else as HTML. A site without its own /sitemap.xml or /robots.txt is given them, listing its pages.
Websites
Assets are the images, fonts, scripts and other files the site uses. Drop files anywhere on the website's page, or open Assets and upload them, in folders if you like. Each is served at its own path (/images/logo.png) and, through the asset_url filter, at an address of its contents that browsers keep for good.
A request with no page of its route is answered with the asset at that path, else that path's .html, else a folder's index.html, so a site of uploaded files works as it is.
Websites
Edits never reach the live site until you publish again. Settings' Unpublish takes the site offline.
Websites
On Pro and Enterprise a site can be served at up to five domains of your own, besides its own address.
CNAME record for it pointing at the site's own address. A domain that can't have one, such as example.com itself, uses its DNS host's ALIAS or ANAME instead, with the TXT record shown.A domain in one of your Domains resources needs none of this: connect it from there.
Domains
A Domains resource holds domains registered here and domains registered elsewhere whose DNS is hosted here, each with its DNS records, contacts and certificates. Organize them in folders. Purchases are charged at once to your organization's billing card, which any plan may have; a resource's Settings › Purchases lists what was bought.
Domains
acme or acme.com.A domain registered here renews by itself, and comes with a transfer lock, WHOIS privacy, our DNS and a free certificate for it and its www.
Domains
Choose Add an existing domain for one registered elsewhere, and either:
TXT record shown, then point it at our nameservers.Domains
Open a domain to see its records. Add, edit and delete them, filter them by type, name or value, and import or export a zone file. Set up mail adds the records a common mail provider needs. Records the app keeps for you, such as a website's, are marked; editing one of a website's records disconnects that address from the site.
Its Nameservers are ours unless you choose others, and every change to the domain is in its History.
Questions or something missing? Contact us.