Navigated to /docs/core/glossary

Tavo.js glossary

Look up the framework terms used throughout Tavo.js guides and API references.

Application and routing terms

TermMeaning in Tavo.js
RouteA public URL pattern discovered from a non-underscore module in src/pages.
Page moduleThe file that supplies a route component and optional loader, action, middleware, metadata, and render policy.
LayoutA _layout.tsx module that wraps matching descendant routes and may own its own loader, middleware, and metadata.
Route groupA folder in parentheses that organizes routes or layouts without adding a URL segment.
LoaderRequest-owned read operation that resolves data before a route or layout renders.
MiddlewareOrdered route work that either continues resolution or redirects before loaders run.
ActionA server handler for a non-GET request to a route, normally used for mutations and forms.
HydrationAttaching Tavo.js's browser runtime to server-rendered HTML using the same serialized route state.

Rendering terms

TermExpanded formMeaning in Tavo.js
CSRClient-Side RenderingThe server sends a document shell and the browser resolves and renders the route.
SSRServer-Side RenderingTavo.js resolves and renders the route for an incoming request, then the browser hydrates it.
SSGStatic Site GenerationTavo.js prerenders selected SSR routes during the production build.
ISRIncremental Static RegenerationA runtime caches SSR output and refreshes it after the route's revalidation interval.
Deferred boundaryAn SSR streaming boundary that sends fallback content before optional promise-backed content settles.

State and extension terms

TermMeaning in Tavo.js
ModelReactive state owned by one mounted createTavo component.
ControllerComponent behavior, lifecycle, services, and managed side effects in createTavo.
StoreObservable state container; a global store is for browser state shared by multiple consumers, not request identity.
ResourceComponent-owned asynchronous read state with loading, success, error, reset, and cancellation behavior.
PluginA manifest-backed framework integration with lazy client, server, and build phase implementations.
Server-only moduleA module Tavo.js prevents from entering the client bundle, normally under src/server or marked with the server-only import.

Look up exact public types

Follow linked API names to their canonical TypeScript declarations and package boundaries.