-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default libraries in Magento #58
Comments
@paales Closing the ticket |
[Folks] Sprint 60 - Service Layer: Refactoring of Checkout and related modules
Merge 2.3-develop to EPAM-PR-2
… Data, Metadata, Page) (#58) - fixed dupes
… Data, Metadata, Page) (#58) - fixed dupes
The biggest hurdle of the current Magento installation is creating a consistent whole for a shop. The default installation in consistent throughout, but when you start installing modules from third parties everything gets messy. This is not because the third parties do a bad job, but because there aren't any default solutions (libraries, css classes, html components, etc.)
Twitter bootstrap is a great example and set of standards how to do things. Create the such a theme yourself you might say, but besides the work involved, it isn't the problem that a consistent theme is impossible to create, but making all modules compatible is. Having a great set of defaults lets module developers build their modules in a standard way without having to resort to their own solutions.
Especially in the Components section and Javascript Plugin section there are a lot of interesting ideas that greatly enrich the possibilities for developers.
It would be also great if we had default libraries for:
Lightboxes (fancybox is great)
Nivo Slider
The point is not that the libraries should be used throughout Magento, but they should be available in the system so that other developers will use them.
The text was updated successfully, but these errors were encountered: