🐛 Bug: Homepage crashes when calendar fetch fails

Describe the bug

The homepage crashes when the external Google Calendar fetch fails.

When the calendar request fails (e.g., due to network/DNS issues), the datesInfo value becomes undefined. This causes:

• A serialization error in getStaticProps
• A runtime error when the UI attempts to call .map() on null/undefined

This results in the homepage failing to load.

Steps To Reproduce

1. Clone and run the project locally
2. Run yarn dev
3. Simulate failure of the external calendar API (e.g., disconnect internet or block access to calendar.google.com)
4. This issue occurs when the external calendar API is unavailable (e.g., DNS failure, firewall blocking, or network issues).
5. Open http://localhost:3000
6. Observe that the homepage crashes

Expected Behavior

The website should load successfully even if the calendar fetch fails.

The application should gracefully handle the failure and fallback to a safe value (e.g., null or empty list) instead of crashing.

Screenshots

Homepage error showing "Error serializing .datesInfo" and map crash

Device Information [optional]

- OS:
- Browser:
- version:

Are you working on this issue?

Yes

Do you think this work might require an [Architectural Decision Record (ADR)]? (significant or noteworthy)

No

Start at the homepage's getStaticProps and trace how the external Google Calendar response becomes datesInfo, then reproduce the failure with yarn dev while blocking calendar.google.com. Confirm that the homepage loads when the fetch fails, serialization succeeds, and the UI does not call map on an undefined value.