rendering strategy
Rendering strategy determines when and where initial HTML is produced.
Use this when A route’s initial content, indexing, or authenticated data needs a deliberate rendering choice.
without the term
“Should these pages be rendered on the server, built ahead of time, or done in the browser? Some are public marketing pages and some show the logged-in user's stuff, and I want SEO on the public ones.”
with the term · How do you ask a model for rendering strategy?
Choose a rendering strategy for each route. Verify initial HTML, personalized-data isolation, and navigation rather than assuming every page needs client rendering.
What is rendering strategy?
Server rendering builds HTML per request, static generation builds it at deploy time, and client rendering builds it in the browser. Each route can use a different one depending on freshness, privacy, and interactivity.
Why does rendering strategy matter when vibe coding?
A convenient starter can impose one rendering model on every route.
How do you do rendering strategy?
Classify public and personalized routes by freshness and interaction needs, then inspect their initial response.
What goes wrong with rendering strategy?
Putting private user content into a shared static or cached response.