Hi, there, Dmytro here.
This month, we focused on accessibility, clearer governance for large teams, cleaner export logic, and practical editor improvements that make everyday work more predictable.
1. New: Accessibility checker
Accessibility testing is now a fully developed workflow inside Stripo.
You can test emails and templates against common vision impairment profiles:
- protanopia;
- deuteranopia;
- tritanopia;
- achromatopsia.
This allows you to see how color choices and contrast behave for people with different types of color blindness and to identify design issues before sending.
We also added filtering for dark mode screenshots inside the testing results. This makes it easier to review how accessibility and dark mode interact in the same campaign.
It is important to note that Stripo’s email code has already been optimized for screen readers. With the accessibility checker now available, teams can build emails that meet modern accessibility requirements directly inside the editor.
Accessibility testing with Stripo is a structured checking process that helps you review how your email performs across different accessibility scenarios before it reaches recipients.
2. New: Text blocks now support Grammarly and browser extensions
We also improved how text blocks interact with browser extensions.
You can now use Grammarly and other browser-based writing tools directly inside the text block. Previously, these extensions had not worked correctly within the editor.
This change improves editing quality and helps teams maintain accessible readable content without leaving Stripo.
3. Improved: Security and account governance
Mandatory 2FA enforcement for invited users
Account administrators now have stricter control over two-factor authentication.
If 2FA is required for a company, invited users who disable 2FA will no longer be able to access company projects. This ensures that security policies are applied consistently across the entire team, including external collaborators.
This update strengthens governance and helps organizations enforce their internal security standards without manual monitoring.
Updated account deletion policy
We have revised the account deletion policy to improve account lifecycle management.
The update clarifies what happens when an account is scheduled for deletion, including retention periods and access restrictions during that stage. This helps organizations better understand how their data are handled and align internal compliance processes with Stripo’s account management rules.
The goal of this update is transparency and predictability, not changing how teams work on a daily basis.
4. Improved: Workspace and team structure
Multi-share templates across company projects
Templates can now be shared multiple times across projects within the same company.
This is particularly useful for enterprises and agencies that operate multiple projects for different markets, brands, or departments. Teams can reuse approved templates across environments without duplicating and manually transferring them.
Module permission is independent from project permission
We separated module permissions from project permissions.
Now, editing modules require only the “Modules” permission. Access to projects is no longer required for managing modules.
This allows for more precise role configuration and cleaner responsibility separation, especially in larger teams where content libraries are maintained by a dedicated group.
Folder limit per project
We introduced a limit of 2,000 folders per project.
For large accounts with complex structures, this helps maintain predictable organization and supports long-term workspace planning without uncontrolled folder growth.
5. Improved: Navigation and recent usage view
Recent usage view
We introduced a new way to view emails and templates based on recent activity.
In the recent usage view, items are displayed by their last edited date, regardless of the folder in which they are stored. Instead of navigating through nested folders, you can quickly see what was most recently worked on.
This is particularly helpful in projects with many folders and distributed campaign structures. When teams operate across multiple regions or workflows, it can be difficult to track which email was updated last. The recent usage view simplifies this process by temporarily stepping outside the folder hierarchy and focusing on activity.
6. Improved: Tracking, exports, and workspace configuration
UTM improvements
We improved how UTM parameters are added to the links.
Stripo now applies UTM tags more accurately to specific link types, reducing the risk of duplicated or incorrectly structured tracking parameters. This helps keep analytics data cleaner and more predictable across campaigns.
In addition, UTM tags can now be added during email generation via the Stripo API, giving teams more control when creating emails programmatically.
“Anchor at the end of URL” control
A new control has been added to the Workspace configuration.
The “Anchor at the end of URL” option moves the anchor to the end of the link during export. This helps maintain a consistent link structure and avoids formatting conflicts when emails are transferred to ESPs or other systems.
For teams that rely on precise link handling and tracking, this adds another layer of control at the workspace level.
Re-export support for Mailjet
Re-export is now supported for Mailjet.
This allows teams to update and resend emails without rebuilding export connections, simplifying iteration cycles for campaigns managed in Mailjet.
7. Improved: Editor workflow
Text block improvements
We refined several aspects of the Text block to make editing more predictable:
- when pasting multi-paragraph content, styles are now applied correctly to each paragraph;
- Justify alignment is available;
- unused custom CSS is removed from the text block to keep the markup cleaner.
Together, these changes improve text formatting consistency and make content editing more reliable.
Disable default CSS for custom markup
Advanced users working with custom HTML now have more control.
A new option allows you to disable Stripo’s default styles when inserting a custom markup. This prevents automatic editor styles from affecting custom layouts and reduces the risk of unexpected visual changes.
This is particularly useful for teams that build complex or highly customized email structures.
AMP generation logic for the Carousel block
We updated how AMP elements are generated.
If the Carousel block is set to HTML mode and there are no other AMP blocks in the email, Stripo will no longer automatically generate an AMP version.
This results in cleaner output and avoids unnecessary AMP codes in emails that do not require them.
8. Coming soon
We are continuing to refine core workflows and prepare several visible improvements for the next releases.
Updated Modules panel design
The Modules panel inside the editor will receive an updated design.
This will simplify navigation across saved modules and make it easier to work with large libraries directly inside the editor.
Keep module styles
We are working on a “Keep Module Styles” update.
When saving and reusing a module, its original style will be preserved instead of adapting to the style of the email where it is inserted. This will help maintain visual consistency when modules are reused across different campaigns.
Code editor UX update
The extra “Save” button in the code editor will be removed.
This change will make the editing process more straightforward and reduce confusion during code updates.
Clearer highlighting of synchronized modules
We are improving how synchronized modules are displayed inside emails.
They will be visually highlighted more clearly, making it easier to identify them and manage synchronization workflows without guesswork.
AI widget launch
We are preparing to launch AI widgets.
This will introduce a new layer of intelligent components inside the editor and mark the next step in how teams build and optimize email content in Stripo.
Wrapping up
This month’s updates focus on three practical areas: accessibility, governance, and everyday workflow clarity.
With the new accessibility checker, teams can review emails against vision impairment scenarios and dark mode behavior before sending. Combined with screen reader-optimized code and improved text editing support, Stripo now provides a complete accessibility workflow inside the editor.
On the governance side, stricter 2FA enforcement, clearer account deletion rules, and improved role separation give administrators more predictable control over large teams and shared environments.
Workflow improvements, such as the recent usage view, refined UTM handling, better export controls, and cleaner editor logic, reduce friction in daily production.
We’ll continue refining core systems while preparing major upcoming features like improved module handling and AI widgets.
If you haven’t explored these updates yet, now is a good time to take a look.
0 comments