Feature-Requests

Translations: Allow adding locales (combinations of language-country)
Now it is possible to only choose languages. But if you work in a few countries, very often you have different content in different places. For example, links: Even if your email content is the same in English in Germany and English in the UK you might have different landing pages. How we handle it now: – If we have an email for multiple regions we can create a single file for different languages (let's say EN, DE, FR, IT etc.) – But if we need a few different English emails (EN for Germany, EN-DE, EN-FR, EN-IT and maybe EN for the United Kingdom) then we have to create separate emails for all English versions. In the end we get one multilingual file (EN, DE, FR, IT) and five additional files just for English. The perfect way: – If you allow setting regions for each language we will be able to have a single file for any emails: EN-DE, EN-FR, EN-DE, EN-IT, EN-GB, DE, FR, IT – But it doesn't mean that you have to always choose both (the language and the country) You can set just the language if you don't need the country. So the approach can be similar to Google's approach to hreflang tags: You can set either just language or both language and region. And if you selected, for example. FR-BE, FR-CH and FR it means that you have three versions of French email: French for Belgium, French for Switzerland and French for any other country. How it can work in the language choosing interface: – There are always two fields for each item: Language and Country – When you selected a language, country by default is Global (meaning just "en", for example) – You can select each combination only once: If English – Global is already selected and you add one more English then you are not able to choose Global anymore. Only with some additional country.
2
·
planned
Copy and paste properties between elements
Stripo has some limitations when it comes to reusing styles. For example, CSS properties cannot be reliably transferred between emails or preserved when saving elements as modules. A common case is buttons: when a button is saved as a module, its hover styles are not retained. This creates unnecessary manual work and makes it difficult to keep emails visually consistent. Proposed feature: allow users to copy properties from one element and paste them onto another element of the same type. For example, button to button, container to container, or one-column structure to another one-column structure. Proposed workflow: 1) Select an element that is already styled correctly. Its properties are copied and stored locally in the browser, for example as JSON. 2) Open another email, select a compatible element, and paste the properties. 3) All parameters are applied instantly to the new element. This would not be a full element copy. Instead, Stripo would paste values such as text, numbers, and settings into the corresponding fields, similar to manual editing but automated. For example, hover properties would simply be pasted into the target button, and Stripo would generate a new CSS style for that button, just as it does today. This avoids cross-email CSS issues while giving users a fast and reliable way to reuse styling across emails and projects. Also this feature is not just a workaround for this specific CSS problem, it is just a great way to speed up emails editing.
2
·
under review
Load More