Copyright (c) 2018 Aggelos Gesoulis - Katerina Limpitsouni
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
At several parts of this theme we turned for solutions to people who have open-sourced their hard work and we want to thank them especially. To mention a few:
Viljami Salminen for the responsive-navigation code.
The guys that created the Materialize framework, whose work on forms was used on a few elements.
Jonathan Neal for his Flexibility library that allows all of us to use flexbox without having to worry too much for old browsers.
Evie uses flexbox but includes the superb Flexibility library to make it work even on Internet Explorer 9+.
However, the targeted browsers are the last two versions of the major ones(Chrome, Firefox, Safari, Edge) and most modern mobile devices.
We would love to improve and perfect Evie and we are sure we've missed a few things. You can report them directly on GitHub or on Twitter.
We are really excited to see what you will create with Evie and the ways you will choose to extend it. If you have created re-usable components that will be of value to others, please contact us or create a pull request on GitHub and we can start collaborating on it.
When Katerina had the idea for unDraw, we created really fast a set of style patterns, that would allow us to focus on more challenging aspects, like color transformations in real time.
This style actually managed to support the whole development of unDraw without slowing us down. So the thought was simple. To organize it a bit better and let it be useful for everyone.
We normally use the BEM methodology (a bit adjusted to our liking), but it would bloat and make the learning curve for Evie much steeper, so we tried to remove all such classes wherever we could and made sense.
This certainly is not a full-blown framework but we feel that it provides a great starting point for different websites and applications. We really can't wait to see what you can create with it!