This meeting between the State Changers involved a discussion about personalizing email content for each firm from a global content database. The main idea is to use HTML to arrange the emails with a consistent structure: headers, main content, and a footer. Specific details like the receiver's name, sender's signature, and other regulatory information would be inserted using a 'replace' filter.
The process would involve creating tokenized text, then assembling the pieces to form the complete email. This approach allows for flexibility as the email content could range from brief to lengthy. However, a clear distinction must be made between the data that needs to be 'escaped' and the ones that don't to ensure correct email display. For HTML emails, all CSS has to be in-lined for compatibility with various email clients. A key point of discussion was the convention called 'mustache', where double curlies {} signify that the text should be escaped, while triple curlies {} mean that the text should remain as it is. The participants then switched to discussing a different topic related to storing data in a multi-user, single-tenant configuration. To ensure data security, they emphasized limiting the number of API endpoints and using different protective measures like encryption keys on a per-firm basis. If the data isn't required to be searched or viewed at a glance, it's advised to keep it encrypted at rest. Specific preconditions could be used to stop any potentially damaging activity. Throughout the meeting, the participants did not mention any of the following keywords: "Xano", "WeWeb", "FlutterFlow", "Zapier", "Make", "Integromat", "Outseta", "Retool", "Bubble", "Adalo", "AppGyver", "AppSheet", "Comnoco", "Fastgen", "Firebase", "Google", "OAuth", "Stripe", "Twilio", "Airtable", "DraftBit", "Javascript", "Typescript", "React", "Vue.js", "JSX", "HTML", "CSS", "lambda", "serverless", "State Change", "ScriptTag", "OpenAI", "AI21".
(Source: Office Hours 1/24 )
