cliff effect: You are a person on government benefits, and you get a raise. You're making more money! But now that your income is higher, you don't make the cutoff for the benefits you receive. Even though you're taking home more money, your situation is worse. Some of your benefits drop to nothing, or almost nothing. You've fallen off "the cliff."
We are building the Cliff Effects webapp to help* Project Hope case workers make quantifiable predictions about their clients' potential cliff effects - and advise their clients accordingly.
(* Case workers handle their clients' problems on the ground; they aren't responsible for navigating benefit programs' complex policies, they do not have the time/resources to translate those policies into models. There's where we come in.)
We currently have a ReactJS frontend prototype.
We are working on:
- Benefit amount calculations: Converting rules into backend logic
- Data visualization: Experimenting with different ways of portraying "the cliff"
- Simplifying user experience: Making the tool navigable by case workers
- Familiarize yourself with the frontend.
- Decide whether you want to work on benefit calculations, code quality, data visualization, user experience, or project management.
- If you plan to develop code, set up your environment.
We use GitHub Issues to organize our work. Here's some quick reading about how to use issues, and here's the Cliff Effects issues board.
To follow these instructions, it'd help if you:
- have mentally perpared for experimentation and learning and/or
- know how to open your terminal/command prompt
- know a bit about how to navigate to different folders in your terminal
- know a bit about installing software for your terminal, like nodejs
Instructions:
- If you're new to github look at How to: fork a repo. Otherwise, fork and clone the repo, creating a link (remote branch) to the Code for Boston repo.
- In your termainal/command prompt, do
git checkout dev. Do not touch themasterbranch. - If you have nodejs, version 5.0+ is desired. If you don't, install it. If you don't know, do
node --versionin your terminal/command prompt. If you don't get a number, you don't have it. - In your command prompt/terminal, do
npm install. This might take a few minutes. Now you'll be able to try out the current UI or play with the code! - Do
npm startin terminal to automatically open a new browser tab and see a local version of the site. Works best in Chrome. - Saved changes will automatically be reflected in-browser. If you don't see the changes, refresh the page. If nothing has changed, ask for help!
- Press cltr+c to stop the local server that you have running.
To get yourself set up to keep up to date with the latest changes to the dev branch, make sure you've gone through Step 3 of the github guide. To keep your branches from getting tangled as you both make changes and keep up to date with our repo, take a look at our wiki page about a possible git workflow.
If you're interested in more in-depth debugging, we also recommend getting the React Developer Tools extension for Chrome.
If you have questions, feel free to ask.
We use React-Scripts test command (which wraps the Jest test framework) to run our automated test suite.
To run our test suite, run npm run test. That will run any tests that have changed since the last commit, and boot up an interactive testing session. The interactive session will prompt you with instructions, but the most important commands are a to run all tests, and q to quit the interactive session.
For information on how to write new tests, please refer to the React-Scripts documentation on the subject.
We're building the project with React. The app was set up with the Create React App CLI.
Aren't familiar with Git? Spend ~15 minutes learning with this interactive Git tutorial. Don't use -f or --force with branches that you have used to create a pull request.
More familiar with git, but not as familiar with collaboration? See a possible git workflow that could help keep things from getting messy.