feat(home): stats section

[dohaki]

Based on #8

Closes ACX-1868

[linear]

ACX-1868 [Landing] Implement stats section

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
across-to	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 13, 2024 9:46am

[james-a-morris]

The Figma design has the hero image at 500px wide. I've tested on Chrome & Safari and noticed that the hero image width is 464px

[james-a-morris]

OOC, does the stats call use SSR?

If the scraper has any issues, what would be the timeout before the user is served data? If there's a timeout, we may want to render this client-side since it's not critical for painting the rest of the page.

[james-a-morris]

Left a comment

[dohaki]

The Figma design has the hero image at 500px wide. I've tested on Chrome & Safari and noticed that the hero image width is 464px

Fixed a18c51b

[dohaki]

OOC, does the stats call use SSR?

The <StatsSection /> component is a Server Component and is rendered on the server, yes. Per default this happens during build time and statically though.

If the scraper has any issues, what would be the timeout before the user is served data? If there's a timeout, we may want to render this client-side since it's not critical for painting the rest of the page.

This use case is the perfect fit for Server Components IMO. There is no need to render the data client-side and create a delay/loading state in the UI. If the request fails during build time, Next.js uses the previously cached value and retries on the next validation cycle.

It was helpful for me to read through these docs in order to understand App Router and Server Components better:

• https://nextjs.org/docs/app/building-your-application/rendering/server-components#static-rendering-default
• https://nextjs.org/docs/app/building-your-application/data-fetching/fetching-caching-and-revalidating#fetching-data-on-the-server-with-fetch

[james-a-morris]

LGTM - I read through the SSR docs +1