D Donkeh docs
Documentation GitHub
CSS-driven UI for .NET 10

Build interfaces with real CSS.

Donkeh brings a full CSS engine, a reconciled virtual DOM and native desktop, Android and browser hosts to plain C#. Write components once; choose the platforms you want.

Desktop · OpenGL Android · OpenGL ES WebAssembly · native DOM
using Donkeh.Hosting;
using Donkeh.UILab;
using static Donkeh.UILab.HtmlHelper;

[AppRoot(Width = 1180, Height = 760, Title = "My app")]
public sealed class App : Component
{
    public override Node Render() =>
        Div(new() { ClassName = "app" });
}
Why Donkeh

A UI engine that respects the platform.

One component model, three very different hosts, and no JavaScript runtime required.

#

Real CSS, not a lookalike

Selectors, specificity, cascade layers, custom properties, media queries, keyframes, transitions, gradients, shadows and modern layout.

◫

One tree, four hosts

The same UILab tree renders to OpenGL on desktop, OpenGL ES on Android, or native DOM elements in the browser.

↻

Hooks and context

State, reducers, effects, memoisation, callbacks, refs and typed context providers with in-place reconciliation.

⌕

Built-in inspector

Inspect the live hierarchy, edit matched styles, sample frame/layout/render timings, browse keyframes and build targets.

⌘

A project CLI

Create blank-window projects and components, embed stylesheets automatically, and keep platform entry points out of your app.

◎

Host capabilities

Platform flags and awaitable camera, microphone, location, notification, storage and clipboard permission requests.

Quick start

From zero to a blank window.

Install the CLI, create a project, and run it. The framework supplies the platform entry point.

dotnet tool install --global Donkeh.CliTool
donkeh new project MyApp
cd MyApp
dotnet run

Add another platform later with donkeh enable-target android or donkeh enable-target web.

Documentation

Start where you need.

01

Getting started

Requirements, project setup, directory structure, host opt-ins and the first build.

02

Creating a component

Components, props, stylesheet registration, CSS files and embedded images.

03

Hooks and providers

State, effects, reducers, memoisation, refs, context and reusable custom hooks.

04

The inspector

Explore the hierarchy, edit styles, read performance graphs, browse animations and deploy builds.

05

Host permissions

Platform flags and awaitable device permissions across desktop, Android and the browser.

06

Routing and setPage

Route tables, wildcard paths, active links and navigating from a component with the router context.

07

HTML and CSS reference

Every typed element helper, the registered CSS properties and a bug template with the context we need.

08

Event reference

Every dispatched event, its handler property, event class, payload and host support.

09

Component testing

Mount components headlessly, query the rendered tree and dispatch click, input, scroll, focus and custom events.

10

Image, video and canvas

Replaced content, packed assets, LibVLC playback and GPU drawing — including current browser limits.

11

Implementation for Nerds

Package-by-package design notes: data structures, hot paths, trade-offs and the decisions behind the engine.

↗

Source and releases

Browse the implementation, download the CLI binaries, or cut a release.