Update README.md

Amogh Singhal · web-flow · commit a6331e323520 · 2019-06-05T09:28:03.000+05:30
diff --git a/README.md b/README.md
@@ -1,7 +1,31 @@
-# Python-Interview-Problems-for-Practice
+# Python-Interview-Problems-for-Practice [![star this repo](http://githubbadges.com/star.svg?user=devAmoghS&repo=Python-Interview-Problems-for-Practice)](http://github.com/ddavison/github-badges) [![fork this repo](http://githubbadges.com/fork.svg?user=devAmoghS&repo=Python-Interview-Problems-for-Practice)](http://github.com/ddavison/github-badges/fork)
+![alt text](https://images.unsplash.com/photo-1494178270175-e96de2971df9?ixlib=rb-1.2.1&auto=format&fit=crop&w=972&q=80)
 40+ Common code and interview problems solved in Python (it's growing...)
 
 ### The core idea is not to utilize built-in functions or library and giving it a more logic-based approach, so that it can be language-friendly and not end up being another repository of "Python Tips and Tricks" .
 
+## How good is the code ?
+* It is well tested
+* It passes style checks (PEP8 compliant) [TODO]
+* It can compile in its current state (and there are relatively no issues)
+
+## How much support is available?
+* FAQs (coming soon)
+* Documentation (coming soon)
+
+## Issues
+Feel free to submit issues and enhancement requests.
+
+## Contributing
+Please refer to each project's style guidelines and guidelines for submitting patches and additions. In general, we follow the "fork-and-pull" Git workflow.
+
+ 1. **Fork** the repo on GitHub
+ 2. **Clone** the project to your own machine
+ 3. **Commit** changes to your own branch
+ 4. **Push** your work back up to your fork
+ 5. Submit a **Pull request** so that we can review your changes
+
+NOTE: Be sure to merge the latest from "upstream" before making a pull request!
+
 # LICENSE
 MIT License
