Ox Content wordmark Ox Content wordmark

cargo doc for JavaScript

A framework-agnostic document generator and high-performance Markdown toolkit for the Vite era, with OG images, theming, search, Rust speed, and zero-JavaScript-first MPA output.

Unofficial project notice

This project is not an official VoidZero product.

ubugeeei is building ox-content as an unofficial proposal, hoping it could someday be adopted as vp doc.

The current branding and visual references are unofficial fan work and will be revised or taken down if VoidZero or the relevant rights holders ask.

What Ox Content Is

Ox Content is a Rust-powered document generator and high-performance Markdown processing toolkit for JavaScript and TypeScript projects.

If you want the shortest explanation, it is best understood as cargo doc for JavaScript with a Vite-native workflow.

It also works as a framework-agnostic documentation pipeline with extra batteries included: built-in OG image generation, full-text search, theming hooks, API doc generation, and a reusable content engine.

The site output is zero-JavaScript-first and MPA-oriented by default, so the baseline experience stays fast and simple. When you do need interactivity, Ox Content can hydrate islands and integrate with Vue, Svelte, and React.

Under the hood, Ox Content is not only a docs theme. It also exposes the Markdown parser, renderer, transforms, and plugin system as reusable pieces, so you can use it as a Markdown library outside the default site generator.

Why It Is Fast

  • Implemented in Rust with arena-based allocation and zero-copy parsing where possible

  • Designed to reuse ideas and ecosystem conventions that feel natural alongside the VoidZero family

  • Optimized for static, cache-friendly multi-page output instead of assuming a heavy client runtime

Integrations

Quick Links

Benchmarks

Ox Content is positioned both as a document generator and as a high-performance Markdown toolkit. The numbers below focus on the Markdown engine side.

Latest local benchmark sweep on 2026-04-24 with Node v24.15.0 on Apple M5 Pro. The tables below show median results from 7 local runs of the benchmark harness for the large 48.7 KB case.

Parse Only (48.7 KB)

Library ops/sec avg time throughput
@ox-content/napi 2337 0.43 ms 111.20 MB/s
md4x (napi) 958 1.04 ms 45.56 MB/s
md4w (md4c) 884 1.13 ms 42.06 MB/s
markdown-it 631 1.58 ms 30.04 MB/s
marked 385 2.60 ms 18.33 MB/s
remark 33 29.97 ms 1.59 MB/s

Parse + Render (48.7 KB)

Library ops/sec avg time throughput
Bun.markdown.html 3376 0.30 ms 160.67 MB/s
md4x (napi) 3167 0.32 ms 150.73 MB/s
@ox-content/napi 2599 0.38 ms 123.66 MB/s
md4w (md4c) 2253 0.44 ms 107.21 MB/s
markdown-it 628 1.59 ms 29.91 MB/s
marked 381 2.62 ms 18.15 MB/s
micromark 36 28.16 ms 1.69 MB/s
remark 29 34.97 ms 1.36 MB/s

In this latest local release-build sweep, Ox Content stays ahead for parse-only throughput. The parse+render comparison now includes md4x (napi), where Bun and md4x lead the table and Ox Content remains close behind while still serving as the native core for the full documentation pipeline.

Reproduce with:

node benchmarks/bundle-size/parse-benchmark.mjs

The benchmark includes md4w (md4c) and md4x (napi) by default and adds Bun.markdown.html automatically when bun is available.