Concepts
Step-through diagrams of how the engine works underneath.
How the engine works underneath, one mechanism per page. Each diagram steps through what happens, first in plain words and then in engine terms (switch to Advanced in the top bar).
From a request at the edge to an interactive page: middleware, settings, loaders, SSR, hydration, the SDK.
Server rendering and hydrationYour components run twice, once on the server and once in the browser, and both runs must draw the same page.
Reading and writing dataReads go through loaders, the api modules and the query cache; writes go through window.Salla and come back as SDK events.
Which store, and its URLsHow the engine decides which store a request is for, which hosts may name one, and the store segment on localhost.
Languages and directionThe locale in the URL, when translations load, how your theme strings merge with Salla’s, and how right-to-left reaches the page.
From twilight.json to useTheme().settingsSettings you declare in twilight.json become merchant choices, arrive with the store settings, and reach components through useTheme().
Home page blocksHow a block declared in twilight.json and arranged by the merchant becomes a registry key and then a rendered section.
How hook slots renderWhat happens between hookRegistry.register and the content appearing: priority order, the merged context, subscriptions and apps.
Overriding an engine componentregister, override, resolve: how the registry swaps a component, which names the engine looks up, and the silent no-op.