18f / cfpb-eprocurement

Procurement prototypes for CFPB

CFPB eProcurement

Prototypes to help CFPB procure things more easily! This site is published automatically by 18F Pages.

Dependencies

• Jekyll: the static site generator
• Grunt: task runner for pulling in assets, linting and concatenating code, etc.
• Less: CSS pre-processor.
• Capital Framework: User interface pattern-library produced by the CFPB.
• tagalong makes it easy to write progressively enhanced data templates in plain old, semantic HTML.

NOTE: If you're new to Capital Framework, we encourage you to start here.

Installation

1. Install Node.js however you'd like.
2. Install Grunt

npm install -g grunt-cli

3. Next, install the dependencies and compile the project with:

./setup.sh

NOTE: To re-install and rebuild all the site’s assets run ./setup.sh again. See the usage section on updating all the project dependencies.

Configuration

If the software is configurable, describe it in detail, either here or in other documentation to which you link.

Usage

This is a Jekyll site. To view it locally, run one of the following:

jekyll serve
# or
npm start

Each time you fetch from the upstream repository (this repo), run ./setup.sh. This setup script will remove and re-install the project dependencies and rebuild the site's JavaScript and CSS assets.

To watch for changes in the source code and automatically update the running site, open a terminal and run:

grunt watch

Alternatively, if you don't want to run the full watch task, there are three available sub-tasks:

# Watch & compile CSS only
grunt watch:css

# Watch & compile JS only
grunt watch:js

# Watch & compile CSS & JS only
grunt watch:cssjs

How to test the software

TODO

Known issues

Document any known significant shortcomings with the software.

Getting help

Instruct users how to get help with this software; this might include links to an issue tracker, wiki, mailing list, etc.

Use the issue tracker to follow the development conversation. If you find a bug not listed in the issue tracker, please file a bug report.

---

Open source licensing info

2. CC0-1.0 License
3. Contributing

---

Credits and references

1. Projects that inspired you
2. Related projects
3. Books, papers, talks, or other sources that have meaniginful impact or influence on this project

cfpb-eprocurement's Issues

"Running" column

Right now, we have a couple columns in the timeline that look like this:

The "running" column shows the cumulative delay to the project. So, the delays on previous milestones add up to contribute to this "running" delay.

I'm worried this wording won't make sense to users. @kategarklavs: Can you help us out?

Update data to have more procurements and timelines

Add timeline data for other procurements to the fake data file.

Showing how many days since a procurement’s status was last changed will allow contracting officers to more quickly identify backburnered priorities, in turn leading them to spend their time more effectively

Procurement status icons aren't visible in IE

E.g. the "!" triangle icon on the overdue procurement.

Change logged in user's role to CO

Document status labels ("Due in...") should be consistent

The document status labels on the milestone list (procurement detail) view show negative values for "Due in", and use different colors from the aggregate (procurement list) view:

correct

incorrect

Collecting key procurement information once and then using it to populate key documents in the acquisition package will be faster than manually compiling the documents through copy and paste

Add procurement team contact information to dashboard list

In general, I want to make sure that we show the contact information of the procurement officer on the COR dashboard. I want to verify some assumptions about whether/how showing this information is important.

• Show the primary procurement contact, their role and their contact information near the procurement
  description.
• Show the secondary procurement contact, their role and their contact information near the procurement
  description.

Indicate completed documents/milestones as locked.

• Append '(locked)' at the end of the status sentence, i.e., "Market research synthesis completed (locked)."

Accordingly, on the document view, we should indicate somehow that the document is no longer editable. I suggest:

• remove the comment field and and submit button
• append '(locked)' at the end of the document title

Difference between latest activity and upcoming milestones unclear

I think we want to differentiate by adding the document revision numbers?

Add the "what's next" and "who's responsible columns"

Need to sketch out this one.

Convert forecast dates to date ranges

One of our assumptions is that forecasted date ranges are more useful to CORs than made up dates.
I think it's easier to keep the dates in the fake data as single dates, so I wonder whether we can have Jekyll add a few dates on either end of the "forecasted date" to make it into a range. For example, under the "forecasted date" in the first row, could 01/11/2016 become 01/09/2016-01/12/2016?

Add a "logged in as Myra Ball (COR)" somewhere near the top right

We want to make it clear that this is a dashboard for a single COR. Adding text like:

Logged in as Myra Ball (COR)

to the top right of the page seems like an easy way to do that?

Add legend to dashboard timeline

Add a legend that explains what the various colors in the timeline table mean.

Add the "responsible team" field to somewhere near the description

There's a column called "responsible team" in the fake data demarcate whether CFPB internal procurement shop or the one over at BFS is responsible for a procurement. I'd like to add this somewhere near the description so we can test whether this information is important to folks or not.