diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 1a9fdc65564..3bb36006de4 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,121 +1,202 @@
-# Contributing to Fabric
+# 🎉 Contributing to Fabric 🥳
 
-## Questions?!?
 
-To get your questions answered, please ask/search on [Fabric's google group], [StackOverflow] or on Fabric's IRC channel (irc://irc.freenode.net/#fabric.js).
-Please do not open an issue if you're not sure it's a bug or if it's not a feature/suggestion.
+## 🧐 Questions?!? 
 
-For news about Fabric you can follow [@fabric.js], [@AndreaBogazzi], [@kangax], or [@kienzle_s] on Twitter.
-Demos and examples can be found on [jsfiddle], [codepen.io] and [fabricjs.com].
+Questions are legit but that doesn't make them bug reports...\
+Please refer to available resources (read below) and refrain from opening an issue in such a case.
+
+To find an answer first [search the repository](https://github.com/fabricjs/fabric.js/search?q=&type=Issues), it contains a lot of useful threads.\
+Refer to `Fabric's google group`, `StackOverflow` and [`Fabric's IRC channel`](irc://irc.freenode.net/#fabric.js) as well.\
+See [Links](#-links).
+
+Questions might inspire you to [improve the docs](#-improving-docs) 🌈 Please do 🌟.
+
+Demos and examples 🤓 can be found on [fabricjs.com](http://fabricjs.com/demos/), `jsfiddle`, `codepen.io` and more.
 
-## Issue tracker
 
-If you are sure that it's a bug in Fabric.js or a suggestion, open a new [issue] and try to answer the following questions:
+## 🏷️ Issue Tracker 
 
-- What did you do?
-- What did you expect to happen?
-- What happened instead?
+- **Before You Begin** 🎬
+  - 📌 Make sure you didn't fall into a known [**GOTCHA**](http://fabricjs.com/fabric-gotchas)
+  - 🔎 [**Searching**](https://github.com/fabricjs/fabric.js/search?q=&ref=cmdform&type=Issues) for existing issues and discussions is
+  🔋 **VITAL** in order to keep the community in a good state, prevent spamming 👎 and become a skilled fabric dev 🦉.
+- The **Title** must be informative, short and 🧿 to the point.
+- **Fill out the 🐛 report with care**, it is there for a reason.
+- **Description** 
+   - Describe the issue making sure you are very clear.
+   - Add (📎) logs, screenshots or videos if that makes sense.
+   - Make an effort explaining yourself
+   - A good description has been read at least 3 times before submitting.
+- **Test Case** 
+   - Create a minimal and immediate test case, reproducing the bug.
+   - Add relevant explanations.
+   - It should be extremely **easy** for someone to understand your bug and **fast** to reproduce it. **Don't leave it to us to do your part**.
+   - Bug templates can be found within a [bug report](https://github.com/fabricjs/fabric.js/issues/new?assignees=&labels=&template=bug_report.md)
+- Specify which **version** of Fabric.js you are using. 
+- **Upgrade** to the latest version before proceeding, your 🐛 may have turned into a 🦋.
 
-### Issue tracker guidelines
+**These are minimal requirements. Without them issues shall be ⛔.**
 
-If you think you found a bug in Fabric file an [issue](https://github.com/fabricjs/fabric.js/issues).
+If it's not a bug **OR** if you're unsure, start a 🤠 [discussion](https://github.com/fabricjs/fabric.js/discussions) or create a post ✉️ on [Fabric's google group](groups.google.com/forum/?fromgroups#!forum/fabricjs) where someone might clarify some of the things.
 
-- **Gotchas**: Make sure you didn't fall into a known [fabric-gotcha](http://fabricjs.com/fabric-gotchas)
 
-- **Search:** Before opening a new issue please take the time to [search](https://github.com/fabricjs/fabric.js/search?q=&ref=cmdform&type=Issues) Fabric's existing issues. This is vital to prevent spamming and to keep the community in a good state.
 
-- **Title:** Choose an informative title.
+## 🚧🎢 Developing 💡✨
 
-- **Description:** Use the questions above to describe the issue. Add logs, screenshots or videos if that makes sense.
+### Getting Started
 
-- **Test case:** Make sure you create a minimal and immediate test case, demonstrating the bug, with relevant explanations. It should be extremely **easy** and **fast** for someone to understand your bug and reproduce it. Bug templates can be found within a [bug report](https://github.com/fabricjs/fabric.js/issues/new?assignees=&labels=&template=bug_report.md)
+1. 🍴 Fork the repository
+1. 💾 Clone your 🍴 to your 💻
+1. Install dependencies 🕹️ `npm i --include=dev`
+1. Next Up [Prototyping](#-prototyping) & [Testing](#-testing)
 
-- **Fabric.js version:** Make sure to specify which version of Fabric.js you are using. The version can be found in [fabric.js file](https://github.com/fabricjs/fabric.js/blob/master/dist/fabric.js#L5) or just by executing `fabric.version` in the browser console. It is advised you upgrade to the latest version before proceeding.
+### 🧭 Prototyping 
+`.codesandbox/templates` contains templates for **INSTANT** out-of-the-box prototyping **👍 Try it out** 
 
-**Without these requirements issues shall be closed.**
+```bash
 
-If you're unsure about something that is not a bug, it's best to start a [discussion](https://github.com/fabricjs/fabric.js/discussions) or create a post on [Fabric's google group](groups.google.com/forum/?fromgroups#!forum/fabricjs) where someone might clarify some of the things.
+npm run sandbox build next [/path/to/sandbox]
+> building next app at /path/to/sandbox
 
-## Pull requests
+npm run sandbox start </path/to/sandbox>
+> starting dev server
 
-We are very grateful for your pull requests! This is your chance to improve Fabric for everyone else.
-Before you begin read this through and take a look at [fabric-gotchas](http://fabricjs.com/fabric-gotchas)
+npm run sandbox deploy </path/to/sandbox>
+> created codesandbox https://codesandbox.io/s/fgh476
 
-### Online one-click setup for making PRs
+npm run sandbox deploy -- --template node
+> created codesandbox https://codesandbox.io/s/fgh476
 
-Contribute to fabricjs using a fully featured online development environment that will automatically with a single click: clone the repo and install the dependencies.
+npm run sandbox -- --help
 
-[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/)
+> Usage: fabric.js sandbox [options] [command]
 
-### Setting up a local environment
+> sandbox commands
 
-1. Clone your fork of `fabric.js` to your machine
-1. Install dependencies: `npm i`
+Options:
+  -h, --help                      display help for command
 
-You can decide how you prefer to work:
+Commands:
+  deploy [options] [path]         deploy a sandbox to codesandbox
+  build <template> [destination]  build and start a sandbox
+  start <path>                    start a sandbox
+  help [command]                  display help for command
 
-#### `fabricjs.com`
-You can start the dev server that runs fabric's website and test live changes.
-After setting up `fabricjs.com` on your machine run `npm start` from the `fabric.js` folder.
-This will start the dev server and watch for changes in both repositories.
-While working, you might need to refresh the page for changes to take place.
-See [Working on fabricjs.com](#working-on-fabricjscom).
-To customize the dev server take a look at [`./scripts`](./scripts).
+```
+
+
+### 🔮 Symlinking 
+Establish symlinking to work with a local version on separate projects.
 
-#### symlinking
-You can symlink `fabric.js` and test your changes in a separate project.
 1. From `fabric.js` folder run `npm link` **OR** `yarn link`.
-1. From your project's folder run `npm link fabric` **OR** `yarn link fabric`.
+1. From the project's folder run `npm link fabric` **OR** `yarn link fabric`.
 
 See [npm link](https://docs.npmjs.com/cli/v8/commands/npm-link) **OR** [yarn link](https://yarnpkg.com/cli/link).\
 Don't forget to unlink the package once you're done.
 
-### Working on `fabricjs.com`
+---
+
+**Developing easily becomes a [PR](#-pull-requests) 😉**
+
+------
+
+## 🔎 Improving Docs 
+
+Improving **DOCS** is **SUPER** important for everyone.\
+Even if it's a small fix it is valuable 💎... **don't hestitate**!\
+We plan on building a brand new website, stay tuned.
+
+### ~~`fabricjs.com`~~ (*deprecated*)
 
 To develop fabric's site you need to clone [`fabricjs.com`](https://github.com/fabricjs/fabricjs.com) in the same parent folder of [`fabric.js`](https://github.com/fabricjs/fabric.js), so that `fabric.js` and `fabricjs.com` are siblings.
 To start the dev server run `npm start:dev` inside the `fabricjs.com` directory (after installing dependecies).
 If you are working on windows, check out [`jekyll` docs](https://jekyllrb.com/docs/installation/) for futher instructions.
 
-**Adding a DEMO**:
+### ~~Adding a DEMO~~ (*deprecated*)
 Take a look at an existing [demo file](https://github.com/fabricjs/fabricjs.com/blob/gh-pages/posts/demos/_posts/2020-2-15-custom-control-render.md).
 Create a new file in the same directory (`posts/demos/_posts`) and you're good to go.
 
-### Tests
-Fabric has 2 test suites: 
-- `unit` testing logic and state
-- `visual` testing visual outcome against image refs
 
-#### Running Tests
-- **Node.js**: run `npm test -- -a -d` to run **a**ll tests in **d**ebug mode (pass `--help` to see more options).
-- **Browser**: start `fabricjs.com` (`npm start`) and navigate to the `tests` tab where you will find the test interface.
 
-### Pull request guidelines
+## 🚀 Pull Requests 
 
-Here are a few notes you should take into account:
+Fabric is an open source project 🦄 and as such depends on the community.
 
-- **Code style, notes:** Make sure you have complied with the [guidelines](https://github.com/fabricjs/fabric.js/wiki/How-to-contribute-to-Fabric#code-style-notes)
+Genuine effort has made this repository what it is 🌺 Join Us as we strive to make Fabric better. 
 
-- **Distribution files:** Do your changes only in the [source files](https://github.com/fabricjs/fabric.js/tree/master/src). Don't include the [distribution files](https://github.com/fabricjs/fabric.js/tree/master/dist) in your commit.
+Before you PR, before even cloning or creating a branch, read this section through and take a look at [fabric-gotchas](http://fabricjs.com/fabric-gotchas).
 
-- **Add tests**: Tests are vital - invest time to extend the [tests suites](https://github.com/fabricjs/fabric.js/tree/master/test). More information about [QUnit](http://qunitjs.com/) tests can be found in the [wiki](https://github.com/fabricjs/fabric.js/wiki/How-to-contribute-to-Fabric#testing-fabric).
+### Getting Started
 
-- **Add documentation:** Fabric uses [JSDoc 3] for documentation. The generated documentation can be found at [fabricjs.com](http://fabricjs.com/docs).
+First of all, take a look at [fabric-gotchas](http://fabricjs.com/fabric-gotchas). It might save you time, effort and frustration.
 
-- **Create topic branches.** Don't use your master branch for pull request. It's better to create a new branch for every pull request.
+Follow [Devleoping](#-developing-) **OR** [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/from-referrer/) and start coding!
 
-- **One pull request per feature/bug**. If you want to do more than one thing, send multiple pull requests.
 
+### ✅ Guidelines 
+
+- **Code style & notes:** Make sure you have complied with the [guidelines](https://github.com/fabricjs/fabric.js/wiki/How-to-contribute-to-Fabric#code-style-notes)
+- **⛔ Distribution files:** Do your changes only in the [source files](https://github.com/fabricjs/fabric.js/tree/master/src). Don't include the [distribution files](https://github.com/fabricjs/fabric.js/tree/master/dist) in your commit.
+- **Add tests**: Tests are vital, invest time to extend the them, see [TESTING](#🧪-testing).
+- **Add documentation:** Fabric uses [JSDoc 3] for documentation. The generated documentation can be found at [fabricjs.com](http://fabricjs.com/docs), see [DOCS](#🔎-improving-docs).
+- **One pull request per feature/bug**. Create a new branch for every pull request. If you want to do more than one thing, send multiple pull requests.
 - **And there you go!** If you still have questions we're always happy to help. Also feel free to consult [wiki](https://github.com/fabricjs/fabric.js/wiki/How-to-contribute-to-Fabric).
 
-[Fabric's google group]: https://groups.google.com/forum/#!forum/fabricjs
-[stackoverflow]: http://stackoverflow.com/questions/tagged/fabricjs
-[@fabric.js]: https://twitter.com/fabricjs
-[@AndreaBogazzi]: https://twitter.com/AndreaBogazzi
-[@kangax]: https://twitter.com/kangax
-[@kienzle_s]: https://twitter.com/kienzle_s
-[jsfiddle]: http://jsfiddle.net/user/fabricjs/fiddles
-[codepen.io]: http://codepen.io/tag/fabricjs
-[fabricjs.com]: http://fabricjs.com/demos
-[fabricjs.com/docs]: http://fabricjs.com/docs
-[JSDoc 3]: http://usejsdoc.org/
-[issue]: https://github.com/fabric/fabric.js/issues
+
+
+## 🧪 Testing 
+Test suites use [`QUnit`](https://qunitjs.com/) for assertions and [`testem`](https://github.com/testem/testem) for serving
+- `unit` tests: test logic and state
+- `visual` tests: test visual outcome against image refs located at `/test/visual/golden`
+
+```bash
+
+npm test -- -a -d
+> Running all tests in debug mode (read more in the help section)
+
+npm test -- -s visual --dev -l -c chrome
+> Running live visual tests on chrome (navigate to see)
+
+npm test -- --help
+
+> Usage: fabric.js test [options]
+
+> run test suite
+
+Options:
+  -s, --suite <suite...>      test suite to run (choices: "unit", "visual")
+  -f, --file <file>           run a specific test file
+  --filter <filter>           filter tests by name
+  -a, --all                   run all tests (default: false)
+  -d, --debug                 debug visual tests by overriding refs (golden images) in case of visual changes (default:
+                              false)
+  -r, --recreate              recreate visual refs (golden images) (default: false)
+  -v, --verbose               log passing tests (default: false)
+  -l, --launch                launch tests in the browser (default: false)
+  --dev                       runs testem in `dev` mode, without a `ci` flag (default: false)
+  -c, --context <context...>  context to test in (choices: "chrome", "firefox", "node", default: ["chrome","node"])
+  -p, --port
+  -o, --out <out>             path to report test results to
+  --clear-cache               clear CLI test cache (default: false)
+  -h, --help                  display help for command
+
+```
+
+
+## 🚩 Links 
+
+For news about Fabric you can follow [@fabric.js], [@AndreaBogazzi], [@kangax], or [@kienzle_s] on Twitter.
+
+- [Fabric's google group](https://groups.google.com/forum/#!forum/fabricjs)
+- [stackoverflow](http://stackoverflow.com/questions/tagged/fabricjs)
+- [@fabric.js](https://twitter.com/fabricjs)
+- [@AndreaBogazzi](https://twitter.com/AndreaBogazzi)
+- [@kangax](https://twitter.com/kangax)
+- [@kienzle_s](https://twitter.com/kienzle_s)
+- [jsfiddle](http://jsfiddle.net/user/fabricjs/fiddles)
+- [codepen.io](http://codepen.io/tag/fabricjs)
+- [fabricjs.com](http://fabricjs.com/demos)
+- [fabricjs.com/docs](http://fabricjs.com/docs)
+- [JSDoc 3](http://usejsdoc.org/)
+- [issue](https://github.com/fabric/fabric.js/issues)