Information about the cookies used on the website
We use cookies on our website to improve the performance and content of the site. The cookies enable us to provide a more individual user experience and social media channels.

Product Team

#MauticProductTeam Steering Mautic's Development: The Product Team,Pioneering Release Cycles and Roadmaps

Changes at "Redefining our way to handle themes"

Compare view mode:
HTML view mode:

Closed at

  • +2024-10-03 12:02:20 UTC
  • +2024-10-03 12:02:20 UTC
Deletions
Additions
  • +2024-10-03 12:02:20 UTC
Deletions
Additions
  • +2024-10-03 12:02:20 UTC

Conclusions (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
  • +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
Deletions
Additions
  • +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
Deletions
Additions
  • +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
Version number 4 out of 4 Show all versions Go back to debate
Version author
Avatar: Anderson José Eccel Anderson José Eccel
Version created at 03/10/2024 12:02

You need to enable all cookies in order to see this content.

Change cookie settings