In D14105#315068, @bytesofman wrote:

Why do we want to fetch every single blog post?

Seems like paginated return would be useful to load only enough blog posts for the current page.

As the blog grows, quickly impractical to have an API loading hundreds of posts on page load when the user can only read one at a time.

So I was thinking ahead of myself for all of the individual paths and pages we need to resolve. Basically any old post slug needs to resolve if navigated to directly...but we wont have that data if only the first 25 posts have been fetched...
But I agree eventually it would be unwieldy, to be fair not for several years at least ha (also curious how webflow does it as they list every post on the blog page with no lazy loading afaict)
Also keep in mind this will only run at build time so users wont be waiting on this data
But anyway thats a separate diff anyway and there are others ways to do it where for the individual post pages the data is fetched by slug and rendered at request.
I think in general theres more than one way to do it obviously, so need to consider what we want to optimize. Speed and SEO will be on our side if fetch them all, but may eventually become too large (although 100per page will limit to only like another page request every two years assuming same rate of blogs)

Also keep in mind this will only run at build time so users wont be waiting on this data

oh ok, then this approach makes sense.

Seems like we don't get a lot of value hosting all the blog posts on a separate server if we still need to rebuild and redeploy the app every time we publish a new blog post.

Why are we getting all of the blog posts at build time and not just loading / rendering the blog page dynamically based on what the server is providing?

So the main value of hosting somewhere else is so the blog authors have a user friendly CMS to make the posts

As for the build time fetching the main benefits are

• Much faster load times
• SEO performance (static prebuilt pages are indexable)

We do have to build the site for every new post, but those aren't super frequent (like 2 a month?) And there are ways to automate it with strapi webhooks

Overall I'm going this route as its recommended specifically for this use case, and will produce a fast site https://nextjs.org/docs/pages/building-your-application/rendering/static-site-generation#when-should-i-use-static-generation

Easy to switch to serverside props instead if there are reason we dont want to do it this way