The specific api/route to the Airtable data is up in the air (currently using Airtable's js api, but have other options: use Airtable's REST api. read static json, use production server's api (which we can beef up), use GraphQL endpoints, local storage using indexed_db, etc.).
Add a javascript client-side data-access layer API that different pages use to get the data. The point of this API is that as we try different options for routes to the Airtable data, none of the pages that use the data will be impacted.
colindavey
commented
3 years ago
The specific api/route to the Airtable data is up in the air (currently using Airtable's js api, but have other options: use Airtable's REST api. read static json, use production server's api (which we can beef up), use GraphQL endpoints, local storage using indexed_db, etc.).
Add a javascript client-side data-access layer API that different pages use to get the data. The point of this API is that as we try different options for routes to the Airtable data, none of the pages that use the data will be impacted.