Konde Web — render landing pages from JSON

If you have ever shipped a side project, you know the landing page is a strange tax. The product takes three months. The landing page takes the weekend before launch. By the time you have wrestled with Tailwind, found a hero image, written copy, and gotten the responsive breakpoints to behave, you wonder why this part — the easy part — somehow ate two days.

Konde Web is our answer. It is the JSON-to-landing-page renderer that powers konde.io itself, and starting today it ships as a public Konde Studio module.

#What it does

You write a JSON config that describes the page in structured blocks — hero, features, pricing, FAQ, testimonials, footer. Konde Web compiles it to a static HTML site that ships to Cloudflare's edge. The whole loop, from config to deployed page, is under thirty seconds.

A trivial example:

Copy{
  "title": "MyApp — the calmest todo app on the internet",
  "theme": "seafoam",
  "blocks": [
    { "type": "hero", "headline": "Get your day back", "cta": "Download" },
    { "type": "features", "items": [
      { "title": "Local-first", "body": "Your data lives on your laptop." },
      { "title": "No accounts", "body": "Open the app, start typing." }
    ]},
    { "type": "pricing", "tiers": [
      { "name": "Free", "price": "$0" },
      { "name": "Pro", "price": "$29 once" }
    ]}
  ]
}

That generates a real landing page — readable, responsive, themed, with proper meta tags and Open Graph cards — in about 1.5 seconds of compile time.

#Why this exists

Three observations made us build it.

Most landing pages are the same handful of sections. Hero, features, pricing, FAQ, footer. Maybe testimonials, maybe a logo cloud, maybe a CTA strip. The structure is so consistent that it has been a meme for ten years. If the structure is consistent, encoding it as a config is reasonable.

Designers want a tool that does not get in the way. The experienced designers I have watched on Figma → Webflow workflows spend more time on the export-and-rebuild step than on the design. A renderer that takes structured intent and resolves typography, spacing, and responsive behaviour automatically removes most of that pain.

Marketing and engineering should agree on tokens, not pixels. When the brand colour shifts from #15a34a to #16b04f, you want every page in your stack to update — not chase down a hundred Webflow projects. Konde Web reads from KDF (the same theme system the rest of Konde uses), so a token change propagates to every page.

#What blocks ship today

Hero (six layout variants), Features (grid, list, alternating), Pricing (two-tier, three-tier, four-tier), FAQ (accordion, two-column), Testimonials (cards, carousel, single-feature), CTA strip, Logo cloud, Footer (four layouts), Newsletter signup (wired to your Konde Email Sender once that ships).

Each block accepts overrides — colours, copy, image URLs — and falls back to sensible defaults when fields are missing.

#How deployment works

You can render Konde Web pages two ways:

1. Static export. Run kw build and get a folder of HTML/CSS/SVG. Drop it on any host. Zero runtime dependencies.
2. Konde-deployed. From Studio, click Deploy. The page goes to a Cloudflare Worker on your-name.konde.web (or your own domain). Updates ship in seconds.

Both produce the same output — same HTML, same fonts, same theme. The deployed mode is included in your Studio license; you do not pay extra to use our edge.

#What it is not

Konde Web is not a CMS. It is not a blog (that is what Konde Docs is for, and yes, this very post is rendered by Konde Docs). It is not a place to put dynamic content like product catalogs or user-generated stuff. The model is static landing page, ships fast, edits via config.

If you need a CMS, you want Sanity. If you need an e-commerce frontend, you want Shopify. If you need to ship a marketing page in thirty seconds and have it look good, that is what Konde Web is for.

#v2 — late 2026

Today's version is the JSON-config flow. v2 (Q3) adds a visual editor that round-trips with the config — drag a block, the JSON updates; edit the JSON, the canvas updates. A/B testing, lead-capture forms wired to your local Konde data, and component-level animations all land in the same release.

The visual editor will not replace the config. We are explicit about this: the JSON is always the source of truth. The visual editor is a faster way to write that JSON. You can hand-edit any time, and any changes round-trip cleanly.

#Get it

Konde Web is in Studio v1.2 (shipping next week). Public docs at docs.konde.io/konde-web once Studio v1.2 lands. Until then, ping us on X if you want early access.