MallokMallok

FeaturesWhat ships in 0.1

Everything a multilingual company site needs, and a clear line around the rest.

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

Standard Markdown, stored as written.

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.

  • Draft, published and scheduled states.
  • Content kinds beyond page and article are declared by the theme — the B2B starter brings products, categories, cases, FAQs and news.
  • Content is always treated as untrusted: HTML is sanitised against an allow-list when the fragment is generated, and the stored Markdown is never modified.
  • Export produces the same bundles import accepts. Round-trip fidelity is covered by tests; a full restore into a second live deployment is still on the acceptance list.
a content bundleimport / export format
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

Languages are a property of content, not a plugin.

Each item carries a locale and a translation group. The main language has no URL prefix; every other language is served under its own.

  • hreflang in the sitemap and canonical links are generated automatically.
  • A bundle holds every translation of one item and shares its images between them.
  • Theme interface strings follow the site's language through language packs.
  • 0.1 delivers the model, the URL rules and simple translation management. Machine translation is a roadmap item, not a current feature.
/products/titanium-baren · main language, no prefix
/zh-CN/products/titanium-barzh-CN
/de/products/titanium-barde
sitemap.xmlgenerated
<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

Declarative themes. Real plugins. Both honest about deployment.

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.

  • Themes contain no arbitrary JavaScript; any client script must be declared in theme.json.
  • Switching a theme changes no content id and no public URL. A kind the new theme does not know renders through its page layout.
  • Official and third-party plugins take the same path: source in the repository, bundled at build.
  • Installing or changing a theme or plugin needs a build and a redeploy. Once deployed, a plugin's enable switch, settings and secrets are live from the admin.
  • A plugin runs with real access inside your own account — the same trust boundary as a WordPress plugin. Review it like any other code you ship.
src/themes/atelier/theme.jsonexcerpt
{
  "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

One form, from product page to inbox.

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.

  • Cloudflare Turnstile against spam.
  • Email to you through Resend, with an optional automatic confirmation to the buyer.
  • Every inquiry is stored in D1, readable in the admin like an inbox, exportable as CSV.
  • Third-party keys are encrypted (AES-GCM) before they are stored in D1; they never go into content or source.
  1. Buyer submits the form[[inquiry]]
  2. Turnstilespam check
  3. Stored in D1
  4. Resendemail to you, optional confirmation to the buyer
  5. Admin inboxCSV export

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

An admin that only shows what you can actually change.

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.

  • A Markdown source editor beside a field form generated from the content kind's schema.
  • A media library; uploads are converted to WebP with width variants in the browser.
  • A setup wizard for the administrator, site name, languages, example content and domain.
  • Scoped API tokens for the CLI and for content pipelines.
ContentMarkdown editor + fields from the kind's schema
Mediaupload, WebP variants, picker
Inquiriesread like an inbox, export CSV
Settingssite, languages, navigation, SEO, email, cache
Pluginsenable switch + settings, live
Themes, plugin installneeds a redeploy — and says so

06CLI

The same data path, from a terminal.

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.

CommandWhat 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

Two stages, three caches, one deterministic core.

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.

STAGE ONE · ON SAVE Markdown+ YAML front matterParse + sanitiseremark / rehype, allow-listResolve mediaimages/ → R2 URLs, srcsetHTML fragmentD1 render_cache (derived) STAGE TWO · ON REQUEST (CACHE MISS) Fragment + databounded D1 batchesLiquid themetemplates ship in the WorkerFull pageCache-Control + Cache-TagEdge cachecache.put(), purge by tag Same Markdown + pipeline version + theme version → byte-identical HTML. No clock, randomness or request data in the render core.
LayerWhereKeyWhat it solves
Edge cacheCache APIThe request URLVisitor requests never reach rendering
Fragment cacheD1 render_cacheMarkdown hash + pipeline version + plugin hashA cold render never parses Markdown
Template cacheIsolate module scopeTheme id + versionLiquid is never parsed twice in one isolate

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.

Purge by tag

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.

The edge keeps it, the browser revalidates

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.

Measured on rc.5, one deployment

Cache hit · CPU
0 ms p50 / p95

Maximum 1 ms across 30 confirmed hits. Zero is the value the platform recorded, not a claim of zero computation.

Cold render · CPU, 30 confirmed misses

Free-plan target: 10 ms. Exceeded in 16 of 30 cold samples; none failed.

Mobile Lighthouse
95–97 performance

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

Structured output, built into the core.

Search output is not left to a plugin or to each theme author. Every Mallok site produces the same set.

  • Sitemap with hreflang, RSS feeds, canonical links and Open Graph tags.
  • JSON-LD for Organization, Article, Product and FAQ.
  • Changing a slug writes a 301 redirect automatically.
  • Semantic HTML and no theme JavaScript on content pages. Cloudflare features you turn on, such as analytics, can still inject their own script.
  • sitemap.xml + hreflang
  • RSS
  • rel=canonical
  • Open Graph
  • JSON-LD · Organization
  • JSON-LD · Article
  • JSON-LD · Product
  • JSON-LD · FAQ
  • 301 on slug change
  • signed draft preview links

Deliberately absent: automatic language detection and redirection. Visitors and crawlers get the URL they asked for.

09Static build

Prefer plain files? There is a second path.

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.

  • It touches neither D1 nor the network.
  • Broken references are reported as errors instead of silently dropped.
  • It is a second path beside the Worker, not a replacement: the costs on the right are the price.
terminalthe path without D1
mallok build ./my-site \
  --theme ./src/themes/atelier \
  --origin https://example.com
Inquiry formnot available — removed and reported
Admin editornot available
Instant and scheduled publishingrebuild and redeploy instead

10The boundary

What is live immediately, and what needs a redeploy.

This is the single most important line in the product, so it is drawn in the interface as well as here.

Live immediately

The content timeline

  1. save
  2. D1 write
  3. purge by tag
  4. live
Build + redeploy

The frame timeline

  1. edit source
  2. build
  3. deploy
  4. live

Changed in the admin or through the CLI by whoever runs the site day to day. No build, no deployment.

  • Pages, articles, products, mediacontent
  • Site name, languages, navigation, SEO defaultssettings
  • The options a theme exposestheme options
  • Plugin on/off switch, settings and secretsplugin settings

Changed in the source tree by someone technical. It travels with the code and takes effect on deployment — never as a one-click switch.

  • Switching or editing a themethemes
  • Installing or updating a pluginplugins
  • Moving to a new Mallok releasemallok upgrade
  • A theme switch migrates no content and changes no URLguarantee

11What it is not

Deliberately out of scope for 0.1.

Knowing where a tool stops is part of trusting it.

Not a hosting service

No Mallok accounts, billing or multi-tenant control plane. Your site runs in your Cloudflare account and nowhere else.

Not a shop — yet

0.1 goes as far as inquiries: no cart, payment, membership or comments. Commerce is a later direction, as plugins.

Not a compatibility layer

It does not run PHP, WordPress themes or plugins, or Astro or Next.js projects. A WordPress importer is on the roadmap.

Not for application logic

Sites that need freely written server-side business logic, permission systems or complex form flows are a poor fit.

Not collaborative editing

There is no real-time co-editing in 0.1.

Not multi-cloud

One cloud vendor and one email provider, stated rather than disguised. The mitigation is that content and inquiries export at any time.

12Roadmap

Directions, not commitments.

None of this is in the current release candidates, and none of it has a date.

  1. 0.2

    • A visual editor
    • Product import from CSV
    • An AI translation plugin
    • An inquiry cart: several products in one request for quotation
    • A WordPress importer
  2. 0.3

    • Payment for samples and small orders through a hosted checkout page
  3. 1.0

    • A hosted setup assistant for non-technical owners
    • Marketplaces for themes, starters and plugins

Source: the product vision, section 9. A “Deploy to Cloudflare” button is also planned and is not available yet.

One command. Your account. Your content.

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-site

Needs 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.