The code and development of the JeevanRakht's website is housed here.
For more details - Refer to this paper.
This project consists of two part like all web application.
- Frontend Part -- HTML, CSS, jQuery and Bootstrap4
- Backend Part -- Node.js with express.js and MongoDB
- \bin:
- \db:
- \models
- \routes
- \views
- app.js
- \public -- html files
- \public\assets -- This will have scss, css, js, images
- gulpfile.js -- This is a task runner to launch app and motitor for file(scss,css,js) changes and reloads the browser.
- package.json
- Gruntfile.js
- Step1 -- Fork the project repo and clone it in your local directory
Note : You can directly update the frontend components inside public\ directory
but we have used gulp to automate the process. You need not to refresh the page after each change
or go to codepen to check your changes you made in scss or html or js files. Just run gulp and have fun.
- Step2 -- Download and install Node (npm comes along with node) Node
verify with below command
>>>node -v
>>>npm -v
- Step3 -- Install the npm modules from the package.json
>>> npm install
- Step4 -- Launch the application using below command:
Below command will run gulpfile.js and start the static website(Frontend)
>>> gulp
OR
Below command will start as full web application(Backend+Frontend)
>>> npm install -g nodemon
>>> npm start
- Step5 -- No more steps
Connect with co-mods if you stuck anywhere
- Add assets such as images and other media in assets folder.
- Follow standard coding practises, naming conventions and the regular document object model (DOM).
- Make issues on GitHub to propose new features, bugs and then make a PR referencing the same.
- It is now mandatory for everyone to comment on every PR made and read other people's code.
- Write your name in Contributors section below when PR is made.
- Make sure you update your REMOTE ORIGIN in case you have forked this repo : Refer
- Once you update the forked repo make sure you rebase the changes and then open the PR. Refer
- Every PR should only have one logical change and the least number of commits possible (If for some reasons the commits are higher then the creator of the PR would be asked to squash them.) If he/she doesn't comply, then PR is not to be merged.
Refer in case there are multiple commits.
- Utkarsh Gupta
- Imran Khan
- Vidit Kothari
- Gaurav Singh
- Shashank Kumar
- Soumya Bahera
- Sujan Patel