community
community copied to clipboard
makerdao
Feature - API Embed
Meetups, grants, translations, and some Contributor Teams Use air table for applications. It would be super snazzy to have embed form.
Beyond just form embed, It would be nice to explore "write to an air table database." ( I think they're called blocks) The example were thinking of for governance communicationsIs to collect emails In an air table for eventual email distribution. We need to keep special consideration for privacy. And we should look at this one next week to decide before implementing anything more advanced than just forms (at least).
Just to clarify, Airtable is not the set platform, but likely. Would be good to know if we have to be platform specific for embeds (Google Forms,Airtable, etc)
@twblack88 I spoke about this with @amy-jung on Friday, but to ensure parts of our conversation have been documented:
I need to know how we plan to use this feature. Would we prefer we build individual components that support the unique features of iframe embed for Airtable, Google Forms, ect. or 1 component to rule them all? (LOTR joke inbound)
ie. We'd have components like <GoogleForm/> and <Airtable/> in MDX with props that can be passed to specific data we'd use to identify individual forms (ie. urls to the embeds for example).
OR
Do we want to have widespread support for iframe embeds? We currently support youtube playlists with the Video component in in this way, but we could expect a component in MDX like <Embed/> where the props you write are what would go directly on the iframe.
There are benefits and detriments to each implementation, but for the sake of doing it once and leaving the more advanced features in your hands I would vote for the latter <Embed/> spec.
As the resident legolas, I would 🗳️ for option 2. Robust embedding would allow us to leverage notion as they release their API in the future, along with a myriad of other services (Airtable, google etc.)
The other consideration is: robust embeds would allow us to tinker on props well into the future. Giving a robust set of data to write, test, break, and fix once the portal launches.
I also vote for Option 2 as widespread support for iframe embeds would be highly desired for many reasons!
Sounds like a plan then team. We can put this in action.
Would it be good to test with Airtable and Google forms as initial test cases for this component?
Revisiting this now that we have the site in the wild. A sitewide supported iframe (full width and whatever height ) is still the best option.
Priority platforms to test: Figma Airtable Google (forms, docs, and/or sheets)
