Indexability

As shown in Reactivity, page logic starts executing in the server at page delivery, for populating it with a valid content, and continues in the client, to support user interaction.

This is important: search engines find the actual content to index, and users find highly dynamic and interactive pages at the same time.

This contrasts with how traditional reactive frameworks were designed to work: they where made to dynamically populate pages in the client, although they now have options to implement what is known as SSR, or server-side rendering, to work in the server too.

Unfortunately these are retrofitted solutions which add to the intrinsic complexity these frameworks already suffer from. As an example, here are some up-to-date instructions for enabling SSR with React.

Although it's a terse post, it still contains a rather long set of instructions, and requires some specific additional code for the server. This is how exactly the same result can be achieved in a Trillo page, without requiring any extra configuration:

<html>
<body>
  <div :count="[[0]]">
    <h1>Hello from Server-Side Rendered Trillo App!</h1>
    <p>Counter: [[count]]</p>
    <button :on-click="[[() => count++]]">Increment</button>
  </div>
</body>
</html>

TBD: data binding, states, routing

PreviousReactivityNextReusability

Last updated