Hi Justin,
When you’re building a custom feature like this, there are a lot of factors like the source data you’re working with, the end goal, and the conditions it will be running in ( e.g. how many visitors per day to the site? how often is the data updated? does the content need to be SEO-accessible, etc. )
I always aim for the simplest approach that will fit the requirement, to keep development time and systems costs controlled.
From your screenshot, I think the end goal here is just display. I’ll assume for now the data is in the format you see it above- one row per item, 3 columns of content grouped by Airport, filtered by # nights.
If traffic is relatively low, you could write JS that hits the Sheet directly, queries the data you need, formats it, and presents it. That alone is a fairly complex setup but it requires no middle tier. Google sheets has a URL-based query syntax which returns JSON.
More robust control over the display could mean building a Google doc which handles the query and layout of your data, essentially an initial presentation, and then you can pull that google doc content directly into your site. Google docs have clean tables and are very useful for this.
More robust needs for performance and higher traffic demands, you can drop a reverse proxy in-between to cache this. This is actually a strategy I use on a number of client sites, where they need the quick free-form access a Google doc provides them, but I need to capture that, style it, and display it on their site.
That path is good for certain types of content, and avoids the CMS.
Another path is the CMS, but you’d need an automation process that detects changes to the sheet and uses the Google API to retrieve it, query it, and build a result. That result could be delivered into the CMS as richtext.
If you’re non-technical and looking for the least-technical path, you could probably ask them to switch from Google Sheets to Airtable ( if the content works there ). Then use Whalesync to pull that data into the CMS, and build your views from the CMS. That comes with a steep monthly cost and some process changes for their team, but it pushes your data-access issues to a 3rd party service, and your formatting issues into the Webflow designer where you can deal with them more effectively.