Eleventy: Headless CMS with 11ty - question on build time

[bosslee]

Hi there

New to headless cms so have a few questions that I like to learn from fellow developers

1. taking eg from the ghost headless with 11ty, let say the ghost blog that i like to pull in has 10 posts
   using the ghost content api and using the js data file, we use node fetch to pull into 11ty during build time. In this initial pull, there will be 10posts.

May I ask:
1/ If I write out a new post and it triggers a rebuild
does it build for the new post or does the rebuild include all from the initial post
which is 11 posts all together? Suppose my content api pulls in all the blog posts

2/ What if I only the new blog post?
ie to say, instead of pulling 11 posts, I pull only the new post
assuming I use a counter value to check
and if I trigger a rebuild with this, will the site still have all the posts
or it will only show the new posts?

3/ does all ssg generator works this way? eg Gatsby?

Thank you very much

[Bagera]

1: All posts will be rebuilt
2: You will only have the latest post
3: Yes, but no. Most or all work like this but services are being developed to take care of this. I know Gatsby is working on this bur that is a premium service that is part of their paid hosting, if I have understood it correctly. 11ty is so much faster at building than Gatsby so the problem is not as big in 11ty.

In my experience with gatsby and 11ty, gatsby gives you more magic for "free" but that magic is very expensive at compile time. In 11ty I don't think you will run into problems with a couple of hundred pages.

[zachleat]

This is an automated message to let you know that a helpful response was posted to your issue and for the health of the repository issue tracker the issue will be closed. This is to help alleviate issues hanging open waiting for a response from the original poster.

If the response works to solve your problem—great! But if you’re still having problems, do not let the issue’s closing deter you if you have additional questions! Post another comment and I will reopen the issue. Thanks!