Featured

Why Lambda Script: Documents as Data

April 2026

Lambda Script approaches documents differently. Instead of treating formats as output targets, Lambda parses 20+ input formats into a unified Lambda/Mark node tree. This means your Markdown, HTML, JSON, YAML, LaTeX, or CSV files become structured data you can query, transform, validate, and render — all with one language and one runtime.

Where most workflows require stitching together pandoc, jq, custom scripts, and template engines, Lambda provides a single, coherent pipeline:

// Parse any format → unified tree → transform → output
let doc = input("report.md", 'markdown')
let images = doc?<img> | ~.src
let headings = doc?<h1> ++ doc?<h2>

// Build a styled HTML page with a table of contents
<html
  <head <title "Report">>
  <body
    <nav <ul (for (h in headings) <li h[string]>)>>
    doc
  >
>

Combined with JIT-compiled performance (competitive with V8, 13× faster than CPython), a rich type system, and a built-in HTML/CSS/SVG layout engine, Lambda Script is designed for anyone who processes documents or structured data as part of their workflow.

Get started →

Coming Soon

Tutorial

Convert Markdown → Styled HTML with Lambda Script

Step-by-step guide to building a custom Markdown-to-HTML pipeline with CSS styling.

Comparison

Pandoc vs Lambda Script: Where Each Fits

An honest comparison of Lambda Script and Pandoc for document conversion workflows.

Deep Dive

Designing Schemas for Document Trees

How Lambda's type system enables schema validation for complex document structures.

Tutorial

Functional Scripting for ETL Pipelines

Patterns and best practices for data extraction, transformation, and loading with Lambda.

Subscribe to stay updated. More content coming soon.