React-Static

A progressive static-site framework for React!

#3 Product of the DayOctober 07, 2017

React-Static is a next-gen static site generator for React. Finally, you can build a website like you do any other React App. There's no special CMS, query language, or crazy lifecycle hooks. Just good old React producing an amazing SEO-ready, user experience driven, progressively enhanced website. The effort is minimal, but the benefits are not!

Discussion
Would you recommend this product?
8 Reviews4.4/5
Good job! How does it compare to Gatsby?
@m_lukaszczyk their medium article compares it to Gatsby (and others): https://medium.com/@tannerlinsle...
@embed_api Gatsby is also based on React.
@m_lukaszczyk sorry then I ihaven't used gatsby much that's is why...

It has some interesting approaches to static site generation that morphs into a React site.

Pros:

Interesting features worth checking out

Cons:

Some more examples would be good

Hey makers, great job, what is the key differences of this static generator with phenomic, gatsby or similar other projects?
@buraktokak Good question. As was mentioned, the linked Medium article (https://medium.com/@tannerlinsle...) goes into more detail. In short, you can spin up Create React App and be running, without having to conform to Gatsby design decisions. That's not to say that their opinions are bad/wrong, as forcing your data into a Gatsby store allows for them to do some magic on your behalf, but I'd rather write my app closer to pure React. The end result of Gatsby and React Static is similar. They both generate static html and both mount React after the first page load, allowing for a SPA-like experience. They both load just small data packages (js bundles for Gatsby, json data for React Static) on subsequent page loads, so they'll both have similar performance.

coooll app

Pros:

great app

Cons:

none

Would I need to build the web app every time the content is changed in WordPress? If so, this tool would be butter suited for websites with fairly static content which rarely changes.
@icyflame The whole build process only takes a minute or two and will run on a CI server, so that shouldn't be much of a concern. Even if you had a site with tens of thousands of pages, it still wouldn't take that long to deploy, and you could even set it up to only rebuild the parts that had changed. WordPress is essentially doing a page build on every single request, so once you've had a few dozen/hundred pageviews, you've already done more work than an entire new build.