Storefront and content
Change the shop while the campaign is still relevant
A new landing page takes a morning, not a sprint. Pages are sections you move and write yourself, and none of it needs a deploy. This page is built that way.
The editor
What you see in the editor is what customers get
The theme lives in the shop, not in a folder on a developer's machine. You change it in the editor and publish, and there is no deploy to wait for.
If an agency builds your theme, it can be pulled from the agency's GitHub repository or imported as a file — and exported again the day you want the files back.
A section
And a new kind of section is one file
The editor is generated from that declaration. So a new section is one file — not a file, plus a form somebody has to build beside it, plus a validation that has to be kept in step with both.
{% schema %}
{
"name": "Hero",
"note": "Toppen av en side.",
"enabled_on": { "templates": ["index", "page"] },
"fields": [
{ "key": "heading", "type": "text", "label": "Overskrift", "translate": true },
{ "key": "lead", "type": "inline", "label": "Ingress", "translate": true },
{ "key": "image", "type": "image", "label": "Bakgrunnsbilde" }
]
}
{% endschema %}translate: true is the whole of multilingual for that field. And enabled_on is why an e-mail section is never offered on a web page: the placement rule lives in the section, not in a list somebody maintains somewhere else.
Editions
One site, several editions, one set of content to maintain
One site can have several editions: Norway and the UK, a consumer edition and a business one. They share the theme and the content, and override where they say so.
Language and edition are two axes, and conflating them is the mistake this distinction exists to avoid. One language can serve many editions — English in the UK, the US and Australia is the same words and three currencies. One edition can serve many languages.
And sometimes an edition needs different text in the same language. «Fri frakt over 500 kr» is not a translation of «Free shipping over £50». It is an override, and a model that treats an edition as one more language has nowhere to put it.
Fronts
One theme, several places
The website, the e-mails and the pages behind a login use the same colours, copy and settings. Change something in one place and the rest follows.
-
The site
The front page and the pages. The website this page is on.
-
The e-mail
The e-mails your customers get, with the same colours and settings as the website. A colour changed in the editor changes both, in one publish.
-
Behind a login
Pages only signed-in customers see, like a business portal. The sign-in covers the whole portal — not a page here and there.
Questions
About editing
Does a new page need a developer?
No. A page is sections somebody places, and the sections already exist. A developer is needed when a new kind of section is wanted — and then it is one file, not a project.
Can we have our own design?
Yes. A theme is text files; your own theme is your own files. What ships is a starting point, not a frame you have to stay inside.
What about several shops?
Several shops can share a theme and content, or have one each. Bring it to the demo and we will look at what fits you.
Try changing something
In a demo we change a sentence on this page while you watch.