Add pre-render contents in fragment

[wildfiremedia]

Summary

Pre-render static content for better performance.

Background & Motivation

Pre-rendering HTML fragments in .astro as static content eliminates the need for dynamic rendering.

I often write a large number of input field controls, which can increase CPU usage.

Goals

• Reduce CPU consumption.
• Improve load times by shaving off a few milliseconds, as even a one-millisecond increase can lower throughput, especially on low-end servers and serverless environments.

Example

Let's see on my contact form, currently, without flatten/pre-render 100 Astro components on a page, it will incurred more processing on every request.

 <Input ...>
 <Input ...>
 <Input ...>
<Selector ...>
<Textbox ...>
...
   <Footer>{years} copyright</Footer>

With Fragment component, I think it's a good candidate for rendering once using the is:static directive:

<Fragment is:static>
 <Input ...>
 <Input ...>
 <Input ...>
<Selector ...>
<Textbox ...>
...

   <Footer>{years} copyright</Footer>
</Fragment>

Which will flatten to HTML on the page at the build step, just like a pre-rendered static page, but only for a portion of the content in SSR mode.

This benefits lengthy marketing pages that don’t use static page rendering. If only a small portion of the content is dynamic (Real-time Statistic), developers might still end up using hundreds of Astro components unnecessarily.

[ematipico]

You might are onto something, but I suggest being more clear about "pre-render something" because it isn't clear at all from the proposal.

Plus, Astro already has the concept of pre-render, so you be extra clear about what you're suggesting

[wildfiremedia]

@ematipico I have updated my example.