Feature Overview

Everything Your Text Pipeline Needs.

From raw Markdown to production-ready PDFs. Texkit provides the engine, the validation, and the integration you need to Compose. Compile. Ship.

Explore Capabilities

The Engine

Templating Engine Deep-Dive

A logic-aware templating language with typed variables, conditional blocks, and loops. Write once, render anywhere.

Variable Injection & Data Binding

Texkit parses YAML front-matter and JSON metadata into a typed context. Access data using the {{ variable }} syntax. The engine handles nested objects, arrays, and computed properties automatically.

Variables are type-checked at compile time, preventing runtime errors where undefined keys might render as empty strings.

Conditionals & Logic

Control the flow of your documents with {% if %} and {% else %} blocks. Logic is evaluated against the document context, allowing for dynamic content generation based on metadata, user roles, or build flags.

# Example: product-spec.txk

title: {{ product.name }}

category: {{ product.category }}

if product.stock < 10:

⚠ Low Stock Alert

Availability: Out of Stock

else:

Availability: In Stock

Price: ${{ product.price }}

for feature in product.features:

- {{ feature }}

Quality Assurance

Schema-Driven Validation & Linting

Define JSON Schema or custom rule sets for your document metadata and content. Invalid documents fail fast with precise, line-level error messages.

JSON Schema Support

Validate structure, types, and required fields against standard JSON Schema definitions. Ensure every document adheres to your organizational standards before compilation begins.

Custom Linters

Write custom validation rules in JavaScript or TypeScript. Enforce terminology consistency, check for broken links, or validate API versioning in your documentation.

Fail Fast

Stop the build process immediately upon encountering validation errors. Texkit provides actionable error messages pointing directly to the source file and line number.

Multi-Format Output

Emit Any Format

From a single Markdown source, generate HTML, PDF, EPUB, plain text, man pages, and custom formats. Output adapters are first-class plugins.

HTML Static sites & web apps
PDF Reports & manuals
EPUB E-books & readers
Markdown Source preservation
Plain Text Logs & alerts
Custom API docs & JSON

Extensibility

Plugin Architecture

Extend Texkit with custom transformers, renderers, and validators. The plugin API is designed for TypeScript users with full type safety.

First-Class Hooks

Plugins hook into specific stages of the pipeline: onParse, onTransform, onValidate, onRender, and onEmit. Each hook receives a typed document context and returns a transformed context.

Whether you need to integrate with a legacy CMS, generate a custom XML schema, or perform heavy data enrichment, plugins run in isolation and can be swapped out without touching the core engine.

Community Ecosystem

Browse the Texkit Registry for plugins ranging from PDF generation (via Puppeteer) to API documentation generation (via OpenAPI specs).

npm texkit-plugin-pdf

Developer Experience

Live Reload & Watch Mode

Develop locally with instant feedback. The CLI watches your source files and recompiles automatically as you type.

Instant Watch Mode

Run texkit compile --watch to keep your build process alive. Changes to Markdown, templates, or config files trigger immediate recompilation.

Git-Native Diffing

Compare your compiled output against the previous build. texkit diff generates a unified diff view of the generated HTML or text, making it easy to spot unintended changes.

Comparison

Why Choose Texkit?

Texkit

The Platform

Full pipeline orchestration
Schema validation & linting
Multi-format output
Plugin architecture
Git integration & diffing

Manual Scripts

The DIY Approach

High initial setup time
Brittle error handling
Hard to maintain across teams
Requires scripting knowledge
Manual deployment steps

Alternatives

Static Generators

Focus on static sites only
Weak templating logic
Difficult to integrate into CI/CD
Less control over output format
Manual validation required