llux-website

Llux Language Reference

Status: Pre-release reference

This page describes the active Llux language direction. Older drafts used computed, command, effect, resource, and layout; those terms should be treated as historical or draft terminology unless reintroduced deliberately.

Core Principles

1. Plain names, clear intention. Keywords use ordinary words.
2. Explicit scope. State is addressed through scopes such as app.count, session.user, or component.value.
3. Four core constructs. The language centers on state, bind, action, and view.
4. One language everywhere. .llux carries implementation; .llux.md can reference Llux expressions with @.
5. Kind errors. Errors should identify the root cause, location, and likely fix.

File Types

Extension	Purpose
.llux	Logic, state, actions, and views.
.llux.md	Intent, layout, semantics, and design-time explanation.
.lmd	Short extension for Llux Layout Markdown.

Entrypoint

Item	Decision
Entrypoint file	start.llux
Root view	RootView

The naming follows the same style as README: direct and human-oriented. start.llux means “start here.”

Constructs

state

Mutable data. State should be explicitly scoped.

app state {
    count = 0
}

session state {
    user = null
}

Use scoped references:

app.count
session.user
component.value

bind

Derived data or reactive binding.

bind double = app.count * 2

action

A state-modifying operation.

action Increment(amount = 1) {
    app.count += amount
}

view

Visual structure.

view RootView {
    Panel {
        Label { text: "Count: " + app.count }
        Button { label: "+1"; action: Increment(1) }
    }
}

Layout Markdown Glue

Layout Markdown is for structure and intent. Use @ when a Markdown attribute should be interpreted as a Llux expression.

::: button action=@Increment(1) label="+1"
::: label [email protected]

The @ prefix means “evaluate this as Llux.”

Components

The planned component model uses one folder per component:

component/
  component.toml
  intent.llux.md
  logic.llux
  assets/
  tests/

Components communicate through declared capabilities rather than hidden cross-component coupling.

Current Parser Note

The parser also recognises supporting top-level forms such as services, import, and component. Public examples should still emphasise the four core constructs unless they are documenting those supporting forms directly.

Historical Terminology

Older term	Current direction
computed	Prefer bind.
command	Prefer action.
layout	Prefer view for .llux; use Layout Markdown for .llux.md.
resource / effect	Treat as draft design space until re-specified.

This site is open source. Improve this page.