Bounded cold renders
A cold render makes at most four D1 round trips regardless of how much content the site holds. List pages never parse body Markdown and never query per item.
FeaturesWhat ships in 0.1
Mallok is a complete CMS — content, themes, an admin, a CLI, inquiries and SEO — published as one npm package and running as one Worker. This page lists what it does, how it does it, and what it deliberately leaves out.
01Content
Content is CommonMark with GFM and a YAML front-matter block. D1 holds the complete text of each file; images and attachments are referenced by relative path and live in R2.
titanium-price-2026-08/
├── index.md # the default locale
├── index.zh-CN.md # other locales, by filename
├── index.de.md
├── images/ # shared by every locale
│ ├── hero.jpg
│ └── chart.png
└── files/
└── datasheet.pdf
02Multilingual
Each item carries a locale and a translation group. The main language has no URL prefix; every other language is served under its own.
<url>
<loc>https://example.com/products/titanium-bar</loc>
<xhtml:link rel="alternate" hreflang="en" href="…/products/titanium-bar"/>
<xhtml:link rel="alternate" hreflang="zh-CN" href="…/zh-CN/products/titanium-bar"/>
<xhtml:link rel="alternate" hreflang="de" href="…/de/products/titanium-bar"/>
</url>
Simplified illustration of the sitemap output.
03Themes and plugins
A theme is a directory of restricted Liquid templates plus a theme.json. A plugin is real JavaScript with its own tables, routes, settings and scheduled work. Both live in your project's source and are bundled at build time.
{
"id": "atelier",
"kinds": {
"product": {
"layout": "layouts/product.liquid",
"listLayout": "layouts/list.liquid",
"base": "products",
"fields": {
"grade": { "type": "string", "label": "Grade" },
"specs": { "type": "keyvalue", "label": "Properties" },
"gallery": { "type": "image[]", "label": "Gallery" },
"datasheet": { "type": "file", "accept": [".pdf"] }
}
}
},
"clientScripts": [ /* declared, never implicit */ ]
}
04Inquiries
The official inquiry plugin is what turns a catalogue into a sales channel. Put [[inquiry]] in a page and the form renders when the plugin is enabled.
In progress: real Turnstile and Resend delivery has not yet been accepted end to end for the current release candidates. Test with addresses you control before relying on it.
05Admin
A React single-page admin served from the same Worker, in English and Simplified Chinese. Nobody using it needs to know what a Worker, D1 or a cache tag is.
06CLI
The CLI talks to the same management API as the admin, so a folder published from CI and an article saved in the browser are stored, rendered and purged the same way.
| Command | What it does |
|---|---|
mallok create <dir> | Create a project, verify it, then deploy it to your Cloudflare account. --no-deploy stops before any cloud resource is created. |
mallok publish <dir> | Publish one or more content bundles, images included. |
mallok import <dir> | Import bundles, keeping the status their front matter says. |
mallok export <dir> | Export the whole site to a directory of bundles. |
mallok build <dir> | Compile a local directory into a static site, touching neither D1 nor the network. |
mallok upgrade --to <version> | Move a project onto another Mallok release. Takes effect when you redeploy. |
mallok preview <dir> | Render bundles locally, offline. |
Also: media push, setup-key, repair, destroy. Every site command accepts --dry-run and --json. See the CLI reference.
07Rendering and caching
The render core has no platform dependencies, so the CLI's local preview, the admin's live preview and the Worker in production run the same function and produce the same bytes.
| Layer | Where | Key | What it solves |
|---|---|---|---|
| Edge cache | Cache API | The request URL | Visitor requests never reach rendering |
| Fragment cache | D1 render_cache | Markdown hash + pipeline version + plugin hash | A cold render never parses Markdown |
| Template cache | Isolate module scope | Theme id + version | Liquid is never parsed twice in one isolate |
A cold render makes at most four D1 round trips regardless of how much content the site holds. List pages never parse body Markdown and never query per item.
Every page carries Cache-Tags for the site, its content, its kind and its locale. A save purges exactly the pages that show the item. A failed purge is recorded and shown in the admin on main; released candidates up to rc.11 can report a failed purge as success.
Pages are cached at the edge for an hour by default (adjustable) and browsers are told to revalidate, so a purge is not defeated by a copy sitting in someone's browser.
Maximum 1 ms across 30 confirmed hits. Zero is the value the platform recorded, not a claim of zero computation.
Free-plan target: 10 ms. Exceeded in 16 of 30 cold samples; none failed.
Accessibility, best practices and SEO scored 100 in all six runs (home and article).
Read these numbers for what they are. They come from one isolated deployment of 0.1.0-rc.5 on a custom domain. No CPU sample has been taken for rc.6 to rc.11, which add work to cold renders, so these figures do not certify the current candidates. Cold renders above 10 ms CPU are a known, accepted limitation of the release candidates. Full release status
08SEO
Search output is not left to a plugin or to each theme author. Every Mallok site produces the same set.
Deliberately absent: automatic language detection and redirection. Visitors and crawlers get the URL they asked for.
09Static build
mallok build compiles a local directory — the same layout mallok export produces — into a complete static site: kinds, tags, several languages and the SEO endpoints, through the same render functions.
mallok build ./my-site \
--theme ./src/themes/atelier \
--origin https://example.com
10The boundary
This is the single most important line in the product, so it is drawn in the interface as well as here.
Changed in the admin or through the CLI by whoever runs the site day to day. No build, no deployment.
Changed in the source tree by someone technical. It travels with the code and takes effect on deployment — never as a one-click switch.
mallok upgrade11What it is not
Knowing where a tool stops is part of trusting it.
No Mallok accounts, billing or multi-tenant control plane. Your site runs in your Cloudflare account and nowhere else.
0.1 goes as far as inquiries: no cart, payment, membership or comments. Commerce is a later direction, as plugins.
It does not run PHP, WordPress themes or plugins, or Astro or Next.js projects. A WordPress importer is on the roadmap.
Sites that need freely written server-side business logic, permission systems or complex form flows are a poor fit.
There is no real-time co-editing in 0.1.
One cloud vendor and one email provider, stated rather than disguised. The mitigation is that content and inquiries export at any time.
12Roadmap
None of this is in the current release candidates, and none of it has a date.
Source: the product vision, section 9. A “Deploy to Cloudflare” button is also planned and is not available yet.
Mallok creates a Worker, a D1 database and an R2 bucket in your own Cloudflare account and deploys the site there. Nothing is hosted by Mallok, and there is no Mallok account to open.
npx mallok create my-siteNeeds Node.js 22+ and wrangler login. Add --no-deploy to generate and check a project locally without creating cloud resources. Currently a 0.1 release candidate.