Do you ever build static HTML concurrently with a React app?
A lot of the times React is taught in a way where you make your entire page as a stand-alone from everything but the App “root” in the HTML. But are there times you would want to use mostly static content, and an actual React app somewhere as a small piece of that static content? Maybe for SEO, in the similar reason in how landing pages are separate from React apps?
Posted May 24, 2019, 7:04 AM UTC
I'd never build websites without Gatsby anymore. It comes with the latest tech stack and best practices for the JAMStack out-of-the-box and is mainly focused to create highly performant static (SSR) websites based on React while allowing to use dynamic content or even make some paths client-only (PWA/App).
Oh wow, that sounds exactly like the solution to my React quips. That is going first on my list of front end techs to learn.
Nice to hear I could convince you 😄 You won't be disappointed, Gatsby is the state-of-the-art for the JAMStack. There are ten thousands of sites already using Gatsby, from small personal pages up to commercial shops. Even the official React website and documentations are build with Gatsby as well as the blog of the React core team member Dan Abramov. If you've installed the official React DevTools Browser Extension you can easily see which websites using React and when opening up your DevTools you'll be surprised how many page's root element have the
idattribute__gatsby😉Yep I'm using it for our main site at work right now. All the optimization is amazing. Even my CEO is like "this is awesome!"