Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Incremental Builds in Gatsby Cloud

gatsbyjs.org

Post reply on HN
Print view View original

11–20 of 81 posts

Re: Incremental Builds in Gatsby Cloud

#11

Post by denster »

kylemathews wrote: post #9

Gatsby founder here. Really appreciate the feedback and support for our launch today! The team worked super hard to get Incremental Builds live in public beta but are taking all the feedback (here and all over the web) as we go into full launch. Let us know what you think. Thanks!

Kyle,

Just read the post, congrats on the launch!

We've been using Gatsby on:

https://mintdata.com

for the past few years, and are huge fans of your work.

I still recall the day when I brought Gatsby into our org, our front-end guys almost ate me alive :D

They said: a React.render(...) + GraphQL thing, why do we need it? What's the big deal?

Fast forward a few years later, and Gatsby dominates (in my opinion) the best way to build a static website based on React.

Keep up the awesome work!

Your true fan, Denis

Re: Incremental Builds in Gatsby Cloud

#12

Post by noworriesnate »

kylemathews wrote: post #9

Gatsby founder here. Really appreciate the feedback and support for our launch today! The team worked super hard to get Incremental Builds live in public beta but are taking all the feedback (here and all over the web) as we go into full launch. Let us know what you think. Thanks!

Thanks for the great piece of software! I really like how the Gatsby community is dabbling in templates for more than just blogs. I've seen documentation sites, landing pages, and notes.

Here are some thoughts on my experience with Gatsby:

- You've done a lot of work to make configuring Gatsby easier, but I still seem to constantly hit roadblocks trying to get the config I want. For example I was running into problems getting MermaidJS, embedded video (that I was hosting on my own machine, not on YouTube), and mdx files all working together.

- I've been thinking that Gatsby is the perfect framework for creating semantic web content. E.g., you could have calendar events sprinkled through a website and create a GraphQL API for listing those calendar events, and that API would be accessible during the build process.

Re: Incremental Builds in Gatsby Cloud

#13

Post by lotyrin »

dgb23 wrote: post #5
bmelton wrote: post #4

Earlier quoted context omitted.

The 'backend' here is ... HTML. For read-only a blog, that's likely more than enough. Otherwise, for dynamic content like contact forms and such, I don't know if there's a meaningful benefit to building out a whole site in PHP/Python/Rails or something (and paying commensurately more in hosting) than to use Formspree or something similar. Yes, it calls an API. And thankfully with Formspree, it's pretty easy to see th…

Content has to come from somewhere. Operational complexity is increased, not decreased, since you are running a build server in addition to your CMS. The benefit is easier optimizations in the frontend.

Yeah, but you're only running your build server some of the time (which is favorable in this era of by-the-second pricing) and you're running it inside a private network where nobody can try to infiltrate it 24/7 for no good reason.

Re: Incremental Builds in Gatsby Cloud

#14

Post by skrebbel »

Having never used a static site generator in anger, can someone explain to me like I'm five what's going on here?

My understanding is that Gatsby is a tool that converts a bunch of markdown files into a static HTML website. Why is slow builds a problem for any static site generator? Why does it need a cloud?

In other words, what problem am I supposed to be having that any of this solves?

Note, I'm trying not to be skeptical here - my company's website is hand-maintained HTML with a bunch of PHP mixed in so I can totally imagine that things may be better. But I don't understand the kinds of situations where using a 3rd party cloud to generate some static HTML solves a problem.

Re: Incremental Builds in Gatsby Cloud

#15

Post by denster »

noworriesnate wrote: post #12
kylemathews wrote: post #9

Gatsby founder here. Really appreciate the feedback and support for our launch today! The team worked super hard to get Incremental Builds live in public beta but are taking all the feedback (here and all over the web) as we go into full launch. Let us know what you think. Thanks!

Thanks for the great piece of software! I really like how the Gatsby community is dabbling in templates for more than just blogs. I've seen documentation sites, landing pages, and notes. Here are some thoughts on my experience with Gatsby: - You've done a lot of work to make configuring Gatsby easier, but I still seem to constantly hit roadblocks trying to get the config I want. For example I was running into problem…

Interesting, what were the challenges you faced with MDX?

We built https://mintdata.com/docs on it, and it's been proverbially better than sliced bread -- that is, a true joy to work with MDX.

What're the challenges/pitfalls you faced with MDX + Gatsby?

Re: Incremental Builds in Gatsby Cloud

#16

Post by sandGorgon »

kylemathews wrote: post #9

Gatsby founder here. Really appreciate the feedback and support for our launch today! The team worked super hard to get Incremental Builds live in public beta but are taking all the feedback (here and all over the web) as we go into full launch. Let us know what you think. Thanks!

Hi Kyle, Gatsby was my second static site generator (after Jekyll) and something I have stuck with the longest.

I know you guys are working towards SSR as well, but do you see a particular point of convergence between what you're doing and Nextjs.

Because it seems that given Nextjs SSR, SSG and everything else working now...Gatsby will get to where Nextjs is today.

Re: Incremental Builds in Gatsby Cloud

#17

Post by akiselev »

skrebbel wrote: post #14

Having never used a static site generator in anger, can someone explain to me like I'm five what's going on here? My understanding is that Gatsby is a tool that converts a bunch of markdown files into a static HTML website. Why is slow builds a problem for any static site generator? Why does it need a cloud? In other words, what problem am I supposed to be having that any of this solves? Note, I'm trying not to be sk…

Static site generators output static HTML files instead of running a server that renders every request, it doesn't say anything about what language they consume. Gatsby is built around Javascript and React, not Markdown.

Re: Incremental Builds in Gatsby Cloud

#18

Post by searchableguy »

skrebbel wrote: post #14

Having never used a static site generator in anger, can someone explain to me like I'm five what's going on here? My understanding is that Gatsby is a tool that converts a bunch of markdown files into a static HTML website. Why is slow builds a problem for any static site generator? Why does it need a cloud? In other words, what problem am I supposed to be having that any of this solves? Note, I'm trying not to be sk…

It doesn't have to be markdown files. Gatsby supports a wide range of data sources which is available to use in your templates via graphql. If your website is big and gets frequently updated with data from the backend triggering the builds, new content on the site can take few minutes to appear as the generator will need to build a static site (html/css/js files) which I assume is a problem for big publication sites.

Re: Incremental Builds in Gatsby Cloud

#19

Post by [deleted] »

skrebbel wrote: post #14

Having never used a static site generator in anger, can someone explain to me like I'm five what's going on here? My understanding is that Gatsby is a tool that converts a bunch of markdown files into a static HTML website. Why is slow builds a problem for any static site generator? Why does it need a cloud? In other words, what problem am I supposed to be having that any of this solves? Note, I'm trying not to be sk…

[deleted]

Re: Incremental Builds in Gatsby Cloud

#20

Post by searchableguy »

sandGorgon wrote: post #16
kylemathews wrote: post #9

Gatsby founder here. Really appreciate the feedback and support for our launch today! The team worked super hard to get Incremental Builds live in public beta but are taking all the feedback (here and all over the web) as we go into full launch. Let us know what you think. Thanks!

Hi Kyle, Gatsby was my second static site generator (after Jekyll) and something I have stuck with the longest. I know you guys are working towards SSR as well, but do you see a particular point of convergence between what you're doing and Nextjs. Because it seems that given Nextjs SSR, SSG and everything else working now ...Gatsby will get to where Nextjs is today.

Yeah. Next js already supports static site generation.
Post reply on HN