Gatsby

Gatsby

Application and Data / Application Utilities / Static Site Generators

Decision about GitHub, Gatsby, Netlify, styled-components, Redux.js, React, Firebase, Google, Frontend, ReactRally

Avatar of johnnyxbell
Sr. Software Engineer at StackShare

I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

31 upvotes7 comments43.2K views

Decision at Algolia about React, Gatsby, Ruby, Middleman

Avatar of ronanlevesque
Software engineer at Algolia

A few months ago we decided to move our whole static website (www.algolia.com) to a new stack. At the time we were using a website generator called Middleman, written in Ruby. As a team of only front-end developers we didn't feel very comfortable with the language itself, and the time it took to build was not satisfying. We decided to move to Gatsby to take advantage of its use of React , as well as its incredibly high performances in terms of build and page rendering.

13 upvotes2 comments58.7K views

Decision at Uploadcare about Netlify, Gatsby, React, Node.js, Django, StaticWebHosting, StaticSiteGenerators, Frontend

Avatar of Zmoki
Frontend Team Lead at Uploadcare
NetlifyNetlifyGatsbyGatsbyReactReactNode.jsNode.jsDjangoDjango
#StaticWebHosting
#StaticSiteGenerators
#Frontend

Since 2011 our frontend was in Django monolith. However, in 2016 we decide to separate #Frontend from Django for independent development and created the custom isomorphic app based on Node.js and React. Now we realized that not need all abilities of the server, and it is sufficient to generate a static site. Gatsby is suitable for our purposes. We can generate HTML from markdown and React views very simply. So, we are updating our frontend to Gatsby now, and maybe we will use Netlify for deployment soon. This will speed up the delivery of new features to production.

#StaticSiteGenerators #StaticWebHosting

7 upvotes27.8K views

Decision at TrackJS about Gatsby, Read the Docs, ReadMe.io, GitHub Pages, Jekyll

Avatar of toddhgardner
President at TrackJS

We recently needed to rebuild our documentation site, currently built using Jekyll hosted on GitHub Pages. We wanted to update the content and refresh the style to make it easier to find answers.

We considered hosted services that could accept our markdown content, like ReadMe.io and Read the Docs, however both seemed expensive for essentially hosting the same platform we already had for free.

I also looked at the Gatsby Static Site generator to modernize Jekyll. I don't think this is a fit, as our documentation is relatively simple and relies heavily on Markdown. Jekyll excels at Markdown, while Gatsby seemed to struggle with it.

We chose to stick with the current platform and just refresh our template and style with some add-on JavaScript.

4 upvotes11K views

Decision about Gatsby

Avatar of andyWynyard

I use Gatsby because it is the quickest way to mock out a project. For websites its the best thing out there. The failings of Gatsby are in web applications that have a great many items being moved in and out of the application all the time.

2 upvotes1.1K views

Decision about Netlify, Gatsby

Avatar of cycorax12

Hello people,

Need help, i want to start full fledged blog. Planning to use Gatsby with Netlify.

Following are question which i need answer to: 1. Gatsby good option then other cms in term of seo, revenue via ads etc ? 2. What datasource to use to show post: Markdown ? Or DB via GraphQL 3. Long term with Gatsby is good ? In term of scaling ?

Thanks

1 upvote1.4K views

Decision about Gatsby

Avatar of katnoria

I use Gatsby because:

When starting out to build my website, I had clear requirements:

  • Should be able to write posts only in markdown.
  • Should be able to create interactive posts with widgets and D3/Vega visualisation.
  • Should be able to pull data from backend web-services.
  • Easy to manage and deploy

Gatsby ticked most except that it had higher learning curve especially when I wanted to add custom React components inside markdown (i.e Vega plots) or handle both Markdown and Javascript posts. It takes time if you want to do more than what is covered in their tutorials but I feel its worth it.

And, with MDX plugin that I am yet to try I see things getting even more cooler (i.e mixing JSX and Markdown).

1 upvote140 views

Decision at CommentBox.io about Gatsby

Avatar of shaunpersad
Maker at CommentBox.io

We use Gatsby.js to render our website server-side for SEO purposes, and blazing fast load times. It also hydrates into a react app, so having dynamic functionality is a breeze. Gatsby

1 upvote25 views