We previously referred to this as "server-side rendering" (SSR), but that term is too generic, so we renamed this initiative to "server directive processing" instead.

This Tracking Issue tracks the ongoing efforts to process the Interactivity API directives in the server.

We will hook into the block rendering pipeline using a combination of render_block_data and render_block. We should also start measuring performance as early as possible to make sure that processing directives is as performant as it can be. For the processing itself, we will try to leverage the new HTML API, as it will be the most performant and safe way to do this.

Tasks

These are some of the initial tasks, although we will edit this post once we progress and discover what other things we need to do.

• Make sure we only process the directives once.
  • Server directive processing: Process only root blocks #55739
• Improve the way we save references to the root blocks.
  • Server directive processing: Improve how block references are saved #56107
• Get rid of the md5 + serialize and find a better way to identify blocks.
• Differentiate between interactive and non-interactive blocks.
  • Server directive processing: Stop processing non-interactive blocks #56302
• Integrate the HTML API in the directives processing.