Website + App to manage every
View Demo
.
Report Bug
.
Request Feature
Information about Students with complete background, for use primarily by recruiters.
-
Information about Internships, Grades, Volunteer work, for reference of teachers, recruiters, department.
-
Verified Profiles: To ensure that the information added by the student is not fake, a system of verification is used for every update a student makes to his/her profile.
-
Three Level of User Permissions: A superuser, a teacher and the student. The student has the most basic access rights, the teacher verifies student information.
-
Dashboard for Student and Teachers: A dashboard facility with interactive forms for students and teachers to regularly update profiles.
-
Filter-based Results: For ease of use by teachers and recruiters, profiles can be filtered based on area of interest, research aptitude, projects, competitive coding skills etc.
-
Profile Updation and Analysis: Whenever a student updates his/her profile, it can be viewed by all as a student progress in the respective domain. Analysis is carried out to show how much progress is carried it in the domain in how much time.
-
Connecting teachers and students: When students take up projects under a college professor, the system users can view the professor portfolio and project details on the portal.
-
BE Project Information: Giving details about final year projects like teacher co-ordinator, project domain, abstract etc. to gauge the area of interest of the student.
- Frontend = React + React Native App
- Backend = Express.js
This is an example of how you may give instructions on setting up your project locally. To get a local copy up and running follow these simple example steps.
This is an example of how to list things you need to use the software and how to install them.
- Clone the repo
git clone https://github.com/your_username_/information-portal.git-
Load the
.envfile into theserver/clientwith referring to.env.example -
Go to the
serverandclientpackages in different terminals
cd server/
cd client/- Install NPM packages
npm install- Run the Client with
npm start- Run the Server with
npm devUse this space to show useful examples of how a project can be used. Additional screenshots, code examples and demos work well in this space. You may also link to more resources.
For more examples, please refer to the Documentation
- Fork the Project
- Clone your forked repo (
git clone REPO_URL) - Create your Feature Branch (
git checkout -b feature/AmazingFeature) - Commit your Changes (
git commit -m 'Add some AmazingFeature') - Push to the Branch (
git push origin feature/AmazingFeature) - Open a Pull Request
Note: NOBODY SHOULD DIRECTLY PUSH TO THE MAIN REPO.
- Add the main repo as upstream
git remote add upstream https://github.com/djunicode/information-portal.git - To get some changes from main repo
git pull upstream
There will be 5 branches
- main
- app
- backend
- frontend
- dev(will be created to merge and test the frontend and backend, then the final changes will be pushed to the main branch
Apart from the 5 branches above you can create as many branches as you want.
NOBODY SHOULD MAKE PULL REQUEST TO MASTER BRANCH. All changes should be made to either app or backend depending on where you are working.
- Commits and pull requests should be made with proper descriptive messages.
- Read any of these guidelines
- Do NOT commit or push any sensitive info such as passwords or emails in the code. Such data should go in the .env file, and a sample empty entry for the same should be added for the same in .env.example
- Make sure to check before you are pushing the changes to the branch
Distributed under the MIT License. See LICENSE for more information.