Update README

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,6 @@
+Make sure these boxes are checked( - [x] ) before submitting an issue.
+
+- [ ] Running latest npm and node? (Run `npm --version` and `node --version`)
+- [ ] The `node_modules` folder has right permissions (Run `ls -ld $(npm root -g)/crontab-ui`)
+- [ ] Read [issues.md](https://github.com/alseambusher/crontab-ui/blob/master/README/issues.md)
+- [ ] Gone through existing open and closed issues. 

README/README.md

@@ -10,6 +10,7 @@ Editing the plain text crontab is error prone for managing jobs, e.g., adding jo
 3. Backup your crontabs.
 4. Export crontab and deploy on other machines without much hassle.
 5. Error log support.
+6. Mailing and hooks support.
 
 Read [this](http://lifepluslinux.blogspot.in/2015/06/crontab-ui-easy-and-safe-way-to-manage.html) to see more details.
 

README/issues.md

@@ -12,3 +12,5 @@ __Hosting crontab-ui : it works on localhost but not outside the server__ - You
 __crontab-ui stopped working__ - It can happen that your crontab-ui can stop working for some reason like adding incorrect jobs or timings. In order to fix it, you can just go ahead a remove the job from `crontab.db` or `env.db` in "crontabs" folder and restart crontab-ui.
 
 __Where is my root node_modules folder__ - You can find it by `npm root -g`
+
+__Mailing related issue__ - Refer [this](https://github.com/alseambusher/crontab-ui/blob/master/README/mail.md).