4 ms·
Hi HN! John from Ghost here - happy to answer any questions about this. We rebuilt our docs using Gatsby and the Ghost API last year and ended up liking it so m
by johnonolan 8y ago
Hi HN! John from Ghost here - happy to answer any questions about this. We rebuilt our docs using Gatsby and the Ghost API last year and ended up liking it so much that we rearchitected everything to make the the JAMstack workflow a first class citizen :)
- cityzen 8y agoHi John! Congrats on everything with Ghost. Is it possible to run Ghost locally and push a build out which is then deployed to S3, essentially removing the "hosting" aspect of things outside of S3? Do you have any resources you can point to that explains like I'm 5 where Ghost ends and Gatsby starts? Most of my dev life lately has been CraftCMS and Laravel but I'm convinced that some variety of serverless is where everything is headed. Thanks in advance!
- johnonolan 8y agoSure thing! I Gatsby generates static HTML files from 1 or more data sources, which can be a filesystem or an API. When a Gatsby build runs, as long as it can access the API in question, then it can pull the content needed to generate a build. Once that build is completed, the resulting directory can essentially just be dragged and dropped (literally, in the case of Netlify) onto a hosting platform. You can absolutely run all of these things locally and have no code running in production at all, if that's what you want to do! The benefit of having your content API in production is that it can be accessed from anywhere, by anything - which opens up a lot more usecases. Best way to get a handle on it all is to play with the starter repo, which should be fairly easy to get up and running: https://github.com/tryghost/gatsby-starter-ghost https://github.com/tryghost/gatsby-starter-ghost
- cityzen 8y agoAwesome! Thanks for the info! Excited to try this out.