Server Side Rendering can give a nice first impression, but it is one of the toughest techs out there.
To this point, I'd actually advocate for going frameworkless and static on a landing page if possible. It's usually not a page with complex state/logic and performance and needling over pixels is what is important.
Server side rendering is actually simple if you strip away modern JS and write HTML.
Static Rendering is probably what you are referring to, server-side rendering implies some munging of data to render the final HTML and send it to the browser.
You are right and I wanted to suggest exactly what you commented. "Keep your landing simple and static (Server Side Rendered)". I was just carried away with my chosen stack and I incorrectly meant "Server Side Rendering your whole ReactJS app" by "Server Side Rendering". I will make a slight correction, thanks for this comment.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
To this point, I'd actually advocate for going frameworkless and static on a landing page if possible. It's usually not a page with complex state/logic and performance and needling over pixels is what is important.
Server side rendering is actually simple if you strip away modern JS and write HTML.
Here is a great article on the tradeoffs:
developers.google.com/web/updates/...
Static Rendering is probably what you are referring to, server-side rendering implies some munging of data to render the final HTML and send it to the browser.
You are right and I wanted to suggest exactly what you commented. "Keep your landing simple and static (Server Side Rendered)". I was just carried away with my chosen stack and I incorrectly meant "Server Side Rendering your whole ReactJS app" by "Server Side Rendering". I will make a slight correction, thanks for this comment.