# Svelte Stack

## Intent

This stack serves a Svelte frontend beside the product's backend stack. A Svelte frontend takes one of three rendering modes, chosen by who reads it. An authenticated console is a static SvelteKit application. A public surface whose pages are shared as links and read by a search engine renders on the server. A device client that asks one question repeatedly is a static page with no router. The shared stack rules on the [Stacks](https://litespec.dev/2.0.0/core/stacks.md) page apply to every stack.

## Standards

### Select a rendering mode by audience

**Requirement:** A Svelte frontend MUST render as a static application when it is a console, and on the server when a public page is indexed.

**Rationale:** A console is reached from the application a signed-in user already has open. Its first response has nothing to index. A public page is reached from a message or a search result. Its title and links belong in the first response. A device client asks one question over and over. It takes a static page with no router. A page counts as indexed when its readers reach it from a message or a search result.

**Example:** A back-office console and an internal admin console ship as static files. A public storefront runs as a Node server that hydrates in the browser. A warehouse handheld client ships as one static page.

### Build a device client as one static page

**Requirement:** A device client MUST ship as one static page with no router.

**Rationale:** A device client asks one question over and over. A router adds downloads without adding destinations.


## Conventions

This stack adds no conventions.

## Verification

| ID | Mark | Evidence |
|:---|:---|:---|
| litespec/frontend/web/svelte/stack#select-a-rendering-mode-by-audience | guidance | Does each frontend render in the mode its audience requires? |
| litespec/frontend/web/svelte/stack#build-a-device-client-as-one-static-page | guidance | Is each device client one static page with no router? |