Consider refactoring dynamic EOIs to make them more useful

[mischacolley]

Thinking we could add fields to the Template EOI for:

• Banner Image (Attachment)
• Page / Banner Title (Text)
• Customise submit button text (Text)

BUT Should we?

• We need to have a discussion about when we:
• • Use an Airtable form like this // We used this because it had to go out fast, dynamic EOIs were to limited and Jarod didn't have the experience with Typeform
• • Use a typeform
• • use a custom form / dynamic EOI
• Dynamic EOIs also need new design
• Can we include more field types mapped to blueprint fields?

[camposcristian]

We've already discussed this for v4 on this issue and I think it didn't change much.

Thinking we could add fields to the Template EOI for:
Banner Image (Attachment)
Page / Banner Title (Text)
Customise submit button text (Text)

@mischacolley this was also my question the other day... How would this live in the same Airtable base to make it practical? Can't we just have a default design to quickly capture EOIs from the website (Like CEO4Good), and then if something custom is needed either goes straight to Typeform or a custom made campaign?

Then when something custom is needed, overall, I think we're spending a bit too much time on designing+shipping campaigns and forms, where the final purpose is to capture emails. We've been doing a similar thing for the past 2+ years with not much change. If we can just agree on some structure, I think this could take hours instead of weeks. But that level of customization I don't see it happening on the Dynamic EOI. Instead, this could be part of a nice Blueprint+Campaign in a Contentful structure.

[mischacolley]

@camposcristianeze agree with a lot of what you've said here. I'm going to add it to the agenda of up coming website planing work. Specifically the stuff around campaigns.