Commit

The next WildflowerJS feature I'd like to discuss is how it handles SSR. We don't use generation/hydration, we use adoption. The html you send is what WF uses to populate state. So you don't have to have an equivalent component on the server side. In fact WF is agnostic to your server backend. As long as you can serve HTML, you can use SSR in WildflowerJS. From the website, here is a diagram of our SSR model and how it compares to other frameworks. No server-side companion. Chunking supported. Data types supported. Here is valid content from a server that will populate state automatically. <div data-component="data-showcase" data-ssr="true"> <div data-bind="username">johndoe</div> <div data-bind="score" data-type="number">1250</div> <div data-bind="verified" data-type="boolean">true</div> <div data-bind="metadata" data-type="json">{"theme":"dark","lang":"en"}</div> <button data-action="showState">Show Current State</button> </div> And to me, the best part about it is that data queries can pick up directly from SSR adopted content. So you can have server-rendered data transition seamlessly to data queries that keep it fresh. I'll discuss that in another post.