Home/Products/Kalenuxer
Kalenux product reference · Open-source build framework

Kalenuxer

Open source. 15+ locales from one source, rebuilt in under a second.

Template includes, variable substitution, multilingual JSON data, incremental builds and one-command deployment in a single pipeline: open source, and refined through years of running real products.

View on GitHub →★5.0 · Reviews7 references
15+languages
<1sincremental builds
3deploy modes
19
15+locales
<1srebuilds
~/my-site
$ kalenuxer build→ 15 locales · 2,140 pages✓ built in 0.8s$ kalenuxer deploy→ uploading 14 changed files✓ live
endefresitptnltrplsvjakozharru
Last reviewed · 28 Sep 2026Maintained by KalenuxSources: official product pages

Kalenuxer is an open-source website build system developed by Kalenux that builds, maintains and deploys every Kalenux web product.[1] It combines template includes, variable substitution, multilingual JSON data, incremental builds and automated deployment in a single pipeline, and its source is published on GitHub.[1]

CITE THIS ARTICLEKalenux. (2026). Kalenuxer. Kalenux product reference. kalenux.com.tr/product/kalenuxer
kalenuxer.config · summary
typeBuild framework
developerKalenux
licenceOpen source[1]
interfaceCommand-line tool[1]
languages15+ per build[1]
build_speedSub-second incremental[1]
deploy_modesfrontend · api · full[1]
built_forKalenux products[1]
sourceGitHub[1]
View on GitHub→
✓stage 01·overview

Overview

Kalenuxer sits between a static site generator and a custom build tool: it handles templating, asset processing, multilingual content and deployment, but stays out of the way of the backend architecture.[1]

It is a production tool, built to solve specific real-world requirements and hardened through years of operating actual products. The source is available for anyone who wants to study or adapt it.[1]

✓stage 02·history and motivation

History and motivation

Kalenuxer was created because existing static site generators were either too opinionated for the server-rendered template integration Kalenux’s projects needed, or too complex to keep lightweight for simple marketing and product pages.[1] In the words of the Kalenux home page, it was built in-house “because nothing else did everything we needed.”[2]

✓stage 03·template system

Template system

The template system is built around two primitives: include directives and variable substitution. HTML source files reference named templates, which are injected at build time; headers, footers, navigation and cookie consent are written once and included everywhere, and a change to a template propagates across every page on the next build.[1][4]

<!-- page.html -->! header !<h1>{ page_title }</h1><p>{ page_intro }</p>! footer !
Directive syntax as documented: ! include_name ! and { variable_name }.[1]
✓stage 04·multilingual builds

Multilingual builds

All user-facing strings, metadata and configuration values live in JSON data files. Each language gets its own file with the same key structure, and the build processes each language independently, producing a complete set of output files per locale from one template. Fifteen-plus languages are supported without changing the HTML, and adding a language means adding a JSON file.[1][2][5]

// en.json// de.json{ "page_title": { "page_title": "Welcome" } "Willkommen" }
✓stage 05·build pipeline

Build pipeline

The pipeline runs as a sequence of stages. Each stage reads source files, processes them and writes output to the distribution directory.[1]

Plugins→Icons→Fonts→CSS→JS→Images→HTML templates→HTML pages→API handlers→Deploy
StageWhat happens
Incremental buildsFile modification timestamps are stored per file; only files newer than their last-processed timestamp are rebuilt. CSS, JS, templates and content are tracked separately, so a stylesheet change does not trigger an HTML rebuild
CSS and JSMinified, versioned with content hashes and injected into pages automatically; an asset manifest maps logical names to file paths
ImagesPNG, JPEG and WebP optimised during the build, with optional responsive variants

On large sites, Kalenux reports that incremental builds cut build time from minutes to seconds.[2]

✓stage 06·deployment

Deployment

Deploy scripts sync the built output to production servers over SSH/SCP in a single command, with no CI service required for small teams. Three modes match the scope of what changed.[1][2][6]

ModeScopeRestart
frontendCSS, JS and HTML onlyNo
apiRebuilds the API serviceYes
fullEverythingYes

For dynamic pages such as articles and user dashboards, Kalenuxer builds the static shell and asset pipeline while server-side templates render the dynamic inner content, so static and data-driven routes coexist in one site.[1]

✓stage 07·documentation

Documentation

Six guides are published on kalenux.com.tr.[1]

Getting Started→Prerequisites, project structure, first build and the output directoryHow to Use→CLI reference, build modes, forcing rebuilds and the asset manifestTemplate System→Include directives, file resolution, URL mappingData & Variables→JSON structure, variable substitution and asset injectionMultilingual→15+ language variants, output structure, RTL supportDeployment→The three deploy modes, SSH key setup, environment variables
✓stage 08·products built with it

Products built with it

Every Kalenux web product is built and deployed with Kalenuxer; the Kalenux page names Kalenux itself, When Notes Fly, Whats Your IQ, Fileformer and QR & Barcode Tool.[1]

When Notes FlyKnowledge libraryWhats Your IQCognitive platformFileformerBrowser-based file toolkitQR & Barcode ToolQR & barcode toolkit
✓stage 09·reception

Reception

On the Kalenux product page, Kalenuxer holds a rating of 5.0 across a moderated review set of 2.[7]

Production-grade architecture, cleanly documented★★★★★
“Reviewed the architecture as part of evaluating build tools for our agency. The approach to CSS/JS versioning, template composition, and deployment is elegant and pragmatic.”
Zara Ahmed, Karachi, Pakistan · May 2026
Impressive static site tooling★★★★★
“The build pipeline Kalenux has developed is genuinely well thought out. The multilingual fanout and templating approach solve real problems I’ve encountered building content sites.”
Pedro Alves, Porto, Portugal · May 2026
✓stage 10·references

References

  1. [1]Kalenuxer Framework: Project Details & Reviews. Kalenux. kalenux.com.tr/product/kalenuxer
  2. [2]Kalenux home page: Kalenuxer Framework section. kalenux.com.tr/
  3. [3]Kalenuxer: Getting Started. Kalenux. kalenux.com.tr/kalenuxer/getting-started
  4. [4]Kalenuxer: Template System. Kalenux. kalenux.com.tr/kalenuxer/templates
  5. [5]Kalenuxer: Multilingual. Kalenux. kalenux.com.tr/kalenuxer/multilingual
  6. [6]Kalenuxer: Deployment. Kalenux. kalenux.com.tr/kalenuxer/deployment
  7. [7]Kalenuxer reviews. Kalenux. kalenux.com.tr/product/kalenuxer/reviews
✓ build complete · 10 stages