User Experience / Interface Tiger Team
#MauticUXUI Driving Innovation: Shaping Engaging and Intuitive User Experiences
If we take an overview of what plugins are today within the platform, we will realize that they are integrations with external services such as CRM or data analysis tools, lead sources and other things that are directly related to some type of of a complete system that exists outside the Mautic domains and is independent of it.
Plugins from the marketplace have a characteristic more related to the addition of functionalities within the platform itself.
To ensure long-term consistency, considering that the marketplace itself is still a beta feature, this would be the perfect time to adjust some things with good planning so that this does not become a problem later.
The objective is to avoid confusion between the nomenclature of features added through the marketplace and the addition of external services such as Twitter, Facebook, etc.
As user help files grow we see that soon many different sections will be talking about plugins without a solid framework of differentiation.
This way, Plugins would be related to the Marketplace and External Services to what we find today on the Plugins page.
What do you think about all this?
The debate was closed on 24/04/2024 15:14 with these conclusions:
No changes
Report inappropriate content
Is this content inappropriate?
Close debate
What is the summary or conclusion of this debate?
Comment details
You are seeing a single comment
View all comments
I don't really see a need to change the naming of plugins. There are all kinds of different names for things like that, and plugins is fairly common. Drupal uses the term "Modules" for both features and integrations. "Connectors" could be another option, but that would only be for external services.
My vote would be to keep the name of Plugins (particularly with the technical considerations that John mentioned) but change how they're organized. The Plugins page could have multiple tabs for 'Core' plugins (maybe call that something like Features?) and Integrations. Companies hosting their own distributions of Mautic (e.g. Acquia, Webmecanik, Dropsolid, etc.) will also have their own plugins - and while they may handle availability of community-contributed plugins differently, those companies may want to clearly separate the plugins (features and/or integrations) that they've built and maintain vs. what's available from the community.
Loading comments ...