Using and Customizing Leaflet
It is built from the ground up to work efficiently and smoothly on both desktop and mobile platforms like iOS and Android, utilizing cutting-edge technologies included in HTML5 and CSS3. The focus is on usability, performance, small size, A-grade browser support, flexibility and an easy-to-use API. The OOP-based code of the library is designed to be modular, extensible and very easy to understand.
- It is seriously easy to understand and extend. There isn't a huge amount of out-of-the-box functionality (like there is with OpenLayers, but it is easy to add the functionality you need. It is easy to go and read the source code and follow along with what your application is doing, and this makes it easy for you to make adjustments where you need them.
- It works nicely on an Android or iOS device. If that isn't very important to you maybe you should rethink whether you need to put a map online at all. Embrace change! Touchscreens are the future!
- The lack of out-of-the-box functionality encourages you to simplify your application, which is the #1 problem with most web-mapping applications that I see. It encourages you to think about what the data is that you're trying to portray, and what the best ways are to do that. Leaflet is not very good for government agencies who think they should make an online map containing 700 layers and no clear direction or focus. But ask yourself: is there really any good reason to make such a map?
You can check out my work on GitHub: https://github.com/azgs/azgs-leaflet, where you can read about how to use it