Type to search pages and rules.

Browse pages

Web Rendering and Routes

A route in a TypeScript web frontend carries metadata deciding how links and search meet it. This page states the metadata rule the React Stack and Svelte Stack add to the rendering rules in Frontend Rendering and Routes. A team that applies it while writing routes keeps every public route linkable and every private route out of search.

Markdown1 rule

Stack: any

Layer: frontend-ui

Concepts#

Rules Kept on the Base Page#

The rendering rules for loaders, suspense reads, search schemas, chunk splits, intent preloading, authenticated caching, proxies, the server cache, and shells live on Frontend Rendering and Routes. The web stacks add only the metadata rule this page states.

  • Loader prefetch: litespec/frontend/rendering#load-route-data-before-rendering
  • Suspense read: litespec/frontend/rendering#read-route-data-from-the-route-cache
  • Search schema: litespec/frontend/rendering#keep-address-parameters-validated-by-a-schema
  • Chunk split: litespec/frontend/rendering#load-each-route-and-each-language-separately
  • Intent preload: litespec/frontend/rendering#prefetch-a-route-on-intent
  • Authenticated caching: litespec/frontend/rendering#keep-authenticated-caching-explicit
  • Proxy behavior: litespec/frontend/rendering#keep-proxy-behavior-at-the-edge
  • Server cache: litespec/frontend/rendering#build-the-server-data-cache-per-request
  • Shell layout: litespec/frontend/rendering#use-a-shared-layout-for-a-shell

Standards#

Define Route Metadata Deliberately#

ruleruleguidance
litespec/frontend/web/rendering#define-route-metadata-deliberately
Statement

A public route MUST define its title, its description, its canonical address, and its indexing policy, while a private route refuses indexing.

Applies toartifact: route

Why

A public route's title, description, canonical address, and indexing policy are what a search result and a shared link show; without them the page arrives as a bare address. A private route refuses indexing, because an indexed console address exposes to search what a signed-in user believes is private.

Example

A channel route states og:* tags and one alternate per language. A console route ships a noindex meta tag in its document.

Checka reviewer answers

Reviewed forWhich public routes miss a title, description, canonical address, or indexing policy, and which private routes miss a noindex marker? Look in the route metadata.

Marked guidance: a reviewer answers this question.

Conventions#

None.