SERVER-RENDERED SITES
Serve dynamic web journeys without rebuilding the product in another framework.
Use the same Fission components for ecommerce, dashboards, portals, and account pages, then choose request-time data, session privacy, cache policy, workers, or focused islands only where the route needs them.
# render every route, then serve locally
fission server check --project-dir my-shop
fission server routes --project-dir my-shop
fission server serve --project-dir my-shop
# build the server binary and browser assets
fission server build --project-dir my-shop
SERVER SHELL
Request-time HTML belongs in the Fission model too.
Server sites combine cached pages, private session pages, signed actions, workers, islands, and deployment packaging around the same Rust components.
REQUEST-TIME ROUTES
Dynamic HTML
Render pages when they need sessions, request data, private state, or cache revalidation instead of forcing every route to be static.
SERVER WORK
Jobs and signed actions
Drain typed server jobs before responding and handle user intent through signed action posts that reducers can validate and retry safely.
FOCUSED BROWSER CODE
Workers and islands
Attach progressive workers or small WASM islands where a page needs browser-side behavior without turning the whole site into one large app.
DYNAMIC WEB MODEL
Choose the route mode based on the data boundary.
Some pages should be static, some should be revalidated, and some must be rendered per request or per session. The server shell exists for that split.
ROUTE MODES
Static, cached, or private
A server site can combine long-lived pages, time-to-live revalidation, request-rendered pages, and session-private pages in one product.
Server guide
USER INTENT
Signed actions, reducers, and jobs
Forms and browser actions post signed payloads back to the server, reducers update state, and jobs/services prepare data before HTML is returned.
Actions and jobs
DEPLOYMENT
Server assets are part of the package
Workers, islands, static assets, server binaries, Docker image metadata, and security settings are generated and checked together.
Package server sites
REQUEST PATH
Model routes, prepare data, render HTML, package assets.
01
Model
Choose which routes are public, revalidated, request-rendered, or session-private.
02
Render
Use Fission widgets for page structure while jobs and services prepare data.
03
Deploy
Package the server as a Docker image with generated assets and security checks.
Dynamic pages without a second app model
Server-rendered routes still use Fission widgets, jobs, services, reducers, generated assets, and deployment packaging instead of a parallel web stack.