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.

User Experience / Interface Tiger Team

#MauticUXUI Driving Innovation: Shaping Engaging and Intuitive User Experiences

Changes at "Move Bootstrap LESS code into CoreBundle"

Compare view mode:
HTML view mode:

Title (English)

  • +Move Bootstrap LESS code into CoreBundle
  • +Move Bootstrap LESS code into CoreBundle
Deletions
Additions
  • +Move Bootstrap LESS code into CoreBundle
Deletions
Additions
  • +Move Bootstrap LESS code into CoreBundle

Description (English)

  • +

    Currently, there are several initiatives addressing both user experience and platform interface, but some insights about the future of these changes have come to light.

    To make the most of the user interface, we use a package called Bootstrap, which you can understand as a ready-made template for building the visual part of web applications but allows customization to fit each brand.

    Since this package was implemented, many changes have occurred to extend functionalities, creating new visuals for parts of the application that Bootstrap alone couldn't handle. Also, many modifications have been made, which have distanced us from the standard visual that came with this template, creating a unique identity for Mautic.

    However, these actions have generated significant problems:

    • Exactly identical code duplicated
    • Our customizations being applied on top of other existing customizations, both remaining in the user's installation
    • Unnecessary and unused code
    • Performance problems due to all the above issues
    • Difficulty in solving emerging issues over the years
    • On the UI developer side, it's hard to hunt down components in the code because they are scattered both in the package directory and within Mautic's own bundles


    Bootstrap has positive aspects when it comes to functionalities since this package is responsible for the functioning of tooltips, accordions, tabs, etc.


    I want to discuss:


    1. Considering the tremendous effort required to update Bootstrap package components, ensuring that nothing breaks, is it feasible to keep Mautic's UI as a package?
    2. Could we move only the UI files (.LESS) into the CoreBundle, to take control of customization and modernize the interface management techniques used without waiting for years until someone decides to update the package?
    3. Could we keep only the Bootstrap JS code, updating to newer versions, without loading its LESS UI files?
    4. Would it be feasible to bring new LESS components from Bootstrap into the CoreBundle with the update, but without importing and changing existing components to ensure a stable UI?
  • +<p>Currently, there are several initiatives addressing both user experience and platform interface, but some insights about the future of these changes have come to light.</p><p>To make the most of the user interface, we use a package called Bootstrap, which you can understand as a ready-made template for building the visual part of web applications but allows customization to fit each brand. </p><p>Since this package was implemented, many changes have occurred to extend functionalities, creating new visuals for parts of the application that Bootstrap alone couldn't handle. Also, many modifications have been made, which have distanced us from the standard visual that came with this template, creating a unique identity for Mautic.</p><p>However, these actions have generated significant problems:</p><ul><li>Exactly identical code duplicated</li><li>Our customizations being applied on top of other existing customizations, both remaining in the user's installation</li><li>Unnecessary and unused code</li><li>Performance problems due to all the above issues</li><li>Difficulty in solving emerging issues over the years</li><li>On the UI developer side, it's hard to hunt down components in the code because they are scattered both in the package directory and within Mautic's own bundles</li></ul><p><br></p><p>Bootstrap has positive aspects when it comes to functionalities since this package is responsible for the functioning of tooltips, accordions, tabs, etc.</p><p><br></p><p>I want to discuss:</p><p><br></p><ol><li>Considering the tremendous effort required to update Bootstrap package components, ensuring that nothing breaks, is it feasible to keep Mautic's UI as a package?</li><li>Could we move only the UI files (.LESS) into the CoreBundle, to take control of customization and modernize the interface management techniques used without waiting for years until someone decides to update the package?</li><li>Could we keep only the Bootstrap JS code, updating to newer versions, without loading its LESS UI files?</li><li>Would it be feasible to bring new LESS components from Bootstrap into the CoreBundle with the update, but without importing and changing existing components to ensure a stable UI?</li></ol>
Deletions
  • Our customizations being applied on top of other existing customizations, both remaining in the user's installation
  • Unnecessary and unused code
  • Performance problems due to all the above issues
  • Difficulty in solving emerging issues over the years
  • On the UI developer side, it's hard to hunt down components in the code because they are scattered both in the package directory and within Mautic's own bundles


Bootstrap has positive aspects when it comes to functionalities since this package is responsible for the functioning of tooltips, accordions, tabs, etc.


I want to discuss:


  1. Considering the tremendous effort required to update Bootstrap package components, ensuring that nothing breaks, is it feasible to keep Mautic's UI as a package?
  2. Could we move only the UI files (.LESS) into the CoreBundle, to take control of customization and modernize the interface management techniques used without waiting for years until someone decides to update the package?
  3. Could we keep only the Bootstrap JS code, updating to newer versions, without loading its LESS UI files?
  4. Would it be feasible to bring new LESS components from Bootstrap into the CoreBundle with the update, but without importing and changing existing components to ensure a stable UI?
Additions
  • +

    Currently, there are several initiatives addressing both user experience and platform interface, but some insights about the future of these changes have come to light.

    To make the most of the user interface, we use a package called Bootstrap, which you can understand as a ready-made template for building the visual part of web applications but allows customization to fit each brand.

    Since this package was implemented, many changes have occurred to extend functionalities, creating new visuals for parts of the application that Bootstrap alone couldn't handle. Also, many modifications have been made, which have distanced us from the standard visual that came with this template, creating a unique identity for Mautic.

    However, these actions have generated significant problems:

    • Exactly identical code duplicated
    • Our customizations being applied on top of other existing customizations, both remaining in the user's installation
    • Unnecessary and unused code
    • Performance problems due to all the above issues
    • Difficulty in solving emerging issues over the years
    • On the UI developer side, it's hard to hunt down components in the code because they are scattered both in the package directory and within Mautic's own bundles


    Bootstrap has positive aspects when it comes to functionalities since this package is responsible for the functioning of tooltips, accordions, tabs, etc.


    I want to discuss:


    1. Considering the tremendous effort required to update Bootstrap package components, ensuring that nothing breaks, is it feasible to keep Mautic's UI as a package?
    2. Could we move only the UI files (.LESS) into the CoreBundle, to take control of customization and modernize the interface management techniques used without waiting for years until someone decides to update the package?
    3. Could we keep only the Bootstrap JS code, updating to newer versions, without loading its LESS UI files?
    4. Would it be feasible to bring new LESS components from Bootstrap into the CoreBundle with the update, but without importing and changing existing components to ensure a stable UI?
Deletions
Additions
  • +<p>Currently, there are several initiatives addressing both user experience and platform interface, but some insights about the future of these changes have come to light.</p><p>To make the most of the user interface, we use a package called Bootstrap, which you can understand as a ready-made template for building the visual part of web applications but allows customization to fit each brand. </p><p>Since this package was implemented, many changes have occurred to extend functionalities, creating new visuals for parts of the application that Bootstrap alone couldn't handle. Also, many modifications have been made, which have distanced us from the standard visual that came with this template, creating a unique identity for Mautic.</p><p>However, these actions have generated significant problems:</p><ul><li>Exactly identical code duplicated</li><li>Our customizations being applied on top of other existing customizations, both remaining in the user's installation</li><li>Unnecessary and unused code</li><li>Performance problems due to all the above issues</li><li>Difficulty in solving emerging issues over the years</li><li>On the UI developer side, it's hard to hunt down components in the code because they are scattered both in the package directory and within Mautic's own bundles</li></ul><p><br></p><p>Bootstrap has positive aspects when it comes to functionalities since this package is responsible for the functioning of tooltips, accordions, tabs, etc.</p><p><br></p><p>I want to discuss:</p><p><br></p><ol><li>Considering the tremendous effort required to update Bootstrap package components, ensuring that nothing breaks, is it feasible to keep Mautic's UI as a package?</li><li>Could we move only the UI files (.LESS) into the CoreBundle, to take control of customization and modernize the interface management techniques used without waiting for years until someone decides to update the package?</li><li>Could we keep only the Bootstrap JS code, updating to newer versions, without loading its LESS UI files?</li><li>Would it be feasible to bring new LESS components from Bootstrap into the CoreBundle with the update, but without importing and changing existing components to ensure a stable UI?</li></ol>
Version number 1 out of 3 Show all versions Go back to debate
Version author
Avatar: Anderson José Eccel Anderson José Eccel
Version created at 09/05/2024 18:02

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

Change cookie settings