Mechanics for building a 5-year plan

[fgregg]

The core functionality of this application is users building a portfolio of projects that could go into an annual budget process (the Capital Improvement Plan).

The users are Cook County Forest Preserve Department Heads, and they will be building a scenario portfolio from around 100 projects. Users should be able to look through the list of projects, select an unselected project, and deselect selected projects.

When a project is selected, it should be placed in visually distinct place from the unselected projects (could just be placed at top of list of all projects, but this is left to you).

When a project is selected or deselected, overall portfolio characteristics should be recalculated. These include.

1. overall budget
2. the names of component projects
3. zones
4. and other attributes to be determined at a future date.

The state of a portfolio will need to be saved to a database.

Here's a current wireframe of what this could look like:

While we are waiting on other parts of this project, let's start building out these these interaction patterns.

[fgregg]

Here's some mocked up data for you to work with. https://github.com/datamade/ccfp-asset-dashboard/blob/master/raw/simplified.csv

[smcalilly]

@fgregg Here is a summary of work steps based on what we discussed. Let me know if I'm missing anything or misunderstood something.

• [x] sketch a basic UI
• [x] create a dummy model + load the mock data. create a view that renders the data in a template
• [x] use data to create a basic UI with these core interactions:
  • select projects and add them to a potential portfolio
  • calculate the portfolio's budget
  • select/choose different projects and recalculate

[fgregg]

looks great @smcalilly

[smcalilly]

This one should be good to close?