refactor: add maizzle v2.x compatibility

Author: cossssmin

.github/FUNDING.yml

@@ -9,4 +9,4 @@ community_bridge: # Replace with a single Community Bridge project-name e.g., cl
 liberapay: # Replace with a single Liberapay username
 issuehunt: # Replace with a single IssueHunt username
 otechie: # Replace with a single Otechie username
-custom: ['https://paypal.me/cossssmin', 'https://www.amazon.co.uk/hz/wishlist/ls/3I8KTU4FLQIZ1']
+custom: ['https://paypal.me/cossssmin']

.gitignore

@@ -1,8 +1,8 @@
-/node_modules/
-/build_local/
-.DS_Store
+node_modules
+build_local
+.vscode
+.idea
 Thumbs.db
-/.idea/
-/.vscode/
+.DS_Store
 npm-debug.log
 yarn-error.log

LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) Cosmin Popovici
+
+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.

LICENSE.md

@@ -12,22 +12,16 @@ The goal is to show examples of how you can use Maizzle to build great HTML emai
 
 The goal is definitely _not_ to tell anyone how they should code their emails.
 
-## Guidelines
+### Privacy & Security
 
-These are the guidelines that any Maizzle REMIX needs to follow.
+- Any sensitive data will be replaced with dummy data
 
-#### Privacy & Security
+- Experiments only use emails that are either publicly accessible (web versions, [CodePen](https://codepen.io/maizzle), [RGE](https://reallygoodemails.com/) or [curated.email](https://curated.email/)), or that you can subscribe to
 
-- Any sensitive data should be replaced with dummy data
+- Images are directly referenced from the online version of the original, if available. Otherwise they will be replaced with placeholders from an online service
 
-- Experiments should only be made on layouts that are either publicly accessible (web versions, [CodePen](https://codepen.io/maizzle), [RGE](https://reallygoodemails.com/) or [curated.email](https://curated.email/)), or that you have subscribed to and received
+### Responsive-only
 
-- Images must be directly referenced from the online version of the original. When unavailable, they will be replaced with placeholders from an online service
+Yes, [Hybrid coding](https://www.google.com/search?q=hybrid+email+coding&oq=hybrid+email+coding) works where `@media` queries aren't supported, but this is becoming more and more of an edge case, and it's also pretty limiting in terms of layout complexity.
 
-#### Built to resemble the original
-
-REMIXes should be as close as possible to the original's layout, color palette, and content.
-
-#### Responsive-only
-
-Yes, [Hybrid](https://www.google.com/search?q=hybrid+email+coding&oq=hybrid+email+coding) works where Responsive doesn't, but it's becoming more and more of an edge case, and it's pretty limiting. Considering the trend is to support `@media` queries in mobile email clients, Maizzle REMIX will only focus on the vast majority of cases, where responsive _is_ supported.
+Considering the trend is to support `@media` queries in mobile email clients, Maizzle REMIX will only focus on the vast majority of cases, where responsive design through `@media` queries _is_ supported.