Currently the site only rebuilds on deploy, so relative "last updated" dates go stale and Airtable data changes aren't reflected until someone manually triggers a deploy.
Solution: Set up two rebuild triggers pointing at a Vercel deploy hook:
- GitHub Actions cron — daily rebuild to keep relative dates fresh
- Airtable automations — one automation per table, triggered on record create/update, calling the deploy hook URL. This way the site rebuilds automatically when content changes.
Setup steps:
- Create a Vercel deploy hook for this project
- Add a GitHub Actions workflow that hits the hook on a daily schedule
- Add Airtable automations for each tracked table (events, map, communities, self-study, jobs, funding, media-channels, advisors, projects, founders)
[written by Claude Code]
Currently the site only rebuilds on deploy, so relative "last updated" dates go stale and Airtable data changes aren't reflected until someone manually triggers a deploy.
Solution: Set up two rebuild triggers pointing at a Vercel deploy hook:
Setup steps:
[written by Claude Code]