2. Use the GitHub Issues EXCLUSIVELY for BUGS, FEATURE REQUESTS or QUESTIONS
2. Use the GitHub Issues EXCLUSIVELY for BUGS, FEATURE REQUESTS or QUESTIONS. Prefix the title of the issue with its context, eg. `[Bug]: ....`
3. Do a quick SEARCH first, to see if someone else didn't open the same issue
4. DON'T ASK to create examples/code for you, read DOCS and APIs first, then you can post what you have tried (we'd like to see your code) and what you're unable to achieve
5. All the statements/questions have to be filled/answered, otherwise, the issue might be CLOSED
5. All relative statements/questions have to be filled/answered, otherwise, the issue might be CLOSED
## For BUGS
## You're submitting a BUG
1. Are you using the latest release (older versions are NOT supported)?
1. If you're not sure, type `grapesjs.version` in console and press ENTER
1. Are you facing the bug with your local copy of GrapesJS or with the current demo?
@ -20,3 +20,7 @@ READ and FOLLOW next 5 steps, then REMOVE them before posting the issue
1. Attach screenshots (using KAP/LICEcap), screencasts or live demo