Skip to content
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

Closed
paales opened this issue Aug 2, 2012 · 1 comment
Closed

Default libraries in Magento #58

paales opened this issue Aug 2, 2012 · 1 comment

Comments

@paales
Copy link
Contributor

paales commented Aug 2, 2012

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.

@magento-team
Copy link
Contributor

@paales
Thank you for the feedback.
It seems, that you're talking mostly about the front-end development. We do acknowledge necessity to standardize that area. In fact, there is already a tech track, which aims to improve the situation -- transition to the jQuery as a primary JavaScript library. It does make sense to also cover CSS and HTML along with the JavaScript. Active work in that direction has already been started, stay tuned.

Closing the ticket

magento-team pushed a commit that referenced this issue Jan 30, 2015
[Folks] Sprint 60 - Service Layer: Refactoring of Checkout and related modules
@stevieyu stevieyu mentioned this issue Apr 3, 2015
magento-engcom-team pushed a commit that referenced this issue Aug 27, 2018
Merge 2.3-develop to EPAM-PR-2
magento-engcom-team pushed a commit that referenced this issue Oct 8, 2018
magento-team pushed a commit that referenced this issue Nov 28, 2018
@FabXav FabXav mentioned this issue Oct 11, 2024
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants