Raahat
Change is the law of nature and the law goes for everything, from our opinions to human nature, from our body's nutrients need to emotional wellness needs and everything else. We need to track these changes to get better understanding of ourselves and everyone around. This tracking is nothing but a form of data collection and tracking. Especially during the pandemic and economic crisis like the ones we are facing now, the data maintenance has become crucial in so many cases like tracking the records of individuals for travel arrangements or distribution of rations or unemployment rate among the most affected classes of the society.
One such use case is of Survey Tracker application to maintain the insights from previous feedbacks and surveys which may go stale after some period of time. Tracking the surveys is considered an important aspect especially in works related to social welfare organisations because the records keep on changing based on individual needs and other factors. One way to keep your survey results fresh and actionable is by running your survey again and creating a multi wave tracking study, also known as tracker or tracking survey.
A tracking survey is a survey that asks the same questions across an interval of time, which allows you to “track” the changes from one deployment to the next and find trends over a certain period. Each time you roll out your survey, whether it’s annually, quarterly, or more frequently is called a “wave.” Comparing survey results across waves will show trends and changing attitudes that can prove helpful in taking further decisions for the governing bodies.
Here is the wireframe of the application we are building!
Prerequisites
Node.js
Please follow this link to setup Node.js in your system if not installed.
Technology Stack Used
- Front End - HTML, CSS , JavaScript
- Framewrok - Bulma
- Library - React
Problem Statements
Question v1.0
Here is the initial version of our Problem Statement, issues will be created based on this.
Question
Here is the final version of our Problem Statement, which we are aiming to achieve till the completion phase of the project.
General Guidelines
- Before working on any issue kindly go through the instructions given in the contributing and readme file carefully.
- For each issue, a detailed explanation is mentioned in issue ticket itself, for more details refer to figma design.
- While making any component, make sure that the code for the all generalised/common components must be kept in src->components->common folder.
- Kindly keep the source code in the src->components folder while making the specific components.
- Kindly use bulma or modular css for desiging a component.
- Please make sure to adhere to the folder structure of the project.
Note
Since you are here, you should most definitely consider joining us on this ride. If you still have any doubts, listen to Richard Stallman's perspective on Free software, free society
Don’t forget to fill the participation form 📃 to take part in the program, if not already done.
RSVP here to win* a limited edition Hacktoberfest 👕Tee-shirt or a 🎍plant.
*You must make four valid Pull Requests between October 1-31 to any public repo on Github
Start contributing!😊
Resources
For all the young ducklings, we have posted some useful resources to go through and understand GitHub and React.
- Bulma Documentation
- Figma for Developers
- Git Documentation
- GitHub Guides
- How to think in react
- React Documentation
- React Routing Video
- Top 5 Skills you must read before working with react
