.webp)
.webp)
Alterações em "Redefining our way to handle themes"
Fechado em
- +2024-10-03 12:02:20 UTC
Conclusões (English)
- +These changes will happen:
- +
- +- Revert the decision to use “Mautic team” as theme authors for Core themes
- +- Allow companies and individuals to be recognized for contributing themes
- +- Define standards and guidelines for integrating new themes into the product
- +
- +
- +Final standards & guidelines
- +
- +1. We can provide items such as placeholders for logo and other resources to incentivize quality in development
- +2. Themes cannot bear the visual identity of the company that is proposing, as this could lead to submissions for convenience
- +3. The content of the themes cannot be aimed at promoting the author, as making this feature valuable for users is the goal
- +4. Themes can contain custom fonts (pages) and images, as long as they are open source or have compatible licences for distribution
- +5. Mobile-first design should be mandatory, as many papers show how the amount of mobile users is bigger than compared to desktop users
- +6. Emails should be designed in MJML
- +7. They will be removed if they become incompatible across the release of major versions
- +8. No external resources allowed, such as importing things from external URLs or CDNs, to prevent potential security issues, improve privacy and compatibility with different clients
- +9. They must not depend heavily on images in a way that themes become unusable or useless when changing an image
- +10. All images must be culturally sensitive and avoid text on top of them
- +11. Emails must have a designed unsubscribe page instead of the default blank screen with message
Compartilhar