Glossary
The 3D and editor terms Volux uses across its UI and docs, in plain language.
3D tools borrow heavily from modeling and game-engine vocabulary. These are the terms Volux uses in its interface and this documentation, in plain language.
- Action — something an event does when it fires: switch a state, tween a transition, play a clip, open a link, start physics. One event can stack many actions.
- Auto-key — an editor mode (armed by default) that records a keyframe automatically whenever you move a selected object while the timeline is open. Only the properties you actually change get keyed.
- Band — a device-width range in your document's responsive settings, such as desktop or tablet. Settings scoped to a band apply when the visitor's viewport falls in that range; each width value in the definitions means "at or below".
- Breakpoint — a width boundary you define for a document that splits it into bands. Desktop is always present; you add more (tablet, mobile) and refine settings per band.
- Bake — freezing computed results into plain data: a physics simulation baked into keyframes, or a modifier stack baked into real geometry. After a bake the render path reads the result directly instead of re-computing it.
- BYOK — "bring your own key". The AI builder connects to your AI provider with your own API key, stored per user on your own site. The agent loop runs in your browser; no keys or prompts ever leave your WordPress install toward Volux the company.
- Clip — one keyframe animation track set on an object, with a duration and a loop mode. Clips play on a shared scene timeline.
- Constraint — a rule that holds an object in a relationship (to its parent, the ground, or another object) and is solved on top of its authored transform every frame, without ever writing that transform.
- Document — the WordPress post or page a Volux project lives in. It holds the scenes, the DOM tree of page elements, and all settings.
- DOM element — a real HTML element on the page that Volux has registered so it can host a scene or carry its own states and triggers (click, hover, scroll).
- Emitter — a particles object. Its settings decide the spawn shape, rate, direction, and lifetime of the particles; the simulation itself runs entirely on the GPU.
- Force field — a separate object that steers every emitter's particles scene-wide: Wind, Vortex, Turbulence, Attractor, Drag, Harmonic, or Curve Guide. Placement and falloff are your per-emitter tools.
- Gizmo — the on-screen handles over a selected object: arrows for moving, rings for rotating, boxes for scaling. Also the small orientation cube in the preview stage.
- Grace state — a license window. When a license has expired or hit its activation limit but the server grants grace, existing Pro content keeps rendering and editing; only creating new Pro content is blocked until you renew.
- Keyframe — a recorded value (position, rotation, scale) at a moment on the timeline. Between keyframes, values interpolate.
- Kinematic sweep — a physics move driven by animation: a Transition action carries a participating body along the exact tween path, colliding as it goes, then hands it back to the simulation at rest.
- Linked element — the page element a scene renders into. Linking is what puts a scene on the published page; a scene with no link never renders.
- Material layer — one entry in an object's material stack. Layers blend top-down — Color, Image, Noise, Glass, and more — each with its own controls, blend mode, and strength.
- Modifier — a non-destructive geometry operation in an object's stack — Subdivision, Simplify, or Cloner. The stack re-evaluates on demand; the base mesh stays untouched until you bake.
- Node — anything in a scene's tree: meshes, cameras, lights, text, curves, speakers. Every node can be selected and transformed; meshes carry materials, and objects can carry events.
- PBR — "physically based rendering", the lighting model Volux materials use. Textures carry real-world channels — color, roughness, metalness, normals — so surfaces react to light consistently.
- Personal camera — the editor-only free-navigation camera. It exists so you can inspect scenes freely; it never becomes a visitor's view and is never saved into the document.
- Scene component — a scene snapshot saved to My Assets. Inserting one copies the entire scene — objects, materials, cameras — into the current document as a fresh, editable copy.
- Shortcode — the
[volux_scene]marker WordPress stores in post content when a document saves. It marks where scenes belong; the page's JavaScript does the actual rendering. - State — a named moment of an object or element, such as hover or pressed, holding its own copy of settings. Interactions and events switch between states; each state can be refined per band.
- Structural key — the fingerprint that decides whether a material rebuilds. Changing a layer's kind or order rebuilds the shader; changing a value like color applies instantly.
- Trigger — the "when" half of an event: mouse up, key press, page start, collision, distance reached, and so on.
- TSL — "Three.js Shading Language", the node-based shader system Volux materials compile to. It is why layers, blending, and PBR channels all work without writing shader code.
- Viewport — the preview stage in the editor: a live view of the published page with every scene rendered on top, navigated by orbiting and zooming.
Next
- Keyboard Shortcuts — the editor's keys in one table.
- Core Concepts — how these pieces fit together, in depth.
FAQ
Common questions about requirements, licensing, import formats, upgrading, and getting help.
Keyboard Shortcuts
Every editor shortcut, generated from the live keybinding table.
Last updated on