Added guidelines for Bug reporting and resolving

README.md

@@ -1 +1,24 @@
-# TechBoardWebsite
+Project Structure
+==================
+
+We'll be following MVC Architecture for our application. Here app.js is the entry point for our application. Designs will be in the ./views directory. Structure of data i.e. models are in the ./models directory and controllers are in the ./controllers.
+
+
+Phase 1 (Designing Phase)
+=========================
+Designing phase is where we develop the layout and theme of the website. Along with the design, we will be working on Frontend part where we’ll define various actions on different events, toggling, and other effects using Javascript.
+
+1.Design_Landing  (Headed By Sameer Kumar Kushwaha)
+---------------------------------------------------
+
+This team is required to develop the designs for Landing Page and its associated pages. Make PR's in the development branch of the repository inside the ./views/Design_Landing  directory as specified by the team lead.
+
+2.Design_X_Club   (Headed By Soumyajit Deb)
+-------------------------------------------
+This team is required to develop the designs for Club X Page and its associated pages. Make PR's in the development branch of the repository inside the ./views/Design_X_Club  directory as specified by the team lead.
+
+
+
+Phase 2 (Backend and API Development)
+=====================================
+This phase will consist of developing APIs for different tasks like routing, updating, creating, deleting etc. along with database persistence.

package.json

@@ -0,0 +1,19 @@
+{
+  "name": "techboardwebsite",
+  "version": "1.0.0",
+  "description": "Technical Board Website 2020. A Programming Club project.",
+  "main": "app.js",
+  "scripts": {
+    "test": "echo \"Error: no test specified\" && exit 1"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/Technical-Board-IIITG/TechBoardWebsite.git"
+  },
+  "author": "Programming Club",
+  "license": "ISC",
+  "bugs": {
+    "url": "https://github.com/Technical-Board-IIITG/TechBoardWebsite/issues"
+  },
+  "homepage": "https://github.com/Technical-Board-IIITG/TechBoardWebsite#readme"
+}

views/Design_X_Club/Bug.md

@@ -0,0 +1,29 @@
+[comment]: <> (This is a BUG list for all the frontend related bugs currently present in Club Pages)
+[comment]: <> (A list of frontend related bugs which are currently present in the club page and has not been been rectified yet are maintained here)
+
+
+# Bug List
+
+
+## About
+
+ - This is a list consisting of all the **frontend** bugs currently present in **club** pages and has not been rectified yet. 
+
+ - To report a new bug, add the description of the bug in this bug list and make a pull request. Maintainers will then review the bug and    try to reproduce it themselves. If the bug is genuine and a concerning issue, bug will be added to this list and will be reported as a
+   issue for this repo. Credit will be given to the founder of the bug by mentioning his/her name, Github ID in the bug description.
+
+ - Format in which bug will be represented in this list:
+
+   1. A heading describing the bug in short (one line)
+   2. A description of the bug reported. Description should be to the point, concise and self explanatory. Bug description should also       contain the steps to be followed to reproduce the bug. Screenshots depicting the bug is welcome too.
+
+   3. Location: This contains the name of the directory/file or files which are concerned with the bug if they are known. 
+
+   4. **Reported by:** This should include the Name and Github ID of the person who reported the bug.
+
+   5. **Resolved by:** This should include the name and Github ID of the person (if any) who solved the bug.
+
+
+# BUGS
+
+[ ] **Add any new bug here**

views/Design_X_Club/TODO.md

@@ -0,0 +1,28 @@
+[comment]: <> (This is a TODO list for all the frontend features to be added)
+[comment]: <> (A list of frontend features to be added to Club Page is maintained here)
+
+# TODO List
+
+## About
+- This is a list consisting of all the **frontend** features to be included in  **club** pages. 
+
+- A feature can only be **checked off** if a **working** version of the feature is implemented and approved by the **maintainer** of the repository.
+
+- To propose a new feature and add it to the TODO list, please discuss about the feature before hand with the maintainers of the repository and only after the approval of the feature, can the feature be added to this list.
+
+- Format in which features will represented in this list:
+
+  1. A heading describing the feature in short (one line)
+  2. A description of the feature proposed. Description should be to the point, concise and self-explanatory. If this is a design idea to be implemented, A prototype design should also be included in the short description in png/jpeg format.
+  3. **Tech Stack:** The language, framework,etc. to be used to implement the feature.
+  4. **Assigned to:** This should include the email ID, Name and the github ID of the person (if any)  who is currently working on implementing the feature. This should be written down by maintainers of this repository.
+
+**PS:** A feature can be a minor addition too! 
+
+# FEATURES
+
+ [ ]  ******** Add the first feature to work upon here **********
+
+
+
+