Core concepts / The mental model

Four pages will give you the model.

LiveView, Events, Components, Templates — what they are, how they fit together, and why the diff happens before bytes leave the server.

djust borrows the LiveView shape from Phoenix and the component shape from React, and runs both on a Rust VDOM. These four pages are the smallest amount of conceptual material you can read and still build something non-trivial. Twenty minutes total.

Start with LiveView → Skip to the quickstart

python

from djust import LiveView
from djust.decorators import event_handler

class CounterView(LiveView):
    template_name = "counter.html"
    count = 0

    @event_handler
    def increment(self):
        self.count += 1

# counter.html:
# <button dj-click="increment">{{ count }}</button>
#
# That's a working reactive view. No JS framework, no API endpoint.

§ I

The four primitives.

Each page is short and self-contained. Read in order for the linear model; jump straight to a primitive if you already know the rest.

LiveView
~5 min

A Python class with reactive state.

What a LiveView is, where it lives in the request cycle, how the WebSocket upgrade hands off from the initial HTTP render, and how state survives reconnects.
Read the guide →
Events
~5 min

How user actions reach Python handlers.

dj-click, dj-input, dj-submit, dj-debounce. The JSON event payload, the handler-shape contract, and how parameters flow from DOM to Python.
Read the guide →
Components
~5 min

Reusable view fragments.

Stateless components vs. LiveComponent (stateful, lifecycle-managed). Parent-child event bubbling via send_parent; the unified Rust → Python implementation pickup.
Read the guide →
Templates
~5 min

Django syntax, Rust execution.

djust ships a Rust template backend that runs the Django template language at native speed. What's supported, what falls back to the Python backend, and the differences worth knowing.
Read the guide →