Why Is Software Documentation Still Static? – WeAreDevelopers World Congress 2026

We had the chance to speak at the WeAreDevelopers World Congress 2026 (Virtual Stage) about a question that has bugged us for a while: why does software documentation still follow a one-way publishing pipeline — Markdown in, static HTML out — when it doesn’t match how developers actually work? Reading, running, changing, observing, debugging: that loop happens somewhere else, never inside the docs themselves. Our answer is to stop treating the browser as a mere display device and start treating it as an application runtime, right there inside the Markdown.

Watch the Talk

In the talk we walk through how LiaScript turns a plain README into that kind of runtime:

• Converting static documentation into an executable environment, without leaving the page
• Embedding and running native JavaScript — including live TensorFlow.js tensor operations and neural network training
• Wiring up Chart.js for dynamic, data-bound visualizations
• Using LiaScript’s macro system to cut down on boilerplate
• Capturing console output and handling asynchronous code cleanly
• Adding interactivity through sliders and responsive data binding
• Enhancing tutorials with animations and text-to-speech narration
• Publishing the whole thing as a decentralized, interactive resource straight from a Git repository

The Slides Are the Demo

True to the talk’s own argument, the slides aren’t a PDF — they’re a LiaScript course, published as a public, CC0-licensed repository. Every code example shown live in the talk (the TensorFlow.js demos included) is in there to read, run, and reuse.

Try It Yourself

Here are the slides in the LiveEditor — change the Markdown on the left and see the result on the right: