# Getting started with Gatsby? **URL:** \ **Category:** Installation\ **Created:** [January 10, 2019, 2:02pm UTC](https://forum.ghost.org/t/getting-started-with-gatsby/4948 "2019-01-10T14:02:09Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![vikaspotluri123](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/vikaspotluri123/32/24_2.png) [@vikaspotluri123](https://forum.ghost.org/u/vikaspotluri123)\ **Post date:** [January 11, 2019, 4:32am UTC](https://forum.ghost.org/t/getting-started-with-gatsby/4948/4 "2019-01-11T04:32:05Z")
The Ghost Docs use Ghost(Pro) as a content source. This forum topic might give you a bit of background as to how a Gatsby+Ghost integration works: > [@Gatsby without Netlify](https://forum.ghost.org/t/gatsby-without-netlify/4936/2): > > Netlify is a large proponent of JAMstack and has done a lot of work towards pushing it forward. It’s just a service that makes static site deployment simple and easy. The downside for not using Netlify is you have to add some logic to handle the stuff Netlify abstracts from you. With a basic usecase, you might have your frontend source managed with git, via a service like Github, and your content managed through Ghost. Every time you make a change to your production Github branch (as an example… the tl;dr is your Ghost publication will be set in private mode, and you will use the content API to pull posts from your publication and build your static site. That static site will be hosted somewhere like Netlify --- _[View the full topic](https://forum.ghost.org/t/getting-started-with-gatsby/4948)._