You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm experimenting with Next.js and exploring a hybrid approach that combines Static Site Generation (SSG) with Client-Side Rendering (CSR) to optimize performance and user experience. The idea is to have the main transactions listing page—for example, /transactions—statically generated at build time, ensuring fast load times and improved SEO. Then, when a user clicks on a specific transaction, the detailed page (e.g., /transactions/[transactionId]) would be rendered on the client side, allowing for more dynamic behavior without a full page reload.
I'm interested in discussing whether this approach is optimal in practice, any potential pitfalls, and best practices for implementing it in Next.js.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Summary
I'm experimenting with Next.js and exploring a hybrid approach that combines Static Site Generation (SSG) with Client-Side Rendering (CSR) to optimize performance and user experience. The idea is to have the main transactions listing page—for example, /transactions—statically generated at build time, ensuring fast load times and improved SEO. Then, when a user clicks on a specific transaction, the detailed page (e.g., /transactions/[transactionId]) would be rendered on the client side, allowing for more dynamic behavior without a full page reload.
I'm interested in discussing whether this approach is optimal in practice, any potential pitfalls, and best practices for implementing it in Next.js.
Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions