Feature-Requests

Create a Stripo connector for Claude such that Claude can create emails and templates within Stripo that can be edited on the design canvas by a human.

Our emails are product heavy so we tend to have rows of 4 products. We want to reduce the scroll as much as possible for mobile which is why the option to stack 2 x 2 on mobile would be ideal. We have found a template that does this, but it requires some coding to tweak colours and spacing so having as part of the fantastic Stripo editor would be awesome. Have attached screenshot examples

To be able to have one section with multiple rows of different numbers of columns - allowing for unified styling of a section with diverse content.

Add possibility to add a gradient background with fixes and fallbacks for various email-clients. Gradients are widely used in email design You always see some nice and clean emails with gradients sent by different brands. But it indeed requires a lot of fallbacks for Outlook, Yahoo, AOL, for example. Would be nice if you could add a gradient tab for background colors like in this guide, for example: https://www.litmus.com/blog/background-colors-html-email (or based on some fresher information). This gradient background tab could contain these fields: 1) RGBA CSS gradient 2) Two fallback colors for Outlook with VML gradients 3) Image gradient (a fallback for Outlook, Yahoo and AOL) 4) A solid fallback color for all other email clients 5) A partial fix for Gmail's dark mode: add a linear gradient to the background image CSS property using HEX colors 6) A further fix: Prevent text colors from being inverted in Gmail: https://www.hteumeuleu.com/2021/fixing-gmail-dark-mode-css-blend-modes/

It would be helpful to add a feature that allows users to switch logos automatically between dark mode and light mode. Many brands don’t have a mid-tone logo that works well on both backgrounds. I’ve tried handling this using HTML-based logo switching, but it’s not a reliable solution. It often causes inconsistencies or errors across different platforms such as Apple Mail and Outlook. A better solution would be to allow users to upload two separate logo versions: One logo optimized for light mode (e.g., black text/logo) One logo optimized for dark mode (e.g., white text/logo) The system could then automatically switch between these logos based on the user’s theme preference. This would ensure better brand visibility, consistency across platforms, and a smoother experience for everyone.

Currently, merge tags are embedded directly inside the exported HTML content. For our email processing and analytics pipeline, we need to scan the entire HTML to identify merge tags before sending emails, which adds extra processing overhead and complexity. Requested Enhancement: Provide an option to export all merge tags separately along with the HTML export. Example Response: { "html": "<html>...{{first_name}}...{{company_name}}...</html>", "mergeTags": [ "{{first_name}}", "{{company_name}}", "{{unsubscribe_link}}" ] } Or, if possible, provide detailed metadata: { "html": "<html>...</html>", "mergeTags": [ { "tag": "{{first_name}}", "name": "first_name" }, { "tag": "{{company_name}}", "name": "company_name" } ] } Why this is needed Eliminates the need to scan and parse the entire HTML for merge tags. Improves performance for analytics and email processing pipelines. Makes merge tag validation and replacement easier. Enables pre-processing and analytics before sending emails. Reduces implementation complexity and potential parsing errors. Use Case Our platform exports email templates from Stripo and processes them further for analytics and email delivery. Having merge tags available separately would significantly simplify our pipeline and improve performance.

The current way of adding borders (changing styles) today does not make sense if we want to apply it to the 4 sides. We have to do it cell by cell and it's impossible to predict the output.

Now you can't save a few structures as a module. The only way is to place them into a separate stripe. But you don't want to have excessive number of stripes on your page not to make your email weight more. Quite often there are cases when different structures belong to each other. For example, when I want to imitate a forum post with an avatar + author name (structure 1 with 2 columns), post text (structure 2 with 1 column) and a section below it with date, number of comments with icon, and reply button with icon (5 columns). In this case it would be convenient to be able to select all three structures and save them as one module. Plus possibility of moving/copying/deleting for multiple structures would be very convenient (I probably forgot about some other manipulations). As an additional idea: When you select objects you always see their controls in the right/left menu. But for such a group of objects this menu will be empty (unless you decide to add some common properties there like paddings or background colors etc.). But even if you keep some common structure properties (which is very useful as well) there should be more free space. You can add some commands to this menu like "Group/Ungroup" for example, so that you can just select them together with one click next time.

Would be really great if you could implement dark mode styles to make it possible to control how the email look in different email clients with dark mode. Of course, email clients behave differently as always but now there are already enough possibilities to give control to some elements. For example: – Override dark mode background colors – Show-hide images for dark mode – etc. – It is even available for AMP emails ( https://dev.to/bdjang/exploring-dark-mode-in-amp-email-5gm7 ) I'm pretty sure your team has already explored this topic. Maybe you have some plans for that (or have reasons to to implement it for now)?

I would like to request the addition of a User Production Dashboard. This dashboard should provide visibility into email creation activity at the individual user level, allowing administrators to track the number of emails created by each user over a selected date range. It should also include a exportable reporting for operational analysis and productivity tracking This feature would provide valuable insight into workload distribution, team utilization, and production trends, helping us better manage email development resources and reporting.