Operating Dornorium CC
Dornorium CC — "Commerce Core" — is the software that runs your online shop: the products, the checkout, the pages visitors see, and the messages they send you. This manual assumes you've never opened it before. Each chapter explains what a feature is for before it tells you which button does what, so you understand the shop you're building, not just the screen in front of you.
Chapter 1 — Orientation
Before touching any settings, it helps to understand what Dornorium CC actually is and how its pieces fit together. Skim this chapter even if you're impatient to get started — it'll save you a lot of confusion later, because almost every other chapter refers back to something introduced here.
1.1 What CC Actually Is
A working online shop is really three separate things wired together: a website people browse, a database that remembers your products/orders/customers, and a payment provider that actually moves money. Dornorium CC is the layer that sits on top of all three and lets you manage them from one place, in a browser, without writing code or touching a server.
You'll do this through six separate screens, called admin pages in this manual — Workspace, Settings, Files, Store, Forms Config, and Website. Each one owns a different part of the shop, the same way a real shop might have a back office for money, a stockroom for inventory, and a shop floor for what customers actually see. Chapter 1.5 gives you a map of all six before we go further.
1.2 Setting Up the Shop
None of the six admin pages exist until the shop has been "installed" once — a bit like how a shop needs a lease signed and the lights turned on before you can start stocking shelves. This is done with a separate small program called the installer, which you (or whoever set your shop up) run on a computer, not in a browser.
The installer talks to Cloudflare — the company whose servers actually host your shop — and, using an account you provide, creates everything the shop needs behind the scenes: a place to run the shop's logic, a database to remember your data, and storage for your files. When it finishes, it hands you a working website address and creates your very first admin login.
- Open the installer on your computer. It asks a short series of questions, starting with how much you want to configure right now versus later — you can always run it again afterwards if you change your mind.
- Give it your Cloudflare account details. This is the account your shop's backend will actually run on, so it needs to be one you control.
- Choose names for the pieces it creates. If a name you pick is already taken in your Cloudflare account, it tells you plainly and lets you either choose a different name or remove the old thing first — nothing happens silently.
- Let it finish. At the end, it creates your first admin account. Everything after this point — products, pages, settings — is managed in your browser through the six admin pages, not through the installer.
Think of it as the one-time "build the building" step. Day to day, you'll live entirely in the browser-based admin pages covered in the rest of this manual.
1.3 Signing In
Each of the six admin pages checks who you are the moment you open it — there's no separate "master login" you do once for everything.
- Open any admin page (for example
settings.html) in your browser. - You'll see a login box before anything else loads. Enter the admin email and password created when the shop was set up.
- Leave "Remember this device" ticked if this is your own computer — it keeps you signed in on that browser so you're not typing your password in every single time you switch between admin pages. Untick it on a shared or public computer, so the next person who opens the browser doesn't land straight into your shop.
- Click Log in.
Unlike most websites, there's no automatic email reset link built into these admin pages. If you're locked out, you'll need direct access to your Cloudflare account and database to reset it manually — so store your password somewhere safe from day one.
1.4 Finding Your Way Around
Once you're in, every admin page shares the same dark header strip across the top. It has three jobs: it shows you which admin pages you can jump to, it has a 🌙/☀️ switch for light or dark mode (§A.1), and it has a Log out button. If a software update becomes available, a small notification card also appears here automatically (§5.5) — you don't need to go looking for it.
Below that header, most pages use a left-hand vertical sidebar for tabs — for example, Settings has sidebar tabs for Payments, Integrations, Localization, Social, Updates, About, and General. This sidebar pattern repeats across Store and Forms Config: click a tab on the left, and the content fills the right. Once this pattern clicks for you on one page, the rest feel familiar immediately.
1.5 The Six Control Panels
Here's the map. Skim it now; each one gets its own proper chapter later.
You'll move between these constantly as you set up a shop — the header links at the top of every page make that quick, and you generally won't have to log in again on each one, provided you ticked "Remember this device".
Chapter 2 — Getting Paid
2.1 Why You Need a Payment Provider
Dornorium builds your shop's checkout page, but it doesn't move money itself — no shop platform does this on its own, because handling card numbers safely is a specialised, heavily regulated job best left to a company that does nothing else. Dornorium hands that job to PayPal, which is why "connecting PayPal" is really the same thing as "turning your checkout on". Without it, visitors can add things to a cart, but there's nothing at the end of the road to actually charge a card.
The good news is that connecting PayPal also quietly switches on more than PayPal branding — the same connection is what powers card payments typed directly into your checkout, plus one-tap Google Pay and Apple Pay buttons, because PayPal handles all three behind the scenes.
2.2 Connecting PayPal
Open settings.html and click the 💳 Payments tab in the left sidebar.
- Log into your PayPal developer dashboard (a separate site run by PayPal, not Dornorium) and find your app's Client ID and Secret.
- Back in Dornorium, paste the Client ID into that field — this one is safe to be semi-public, it just identifies your app to PayPal.
- Paste the Secret into its field — treat this like a password. Never share it or post it anywhere public.
- Leave Mode set to Sandbox for now (see §2.3 for why).
- Click Save PayPal credentials.
Once saved, a status badge on this tab tells you whether the connection is working. If it isn't, the most common cause is a Client ID or Secret copied with an extra space, or copied from the wrong PayPal app.
2.3 Testing vs. Taking Real Money
The Mode dropdown on the Payments tab is one of the most important switches in the whole shop, so it's worth understanding properly rather than just clicking through it.
Sandbox mode connects your shop to PayPal's practice environment. Test "customers" can go through your entire checkout, and it'll look and behave exactly like the real thing — except no real card is ever charged and no real money moves. This is what you want while you're setting the shop up and testing that everything works.
Production mode connects to the real PayPal network. From the moment you switch to this and save, every checkout on your live site charges a real card. Only switch to Production once you've genuinely tested your whole shop — products, shipping, and checkout — in Sandbox mode first.
A shop that looks finished but still shows Sandbox in this dropdown will let customers "complete" an order without ever being charged. If you've published a site and orders don't seem to be resulting in real payments, this is the very first thing to check.
Chapter 3 — Messages From Customers
3.1 Why Forms Need Their Own Address
Three parts of your shop involve a visitor typing something and hitting submit: the Contact page, the Support wizard, and the Newsletter signup/unsubscribe box. All three are handled not by your main shop, but by a separate, lightweight program called the Forms & Ticketing Worker — built to just receive messages, store them as tickets, and reply, without needing the rest of the shop involved.
Because it's a separate program, your website needs to be told its web address before any of those three features will actually work. That's the entire purpose of the Worker URL field — it's not a feature switch, it's a single address book entry that a handful of pages all depend on.
3.2 Connecting the Forms Worker
Open settings.html → 🔌 Integrations tab.
- Paste the Worker's address into the Worker URL field. It'll look something like
https://your-ticketing-worker.workers.dev. - Click Save Worker URL.
The Integrations tab also houses your Cloudflare API credentials and Turnstile spam protection (§5.2 and §5.3) — they all live here together because they all depend on external connections your shop makes.
If you leave the Worker URL blank, Dornorium doesn't just break — it quietly falls back to a placeholder address that was built into the site when it was created. That's convenient for testing, since Contact and Support pages won't visibly error out, but it means messages may not actually reach you. Always set a real address before launch.
Chapter 4 — Speaking More Than One Language
4.1 How Dornorium Thinks About Languages
A lot of shop software treats "adding a language" as a separate, painful project. Dornorium treats it as a normal, ongoing part of running the shop: almost every screen with customer-facing text — product names, contact form labels, support flow wording, newsletter copy — has its own per-language version, and you can add or remove languages at any point, not just when the shop is first built.
There's no limit baked into the idea of "how many languages a shop can have" — you can run a shop in two languages or in a dozen. What decides how much work it is isn't Dornorium, it's simply how much content you're willing to translate.
4.2 Turning Multi-Language On
Open settings.html → 🌐 Localization tab. This particular switch controls one specific thing: what happens when someone visits your bare domain name with no language in the address.
- Choose Single language if your site only ever speaks one language — visitors land directly on your homepage, no redirect involved.
- Choose Multi language if you're running more than one — visitors are automatically sent to a language-specific folder, like
/en/or/fr/, based on the default you set. - If you picked Multi language, click a language chip to make it the Default — the one used when Dornorium has no other signal about which language a visitor wants. You can also use the Default dropdown below the chips.
- Click Save Languages.
The list of "available languages" you're choosing from here is pulled from the master language registry that also lives on this same tab (§4.3 below). Think of the toggle at the top as the on/off switch and default choice, and the Manage languages card below as where languages themselves are actually created.
4.3 Adding a Language, Any Language, at Any Time
The master list of languages your shop knows about lives on the same 🌐 Localization tab in settings.html, in the Manage languages card. This unified registry is shared across Shop, Forms, and the Localization toggle itself — you manage all language definitions in one place.
- Open
settings.html→ Localization tab → scroll to Manage languages. - Click Add language, and choose the language you want to add.
- Fill in its base text fields on the right, then click 💾 Save language.
- If a translator has sent their work back to you as a file rather than typing it in themselves, use 📥 Import language to load it in one go instead.
- Repeat this for as many languages as your shop needs — there's nothing special about the second one versus the fifth.
Adding a language to this master list is only step one, though — it makes the language available, but your product names (§7.9), contact/support wording (Chapter 9), and site pages (Chapter 10) each still need their own translated content filled in separately, at whatever pace suits you. Chapter 12's closing section walks through exactly what that looks like in practice.
Delete language, on the same tab, removes it completely. Only do this once you're certain nothing on your live site — a page, a product listing, a saved link — still expects that language to exist.
Chapter 5 — Brand & Security
The rest of Settings covers: your social presence linked up consistently across the site, locking your forms down against spam, the live data source toggle, and keeping the software up to date.
5.2 Cloudflare Credentials
Open settings.html → 🔌 Integrations tab. Cloudflare is the company hosting your shop behind the scenes (§1.2). Some features — like the Turnstile spam check below, and software updates (§5.5) — need Dornorium to be able to make small changes in your Cloudflare account on your behalf, which is what these credentials authorise.
| Field | What it's for |
|---|---|
| Account ID | Identifies which Cloudflare account is yours. |
| API Token | A permission key that lets Dornorium act on your behalf. Once saved, it's never shown back to you again — if you need to change it later, paste in a new one; leaving the field blank keeps whatever's already saved. |
| Worker name / Pages project | The exact names given to these when the shop was installed (§1.2). |
Fill these in and click Save Cloudflare credentials.
5.3 Turnstile — Keeping the Robots Out
Any form open to the public internet — your Contact page, your Support wizard — will eventually attract automated spam if left unprotected. Turnstile is Cloudflare's answer to the old "click all the traffic lights" puzzle: a quiet, mostly invisible check that confirms a real person is submitting the form, without getting in a genuine visitor's way. Turnstile settings also live on the 🔌 Integrations tab, directly below the Cloudflare credentials.
You can either connect a Turnstile widget you've already created elsewhere, or let Dornorium create a brand new one for you without leaving this page.
- Already have one? Paste its Site key and Secret key in, list the Hostnames it should be active on (comma-separated, up to 10), then click Save.
- Starting fresh? Click Create Turnstile Widget, give it a name and the same list of hostnames, then click Create in the pop-up — Dornorium creates it directly in your Cloudflare account and fills both keys in automatically.
- Use Show next to the secret key if you ever need to double-check it without having to paste a new one in.
This button switches Turnstile off entirely. It's useful for a moment of troubleshooting, but leaving it off exposes your forms to spam — always turn it back on once you're done investigating.
5.4 Live Data Source Toggle
Open settings.html → ⚙️ General tab. You'll find a card called Live data source with two options: JSON and SQL.
Every site ships with a simple, built-in ("JSON") version of its text — think of it as the factory default. The moment you edit and save something through Forms Config or other tabs, your changes are stored separately in the database ("SQL"). This toggle decides which version your live site actually reads.
If your edits in Forms Config or elsewhere don't seem to appear on the real site, check this switch first — it's almost always the culprit. Flip it to SQL once you've started customising content, and leave it there.
The Shop name field — shown in the top-left corner of the Cart and Order Confirmation pages — lives on this same General tab. Type your shop name and click 💾 Save.
5.5 Software Updates
Dornorium itself is occasionally improved — bug fixes, new features — and the 🔄 Updates tab is how your shop checks for and installs those improvements, the same way an app on your phone updates itself.
- Click Check for Updates. Your current version is shown, and if something newer is available you'll see its version number, when it was published, and a changelog describing what changed.
- Click Apply Update to install it — a progress bar walks you through each step as it happens, so you're never left wondering if it's stuck.
- If an update causes a problem, click Rollback to return to the version you had before.
You don't need to remember to check manually — if an update is available, a small notification card appears automatically in the corner of every admin page. Click View Details on it to jump straight to this tab, Apply Now to install immediately, or the × to dismiss it and deal with it later; it'll simply reappear as a reminder next time you log in.
5.6 About
The ℹ️ About tab on settings.html shows your current Dornorium version information and build details. Useful as a quick reference when contacting support or reporting a bug.
Chapter 6 — Your File Library
6.1 Why Files Live in One Place
Open files.html. Nearly everything visual in your shop — a product photo, a homepage banner, a downloadable spec sheet — is, underneath, just a file sitting somewhere with a web address. Rather than uploading a photo separately every time you need it in a product, on a page, and in an email template, Dornorium keeps one shared library. Upload a file once here, and reuse its address anywhere the shop asks for an image or video.
This also means deleting a file here removes it everywhere it's used — worth keeping in mind before you tidy up (§6.4).
6.2 Browsing & Categories
Down the left side, files are grouped into All files, 🖼 Images, 🎬 Video, 🗄 Data, and 📦 Other, each showing a running count. Click a category to see only that type — useful once you've built up more than a handful of files and don't want to scroll past videos while looking for a product photo.
6.3 Getting a File In
There are three ways in, depending on how much control you need over the result.
- Drag and drop — the fastest way for everyday use. Drag a file straight from your computer onto the dashed box that says "Drag & drop files here to upload".
- ⬆ Upload — click it and pick one or more files from your computer's normal file picker. Dornorium works out the right category (image, video, data, other) automatically from the file type.
- ⚙ Custom… — for when the exact file path matters, not just that the file exists somewhere. Click it, and you'll get to choose the folder and filename yourself, with a live preview of the final path as you type (e.g.
/assets/images/banners/hero-01.webp). Use this if, say, a page you're building in Website already expects an image at a specific address.
6.4 Using a File Elsewhere, and Removing It
Every uploaded file shows as a small card with a thumbnail and two buttons.
| Button | What it does |
|---|---|
| 🔗 Copy link | Copies the file's full address to your clipboard — this is what you'll paste into a product's image field, or a block in Website, whenever it asks for a path. |
| ✕ Delete | Removes the file permanently. |
If a product or a page is still pointing at a file's link when you delete it, that image or video simply stops appearing wherever it was used — Dornorium won't warn you beforehand. Before deleting anything you're not sure about, think through where else it might be in use.
6.5 Storage Space
A small bar at the bottom of the category list shows how much of your available storage you've used, turning red as you approach the limit — worth a glance before uploading a large batch of high-resolution photos or videos at once.
Chapter 7 — Products
7.1 What a "Product" Is to Dornorium
Open store.html, and click the 📦 Products tab in the left sidebar. A product record here is more than just a name and a price — it's everything the storefront needs to show, sell, ship, and translate that item, gathered in one place: its basic details, its photos and video, its stock level, any colour or size variants, physical dimensions, post-purchase actions, and its text in every language you support. Editing a product here is what changes what customers see everywhere it appears.
7.2 Finding a Product
The list on the left shows every product you have, each with its category and price. Type into the Filter products… box to narrow it down by name or SKU as your catalogue grows. Click any product to open it for editing on the right.
7.3 Creating Your First Product
- Click New above the product list. A small "New product" dialog appears asking for an ID (auto-generated from the name if you leave the ID field blank) and a category — fill these in and confirm to create the record.
- Work through the sections described in §7.4 onward. At an absolute minimum, give it a price and a primary image before saving — everything else can be filled in gradually.
- Click Save product at the top of the form.
The same toolbar has a Delete product button next to Save, and it acts immediately on a single click — there's no extra confirmation step. Make sure you're looking at the right product before you use it.
7.4 The Core Details, Explained
| Field | What it means, and why it matters |
|---|---|
| ID (slug) | A short, unique, web-friendly name for the product, used internally and in web addresses. Once orders or reviews start referencing a product by its ID, changing it later can disconnect that history — so it's worth getting right the first time, even if the price and description change later. |
| SKU | Your own internal stock code, if you use one for accounting or a warehouse system. |
| Category | Groups similar products together — used for filtering the shop page and for pointing a Website product grid at a set of related items (§10.6). |
| Price (EUR) | The product's base price. Other currencies shown to customers in different countries are calculated automatically from this using the exchange rates set in §8.2 — you only ever set the price once, here. |
| Discount (%) | Automatically reduces the price by this percentage everywhere it's shown. Leave at 0 for no discount. |
| Weight (kg) | Feeds directly into the shipping cost calculation in §8.1 — worth keeping accurate rather than guessing, since it affects what customers are actually charged for delivery. |
| Stock | How many you currently have available. Once it reaches 0, the product automatically shows as out of stock — Dornorium won't let it be sold past that point. |
| Rating / Review count | The stars shown on the product card. These normally fill themselves in as real reviews come in (§8.3), but you can set them by hand here if needed. |
| Sort order | Lower numbers appear first wherever products are listed together — a simple way to feature your bestsellers or newest items at the top. |
| URL (optional link-out) | Only needed if this "product" entry should actually send visitors somewhere else entirely — for example, a partner's site — instead of opening a normal product page on yours. |
Four checkboxes underneath fine-tune how the product is presented: Up label and Down label turn a small badge on or off, whose wording is set per language on the Translations section (§7.9); Show buy now adds a one-click purchase button; Show quantity selector lets a customer choose more than one at a time; and Show exact stock count shows the real number remaining rather than just "In stock" or "Out of stock" — useful for creating urgency on low-stock items, though not something every shop wants switched on.
7.5 Photos, Gallery & Video
All product media works as file addresses — the actual photos and videos themselves live in the shared library covered in Chapter 6. You can either type a path in by hand, or use the built-in Media Library picker to grab a file you've already uploaded without leaving this screen.
- Primary image path — the main photo shown on the shop grid and at the top of the product page. This is the first thing a customer sees for this product.
- Gallery images — extra photos, added one at a time with Add image. Drag them into the order you want, since the order here is the order they're shown in.
- Media Library — Images — an easier alternative to typing paths: pick a file from the dropdown, then click Set as primary or Add to gallery depending on where it should go.
- Video paths — works the same way as the image gallery, for any product video clips, with its own Media Library — Video picker.
7.6 Colours, Options & Relations
Below the media sections you'll find areas for anything a product can come in more than one form of — different colours, size or style options (material, finish, etc.), and related products to suggest alongside this one. Each works the same way: add a row, fill in its details, and it's saved along with the rest of the product.
Each colour or option row can also carry a sold-out flag, allowing you to mark individual variants as unavailable without removing them from the listing entirely.
7.7 Dimensions
The Dimensions (cm) fieldset lets you record the physical size of a product: Length, Width, and Height. These are informational fields displayed to customers and can be used by shipping integrations that require parcel dimensions alongside weight.
7.8 Shipping & Virtual Products
The Shipping & Virtual Product fieldset has a single toggle: Requires shipping. It's on by default for physical goods. Turn it off for digital downloads, licences, or any product where no parcel will ever be sent — doing so removes the shipping cost calculation and address collection from checkout for that item entirely.
7.9 Post-Purchase Action & Checkout Form
The Post-Purchase Action & Checkout Form fieldset is Dornorium's built-in webhook and checkout form designer — a powerful feature for digital products, licence delivery, integrations with fulfilment services, and anything else that needs something to happen automatically after a successful payment.
The post-purchase action
Configure an HTTP request that fires automatically after a customer completes checkout for this product. The action can be a POST, GET, PUT, PATCH, or DELETE, sent to any URL you specify.
| Field | What it does |
|---|---|
| Action type | HTTP method for the request (POST is most common for webhooks). |
| Target URL | The endpoint that receives the request — your own server, a third-party service, a licence API, etc. |
| Custom headers (JSON object) | Any HTTP headers the target requires, such as {"Authorization":"Bearer …"}. |
| Request body template | The JSON body sent with the request. Supports placeholders: {{order.id}}, {{order.ref}}, {{order.email}}, {{order.amount}}, {{order.currency}}, {{order.full_name}}, and any form field collected at checkout via {{form.field_name}}. |
| Action enabled | Tick to activate; untick to disable without losing the configuration. |
The checkout form designer
Optionally, add a custom form that appears on the checkout page before or after the order summary — giving you a way to collect additional data from the buyer (a licence name, a personalisation note, an account username) that then flows directly into the action's body template via {{form.field_name}}.
- Choose Form placement: before the payment methods, or after the order summary.
- Use the form designer on the left palette to add blocks: 📝 Text (instructional text or HTML), ⌨️ Input (text, email, or number field), or 🖼️ Image.
- Click a block on the canvas to edit its properties in the right panel.
- Choose a Form language — form text follows site language the same way product translations do.
- Click 👁 Live preview to see what the form looks like at checkout.
- Click Save action & form when done.
Use Test action now to fire the configured request immediately with sample data, so you can verify the endpoint is receiving it correctly before any real orders arrive. Remove action clears the entire configuration for this product.
Set action type to POST, target URL to your licence server's endpoint, add a request body template like {"email":"{{order.email}}","product":"{{order.ref}}"}. Add an Input block to the form asking for the customer's desired username. After payment, the action fires with the order details and the username they typed, your server issues a licence, and all of this happens without anyone on your team being involved.
7.10 Selling the Same Product in Other Languages
Some things about a product are the same no matter who's looking at it — its price, its photos, its stock level. Others — its name, its description, the wording on any badge — depend entirely on the language your customer reads in. Dornorium keeps these separate deliberately, so translating a product's text never risks accidentally changing its price or stock by mistake.
- In the Per-Language Text panel on the left, choose a language from the dropdown. (The language needs to already exist in your master list — see §4.3 if it doesn't yet.)
- The form on the right switches to show only the fields that can be translated for that language, including a URL text field that overrides the buy button's text in that language when the product has a link-out URL set.
- Fill them in and save, the same way you would the main product form.
- Repeat for every language you support — there's no limit, and you can do this gradually rather than all at once.
7.11 Backing Up and Bulk-Editing Products
Editing products one at a time in the form works fine for a small catalogue, but becomes slow once you have dozens — the Import/Export tools exist for exactly that situation.
| Button | What it does |
|---|---|
| ⬆ Export products JSON | Downloads every product's core data as a single file — useful as a straightforward backup, or as a starting point to edit many products at once in a spreadsheet or text editor before importing the result back in. |
| 📥 Import products JSON | Loads product data from a prepared file, updating or adding many products in one go. |
| ⬆ Export text / 📥 Import text | The same idea, but scoped to just one language's translated text — handy when sending content out to a translator and bringing their finished work back in. |
Importing overwrites any product that matches by ID. Always export a fresh copy of what you currently have first, so there's something to fall back to if the import doesn't go the way you expected.
Chapter 8 — Running the Shop
Still inside store.html — this chapter covers everything about running the shop day to day once products exist: what shipping costs, which countries and currencies you support, what customers say about what they bought, keeping an eye on orders as they arrive, and controlling the look of your store pages.
8.1 Working Out Shipping Costs
Open the 🚚 Shipping tab. Dornorium calculates shipping in two layers, kept in separate tables on purpose so that importing one never accidentally wipes out the other.
| Table | What it's for |
|---|---|
| Base Settings | Your global defaults — a base rate, a price per kilogram, and the order total that earns free shipping. These apply to every country you sell to, unless a specific country overrides them below. |
| Country-Specific Rates | Per-country overrides — a different shipping zone, an extra surcharge, a different free-shipping threshold, and an estimated delivery time, for whichever countries need something other than your default. |
Add rows with Add key / Add country, or load several at once with 📥 Import rates / 📥 Import countries.
Say you want free shipping over €50 for everyone, but shipping to one particular country genuinely costs more and takes longer. Set the €50 threshold once, in Base Settings — that becomes the rule for every country. Then add one Country-Specific Rate row just for that country, with a higher base price and a longer estimated delivery time. Every other country keeps using your global default; only that one country's row overrides it.
8.2 Currencies & Countries
Open the 💱 Currencies tab. This controls two things at once: which countries appear as options at checkout, and what currency each of them sees your prices converted into — using the exchange rate you set, so you only ever type a price in EUR once (§7.4) and every country's shown price is worked out from that automatically.
| Column | Meaning |
|---|---|
| Code | The country's two-letter code (e.g. DE, US). |
| Label | The country name customers actually see. |
| Currency / Symbol | Which currency that country pays in, and its symbol (e.g. $, £). |
| Rate → EUR | The exchange rate used to convert your EUR prices for that country. |
| Decimals | How many decimal places to display — 2 for most currencies, 0 for currencies like Yen that don't use them. |
| Active | Untick to temporarily hide a country from checkout without deleting the row — useful if you need to pause selling somewhere without losing your saved rates. |
8.3 Customer Reviews
Open the ⭐ Reviews tab and pick a product from the dropdown to see everything customers have said about it — including its star-rating breakdown and any photos or video they submitted along with a review. After making changes, click Save rating breakdown & videos to keep them. Chapter 9.5 covers turning on the automatic email that invites customers to leave these reviews in the first place.
8.4 Watching Your Orders Come In
Open the 💰 Sales tab — a live table of every order placed through checkout.
| Control | What it does |
|---|---|
| Country / month / fulfilled filters | Narrow the table down — for example, to just unfulfilled orders from last month in one country. |
| Search box | Matches by customer name, email, or order ID. |
| Column headers marked ↕ | Click to sort by that column, click again to reverse it. |
| (click a row) | Opens the full order — items, billing and shipping address, and payment status. |
| ⬆ Export CSV | Downloads the currently filtered orders as a spreadsheet-friendly file, for bookkeeping outside the shop. |
8.5 Shop Appearance
Open the 🎨 Appearance tab. This is where you control the visual colours and branding of all default store pages — shop, cart, product, reviews, reviews-display, review-submit, contact, support, subscribe, and the order success page. Website-builder pages use their own styling and are not affected by this tab.
The appearance controls are grouped into logical fieldsets. Each fieldset contains colour pickers — click any swatch to open a colour picker and choose your shade.
| Fieldset | What it covers |
|---|---|
| Brand / store name | Store name colour, accent colour, page background, and body text colour — the foundational palette everything else draws from. |
| Header | Background, text/logo colour, nav link colour, and border colour for the header bar shown on all default store pages. |
| Product card / badge | Card background, title colour, label colour, price colour, and the sale/discount badge background and text. |
| Buttons | Background, text, hover background, and hover text for "Add to Cart" and other primary action buttons. |
| Cart icon | Background, icon colour, hover background, and hover icon colour for the floating cart button. |
| Cart hover panel | Background, text, and border of the mini-cart panel that appears when hovering the cart icon. |
| Category filter chips | Text colour and the active/selected filter chip background and text colour. |
Click 💾 Save appearance to apply your choices. Use Reset defaults to return everything in this tab to the factory colour scheme.
Chapter 9 — Contact, Support & the Newsletter
9.1 One Page, Three Different Jobs
Open forms-config.html. This page controls every word a customer sees on three quite different features — the Newsletter signup, the Contact page, and the Support wizard — plus the actual logic behind the Support wizard's questions and answers.
Most tabs here show a small switch that reads "Live page reads from: JSON / SQL". It's worth understanding, because it's the single most common source of confusion on this page. Every site ships with a simple, built-in ("JSON") version of its text — think of it as the factory default. The moment you edit and save something on one of these tabs, your changes are stored separately ("SQL"). If this switch is left on JSON, your live site keeps showing the original factory text, no matter what you've typed and saved here. If your changes ever don't seem to appear on the real site, this switch is the very first thing to check. (You can also flip this globally from Settings → General → Live data source.)
9.3 The Contact Page
Click the 📝 Contact Form tab. Two separate things live here: the categories a customer chooses from first, and everything else on the page.
Contact Categories
Rather than one open-ended message box, your Contact page starts by asking what a visitor's message is about — Billing, a general question, and so on. This matters because it's what lets you route or prioritise messages later, rather than every message landing in one undifferentiated pile.
- Click ➕ Add category — give it a Label (what the customer reads, e.g. "Billing"), an Icon (an emoji works well here, e.g. 💳), and optionally your own ID (leave it blank and one is generated automatically).
- Click 💾 Save Categories.
Contact UI Strings
Below the categories, every other piece of page wording is grouped into clearly labelled sections — Page Headers, Step 1: Category Selection, Step 2: Form Fields, Buttons, Success State, Validation Errors, and Turnstile/Security messages. Edit whichever fields you want to change, then click 💾 Save Contact UI Strings.
The Export/Import buttons at the bottom of this tab save or load categories and UI strings together, as one file. If you import a file that only contains some of these — say, just UI strings, with no categories in it — only that part gets updated. Anything you already had that isn't in the imported file is left exactly as it was.
9.4 Building a Support Wizard
Click the 🆘 Support Form tab. This is the most powerful part of Forms Config, because it's not just text — it's an actual decision tree. Instead of a blank contact box, a customer with a problem is guided category by category, question by question, either straight to a solution, or, if nothing resolves it, handed off to you with all the useful context already gathered.
Building the flow
- Click ↻ Load current flow first, so you're editing on top of whatever already exists rather than starting from nothing.
- Click ➕ Add category for a new top-level topic — for example, "Order Issues".
- Inside a category, click ➕ Add question, then ➕ Add option for each possible answer a customer might give.
- For every answer, use its Next dropdown to decide what happens once it's picked — either move on to another question, or jump to one of your End Actions, described next.
- Once the tree looks right, click 💾 Save Flow to SQL.
End Actions
Not every answer needs to lead to another question — eventually, a path through the wizard has to end somewhere. An End Action defines what that ending looks like: showing a plain "your issue is resolved" message, or redirecting the visitor somewhere else, like your Contact page. Click ➕ Add end action, name it, and choose whether it shows a message or redirects to a URL. Any answer's Next dropdown can then be pointed at it by name.
Category "Shipping" → question "Has your order arrived?" → one answer is "No, it's late", whose Next is set to an end action called "Contact support" that redirects to your Contact page, already set to the right category. A different answer, "Yes, but it arrived damaged", points to a separate end action for starting a return instead. Two different problems, two different resolutions, without a human needing to read every message first.
Advanced: raw JSON
If you're comfortable editing structured text directly, the "Advanced: edit raw JSON" section shows the entire flow as one block of text you can edit by hand, then bring back into the visual builder with ⬆ Load JSON into builder. ⬇ Export JSON / 📥 Import JSON work as elsewhere — a full backup or bulk-load of the flow, its end actions, and its UI strings together.
Support UI Strings
Underneath the flow builder itself, every other piece of page text is grouped the same way as the Contact tab — Page Headers, each numbered step, Buttons, Success State, Validation Errors, and Turnstile/Security. Edit what you need, then click 💾 Save Support UI Strings.
9.5 Asking Customers for Reviews
Click the ⭐ Reviews Form tab. The post-purchase review request email, the star-rating widget shown on product pages, and the standalone reviews page are all handled by the same Forms & Ticketing Worker as Support and Contact (§3.1) — not by a separate service. This tab shows whether that connection is working; the address itself only needs to be set once, either here or on Settings → Integrations → Worker URL (§3.2) — they're the same setting viewed from two places.
Chapter 10 — Website
10.1 Building Pages Without Writing Code
Open website.html. Everything covered so far — payments, files, products, forms — is the machinery behind your shop. Website is where you actually construct the pages a visitor sees and clicks through: a home page, an about page, a landing page for a seasonal sale. You do this by dragging ready-made pieces, called blocks, onto a page and arranging them — no coding involved, though a Code panel exists for anyone who wants it (§10.5).
10.2 Managing Pages
| Control | What it does |
|---|---|
| ➕ (New blank page) | Creates a fresh, empty page to build on. |
| Pages dropdown | Switch between every page you've already built. |
| 🗑 (Delete this page) | Removes whichever page is currently open. This isn't easily reversible beyond your recent Undo history (§10.4) — make sure it's the right page before clicking. |
10.3 Save, Publish & Preview — Know the Difference
These three buttons look similar but do genuinely different things, and mixing them up is the most common way a shop owner accidentally shows customers an unfinished page, or forgets to show them a finished one.
| Button | What it does |
|---|---|
| 💾 Save | Stores your work-in-progress so you don't lose it. This does not put anything live — a saved-but-unpublished page is invisible to real visitors. |
| 📄 Save As… | Saves a separate copy under a new name, leaving the original untouched — a safe way to try an alternative layout without risking the version that already works. |
| 👁 Preview | Opens the page exactly as a visitor would see it, without publishing anything — always do this before you publish. |
| 🚀 Publish | Takes your saved page and makes it live. This is the only one of the four that actually changes what real visitors see. |
Clicking Save feels like "I'm done", but it isn't the same as putting the page in front of customers. Get in the habit of Save → Preview → Publish, in that order, every time.
10.4 Working on the Canvas
The strip of icons in the middle of the toolbar controls how you're currently working on the page.
| Icon | What it does |
|---|---|
| ↶ / ↷ | Undo and redo your last change — Ctrl+Z / Ctrl+Y also work, if you prefer the keyboard. |
| ⛶ / 🖥 / 📱 / 📲 | Switch the canvas to full width, a desktop-sized frame, a tablet-sized frame, or a mobile-sized frame — use these to check the page looks right at every screen size, since a layout that looks great on a laptop can break on a phone. |
| 📌 (Free positioning) | Lets you drag the selected block, image, or product anywhere on the page with the mouse, instead of it snapping into the normal top-to-bottom order. |
| ▦ (Grid toggle) | Shows a snap-to grid on the canvas, so anything you drag lines up neatly against it. |
| 🧹 (Clear page) | Removes every block from the page currently open — it asks you to confirm first, because this is hard to undo. |
| ⛶ (Focus mode) | Hides both side panels so the canvas fills the screen — press F as a shortcut, or click it again, to bring the panels back. |
10.6 Adding Things to a Page
The left-hand panel has three tabs.
- Blocks — a shelf of ready-made pieces: text, images, buttons, product grids, and more. Drag one onto the canvas to add it to the page.
- Layers — a list view of everything currently on the page, nested to show what's inside what. Useful for selecting something buried inside other elements that's awkward to click directly.
- Design — page-wide design options that affect more than a single block.
Click ‹ to collapse this panel and give the canvas more room, or the lock icon to keep it permanently open while you work.
Drag a product grid block onto the page, select it, open its Settings panel on the right (§10.7), and point it at a category from Store (§7.4) — e.g. bags. Every product you've tagged with that category shows up automatically, and stays in sync as you add or remove products later.
10.7 Styling What You've Added
The right-hand panel has two tabs, and only shows anything once you've selected a block on the canvas.
- Style — colours, spacing, fonts, borders, and other visual properties for whatever's currently selected.
- Settings — the block's own configuration, like which product a single-product block shows, or where a button links to.
10.8 The Floating Toolbar & Symbols
Click any block on the canvas and a small floating toolbar appears right above it.
| Icon | What it does |
|---|---|
| ↑ / ↓ | Move the selected block up or down the page. |
| ⧉ (Duplicate) | Makes an exact copy of the block, placed right next to the original. |
| 🔗 (Turn into Symbol) | Converts the block into a reusable Symbol. |
| ✕ (Delete) | Removes just the selected block. |
A Symbol is worth understanding properly, because it can save you a lot of repeat work. Once a block is a Symbol, every copy of it anywhere on your site stays linked — edit any one copy, and all the others update automatically, without you having to find and change each one individually.
Build your footer once — social links, contact link, copyright line — select it, and click 🔗 to turn it into a Symbol. Add that same Symbol to every page you build. Next year, need to update the copyright year or add a new link? Edit it once, on any single page, and every other page carrying that Symbol updates immediately.
Chapter 11 — Workspace
The Workspace (workspace.html) is your setup launchpad — where you choose the structure and visual starting point for your site before diving into the builder. It's typically the first admin page you visit on a fresh install, and it becomes a handy overview dashboard once your site exists.
11.1 What the Workspace Is For
Rather than starting from a completely blank Website canvas, the Workspace offers you a curated library of Site Kits — pre-built bundles of pages, blocks, and styles that match a particular look and purpose — and a gallery of templates within each kit. Pick a kit that matches your brand direction, choose a template that fits your style, and Dornorium builds out the page structure for you automatically, ready to customise in Website.
If you'd rather start completely from scratch, you can skip kits entirely and design your own site on a blank canvas.
11.2 Choosing a Starting Point (First Visit)
On a fresh install, the Workspace shows a "Choose your starting point" screen with two options.
- Design your own site — skips kits and templates entirely, taking you straight into Website on a blank canvas. Best if you already have a clear design direction or want total control from the start.
- Choose a kit — the kit row shows the available Site Kits. Click one to select it; the template gallery below updates to show only templates that belong to that kit. Use the Style, Layout, and Complexity filters to narrow down, or the search box to find something specific.
You can also shortlist kits and templates to compare them side by side before committing. Click the star ★ on any card to add it to the shortlist, then click ★ Shortlisted in the toolbar to view only your saved picks. The ✨ Surprise Me button picks a random template if you're undecided.
Once you've decided, select the template and confirm — Dornorium builds the site structure and opens Website. The build process takes a moment; a progress indicator keeps you informed.
Once a kit and template are applied, they set your site's page structure. You can change styling and content freely afterwards, but swapping to a completely different kit later will overwrite your existing site (see §11.4).
11.3 Your Existing Site
After your site is built, returning to workspace.html shows an overview card for your current site — its name, the kit it was built with, a thumbnail preview, and quick links to jump into Website or open the live site.
11.4 Changing Your Kit
If you want to try a different kit after your site is already live, the Workspace offers a Change kit flow — the same template gallery as first-run, but with a clear warning banner at the top. Swapping kits replaces your current design entirely. This cannot be undone. Make sure you've backed up anything you want to keep (via Website's Export feature) before proceeding.
Chapter 12 — Start to Finish
Everything above is explained piece by piece. This chapter puts it all together as one continuous example — a small shop called Dornori Studio, selling a canvas tote bag — so you can see how the pieces actually connect when you're setting up a real shop. Follow it in order the first time; the sidebar entries above still work individually if you just need a refresher on one step later.
12.1 What You'll Need Before You Start
Having these ready beforehand means you won't have to stop halfway through to go and find them.
| What | Why you'll need it |
|---|---|
| PayPal Client ID & Secret | To take payments (§2.2) |
| Your Cloudflare Account ID & API Token | To connect Turnstile spam protection (§5.3) |
| 3–5 product photos | Primary image and gallery for your first product (§7.5) |
| Your Forms Worker's web address | So Contact, Support and Newsletter actually reach you (§3.2) |
12.2 Stage 1 — Lay the Groundwork
Open settings.html and log in.
- Payments tab — paste in your PayPal Client ID and Secret, leave Mode on Sandbox for now, click Save PayPal credentials. You'll switch to Production later, right before launch (§2.3) — testing thoroughly on Sandbox first is what keeps you from discovering a checkout bug with a customer's real card in the middle of it.
- Integrations tab — paste your Forms Worker's address into Worker URL, click Save Worker URL. Then enter your Cloudflare Account ID, API Token, Worker name and Pages project name (from installation, §1.2), click Save Cloudflare credentials. Then in the Turnstile card, click Create Turnstile Widget, name it something like
dornori-studio-forms, list your domain (e.g.dornoristudio.com) as a hostname, click Create. - Social tab — click + Add network for each platform you're on, filling in the Base URL and Handle for each, then Save Socials.
- General tab — type
Dornori Studiointo Shop name and click 💾 Save. Leave the Live data source on JSON for now — flip it to SQL once you start customising Forms Config content.
Leave the Localization tab as it is for now — Single language, unless you already know at launch you need more than one. Multi-language setup is genuinely easier to add once your shop and its content already exist, and §12.9 walks through exactly that.
12.3 Stage 2 — Get Your Photos In
Open files.html.
- Drag your five tote bag photos onto the drop zone. Once they've uploaded, click the 🖼 Images category to confirm all five are there.
- Click 🔗 Copy link on the photo you want as the main product image, and paste it somewhere temporary — a notes app is fine — ready for Stage 3.
- Repeat for the other four; these will become the gallery.
12.4 Stage 3 — List Your First Product
Open store.html, clicking the 📦 Products tab.
- Click New, enter ID
canvas-tote-naturaland categorybagsin the dialog, and confirm. - Fill in the core details (§7.4): SKU
DOR-TOTE-001, Price28.00, Discount0, Weight0.35, Stock120, Sort order1so it appears first while it's your only product. - Fill in Dimensions: Length
40, Width35, Height10(in cm). - Leave Requires shipping ticked — this is a physical product.
- Tick Show buy now and Show quantity selector; leave Show exact stock count unticked, so it just reads "In stock" for now.
- Paste your best photo's link into Primary image path, then add the other four via Add image under Gallery images, in the order you want them shown.
- Click Save product.
12.5 Stage 4 — Set Shipping & Countries
Still in store.html.
- Currencies tab — click Add country for each country you'll ship to (say, DE, FR, US), filling in Label, Currency, Symbol, and Rate → EUR for each, leaving Active ticked.
- Shipping tab → Base Settings — add a base rate of
4.90, a per-kg rate of1.50, and a free-shipping threshold of60. - Country-Specific Rates — add a row for the US with a higher base rate (
12.00) and a longer estimated delivery (7-10 days), since it genuinely costs more and takes longer to ship there than within Europe.
12.6 Stage 5 — Set Up Contact & Support
Open forms-config.html.
- Contact tab — add two categories,
Orders(📦) andGeneral Question(💬), then Save Categories. Fill in the Page Headers (Title: "Contact Dornori Studio") and Save Contact UI Strings. - Support tab — ↻ Load current flow, then ➕ Add category named "Order Issues". Add a question, "Has your order arrived?", with two answers: "No" and "Yes, but it's wrong". Add an End Action, "Contact us", that redirects to your Contact page, and point the "No" answer's Next dropdown at it. Save Flow to SQL.
- Newsletter tab — fill in a Subscribe heading ("Join the Dornori Studio list") and subtitle, then Save Newsletter Content.
- Go to Settings → General tab and flip Live data source to SQL, then save. This makes your saved Forms Config content appear on the live site.
12.7 Stage 6 — Build the Home Page
Open workspace.html if this is a fresh site, or website.html if you already have pages.
- If starting fresh: choose a kit and template from the Workspace (§11.2). Once built, Website opens automatically.
- Open your home page from the Pages dropdown, or create one with ➕ if it doesn't exist yet.
- Drag a hero/banner block from the Blocks tab onto the top of the canvas. Select it, open Settings, and set its image to a homepage banner you've uploaded.
- Drag a product grid block below it. Select it and, in Settings, point it at your
bagscategory so your tote bag appears automatically. - Build a footer with your social links and a link to Contact, select it, and click 🔗 in the floating toolbar to turn it into a Symbol — ready to reuse identically on every other page you add from here.
- Click 💾 Save once it looks right.
12.8 Stage 7 — Go Live
- Click 👁 Preview, and check it on desktop, tablet and mobile using the device icons (§10.4).
- Happy with it? Go back to
settings.html→ Payments tab, switch Mode from Sandbox to Production, and Save. - Back in Website, click 🚀 Publish.
- If your changes don't seem to appear for visitors right away, open the ☰ menu and click ♻️ Purge Cache.
Confirm PayPal Mode really is Production, that Turnstile is actually connected, and that the Live data source is set to SQL (§2.3, §5.3, §5.4) — these are the three settings most often left in their test/default state by accident, and the ones that matter most once real customers arrive.
12.9 Expanding Into New Languages
A shop doesn't have to launch multilingual — it's entirely normal to start in one language and add others as the business grows into new markets. There's no cap on how many you can add, and no reason to add them all at once; do it whenever a language genuinely serves customers you have or want. Here's what that looks like for Dornori Studio adding French, and the same steps apply whether it's the second language or the eighth.
settings.html→ Localization tab → scroll to Manage languages → Add language, choose French, fill in its base text, Save language (§4.3).settings.html→ Localization tab → switch to Multi language, click the French chip alongside English to enable it, keep English as Default, Save Languages (§4.2).- Back in
store.html→ Products tab, open the tote bag, switch the Per-Language Text dropdown to French, translate the name and description, Save (§7.10). forms-config.html— repeat the Contact, Support and Newsletter text for French, using the language pickers on each tab.website.html→ ☰ menu → 🌐 Duplicate for Languages to create a French copy of your home page, adjust its text, Save, and Publish.
When German customers start showing up too, you repeat exactly this sequence again — there's nothing different about adding a third or fourth language than adding the second.
Appendix
A.1 Light & Dark Mode
Every admin page has a 🌙/☀️ toggle in the header. Click it to switch between light and dark mode — your choice is remembered on this device, so you won't need to set it again next time.
A.2 Troubleshooting
| Symptom | Likely cause |
|---|---|
| Can't log in anywhere | Double-check your email/password; there's no self-serve reset — see §1.3. |
| Real customers can't pay | PayPal Mode is probably still set to Sandbox — check Settings → Payments (§2.3). |
| Contact/Support/Newsletter pages seem broken or point nowhere | The Forms Worker URL likely isn't set — check Settings → Integrations → Worker URL (§3.2). |
| Bare domain doesn't redirect to a language folder | Multi-language mode isn't turned on, or no default is set — see §4.2. |
| Social icons on the site don't match what you expect | They're pulled from Settings → Social (§5.1) — update the rows there, not on the page itself. |
| Contact/Support forms getting spammed | Check Settings → Integrations → Turnstile isn't accidentally set to Clear/Disable (§5.3). |
| An uploaded image doesn't show up on a product or page | Either the wrong path was pasted in, or the file was later deleted in Files — re-check the link (§6.4). |
| Changes made in Forms Config don't appear on the live site | The "Live page reads from" switch is probably still set to JSON instead of SQL — check Settings → General → Live data source (§5.4) or the toggle on the relevant Forms Config tab (§9.1). |
| Shop name doesn't appear on Cart/Success pages | Check Settings → General → Shop Identity — set the name and save (§5.4). |
| Shipping cost looks wrong for one country | Check whether a Country-Specific Rate is overriding your Base Settings for that country (§8.1). |
| Website changes aren't visible to customers | You Saved but didn't Publish — see §10.3 — or Cloudflare is still serving a cached copy; try Purge Cache (§10.5). |
| Editing a footer/header in one place changed it everywhere | That's expected — it's a Symbol (§10.8), designed to update everywhere at once. |
| An update popup keeps appearing | Go to Settings → Updates and either apply it or dismiss the popup with × — it'll return later as a reminder (§5.5). |
| Post-purchase action isn't firing | Check that Action enabled is ticked on the product, and use Test action now to verify the endpoint is reachable (§7.9). |
| Store page colours look wrong after editing Appearance | Appearance only affects default store pages; website-builder pages use their own styling — check §8.5. |
| Workspace shows "Could not load config.json" | The site may not be deployed correctly yet — verify the Worker URL is set in Settings → Integrations (§3.2). |
5.1 Your Social Links
Open
settings.html→ 📱 Social tab. This is deliberately the only place your social media links are stored. If your site shows a row of social icons somewhere, that block is only choosing which of the rows saved here to display — it isn't storing a separate copy of the link. Update it once, here, and it's correct everywhere.https://instagram.com/— and your Handle, the part unique to you, likedornori.info. Dornorium joins the two together to build your actual profile link.