Server-side Rendering (SSR)

[exastencil]

Given a set of components, the engine must at the very least be able to render them into an HTML document that the web server can serve.

This is one of the core features needed to make Porous feasible.

This feature integrates with the Page/Component API and the Router to determine which component to render, but in the absence of multiple pages it should also just work without specifying a route. Since a feasible SSR app may still need client-side interaction, but not want full client-side rendering (CSR), there should be a mechanism to facilitate this.

Since a goal of the project is not to mix Ruby and JavaScript, and since params and props are instance variables, it seems logical to send through behavior as text/ruby scripts and have Opal or a WebAssembly-based Ruby handle it. However, it may be tricky to isolate this code, and switching to CSR for interactivity may be the simpler (and thus better) option.