rikka-site

To build a resource-oriented server with content negotiation, model URLs as explicit resource classes like collections and items, then register transformers to automatically serve formats such as HTML, JSON, and CSV from a single endpoint.

Server-side rendering hydration with custom elements works by pairing SSR output with client components and SDK helpers, requiring explicit Repr-based handlers and router integration to serialize and hydrate interactive applications.

Yes, you can deploy a resource-oriented server app across Node and edge runtimes by defining a single resource tree that supports server-side rendering serialization and client-side routing for both environments.

The best way to serve multiple formats like JSON-LD and protobuf from one endpoint is using a resource-oriented server that applies automatic content negotiation, preventing the need to duplicate handlers for each specific format.

Yes, you need explicit Repr-based handlers and kind-based resource classes to serve static assets and proxies, ensuring predictable HTTP behavior across collections, items, actions, and auth-gated routes.

A limitation of using this resource-oriented server is the prerequisite to define explicit transformers and kind-based resource classes, which requires upfront structural planning before serving any data formats or hydrating client components.