As someone who is also building a React-based SSG, what do you believe makes sitegen's design superior to other React SSG's?

  Location: SF
  Remote: Yes/Preferably (6+ years of remote experience)
  Willing to relocate: No
  Technologies: JS(Babel), React, Haskell, Docker
  Résumé/CV: christopherbiscardi.com/resume.pdf
  Email: chris@christopherbiscardi.com

Current Interesting projects:

- Static Site Generator based on Relay/GraphQL and Webpack.

  * https://github.com/superawesomelabs/leo

- A Modern Component library system built on PostCSS and Babel (Not OSS yet)

- Content about creating a product with microservices(Docker), Haskell's Servant and Relay/GraphQL

React Router has been iterating towards better APIs for advanced use cases (server-side rendering, code splitting, relay (and other lib) integration, etc). Having used it in projects spanning the above use cases, the evolution of the API has been welcome change.

I'm also happy to see codemods and other AST manipulations (such as babel plugins) gaining popularity. Similar to eslint's --fix, codemods are making repetitive changes easier across large codebases.

I've been using lost for a few months now. Even if you don't use it it's worth taking a look. (built with PostCSS)

We use it at $work in an "isomorphic" context along with react-router[0] and fluxible[1]. I'm very happy with it and the ecosystem developing around it. Using React also provides an interesting lead-in to native apps with react-native.

We transpile all of our JS with babel as well. I'd be happy to answer any more specific questions as well.

[0]: https://github.com/rackt/react-router [1]: https://github.com/yahoo/fluxible

For Haskell, Hayoo[0] works well

[0]: http://hayoo.fh-wedel.de/?query=.%3A

The link for OSX points to `new-www`.haskell.org. I'm sure the old site still links to haskell platform.

After looking into this I've come to the conclusion that rewriting the JavaScript to handle events through React's system is the best way to include Foundation's JS components. (This is something I'm planning to do with Foundation-for-Apps since I won't be using Angular).

That said, the styles are still usable without modification and you could tell React to not handle pieces of the DOM in some cases for the existing JS.

You could use this list to discover [other keyword] if you are unfamiliar with the landscape. (For example, Isomorphic applications)

I find it no more complicated than things such as figuring out things like clearfixes were in the beginning.