caciviclab / odca-jekyll Goto Github PK

We want our jekyll site to look like the ODCA mocks and not necessarily the existing site. We should re-use the existing styles where possible but build towards the mocks if there is some divergence.

• Copy minima files to repo, remove the minima gem theme
• Scaffold base SMACSS framework
• Convert all the LESS to SASS so folks can take a look at the source and pull in what they want (but not commit it to master)
• Port over base styles
• Port components by page
  • Header/footer #26
  • Home #27
  • Ballot #28
  • Candidate #29
  • Referendum #30
  • Referendum supporting/opposing #31
  • Committee #32
  • About #33

Wiki should document how to add ballot information so folks can add their city to ODCA on their own https://github.com/caciviclab/odca-jekyll/wiki

How should we combine this repo with disclosure-backend-static?

S3 or should we just store them in Jekyll?

Office elections like "City Council" often run in multiple districts. We'd like to group all the districts under a
common heading. Mockups here.

As a voter, I want a link on the candidate page so that I can learn more information about the candidate from an outside authroitative source.

Link to candidate committee from the candidate page as contributions.

The committees have been created on the feature/committees branch.

Until the Oakland June and November 2018 elections have data that we've reviewed (they currently show missing finance data), let's hide them in the nav so users are not confused.

We'll probably want to do this with a javascript visualization library.

• Depends on #55

Part of #18 to style the candidate page.

We want our jekyll site to look like the ODCA mocks and not necessarily the existing site. We should re-use the existing styles where possible but build towards the mocks if there is some divergence.

You can take a look at this branch for the disclosure-frontend converted LESS files in case it's helpful.

Help us shape our CSS architecture by documenting your work or suggesting better process and methods.

There are many places throughout the site where data doesn't show up and we get unideal behavior. Often headings with no content below it or "$0.00" repeated.

• candidate summary on ballot page
• candidate pages
• referendum page

Implement the new ballot nav.

Don't worry about grouping the office elections together, that is covered by #91.

Part of #18 to style the about page and other content pages.

We want our jekyll site to look like the ODCA mocks and not necessarily the existing site. We should re-use the existing styles where possible but build towards the mocks if there is some divergence.

You can take a look at this branch for the disclosure-frontend converted LESS files in case it's helpful.

Help us shape our CSS architecture by documenting your work or suggesting better process and methods.

The sum of supporting_organizations.amount should be totaled on the back end so the front end doesn't have to do it.

We need to be able to update the finance information automatically. Currently, you run the gulp tasks and then have to manually review the changes.

Update the base styles for the new site design.

• Color palette
• Fonts
• Typography
• Base elements (p, a, etc)

The money filter assumes you're dealing with pennies so 109521.66 -> $1,095.22

We don't track fractions of dollars nor do we use non USD currency, so I think we should create a new filter dollar that will round and convert to dollar formatting.

Part of #18 to style the ballot/election page.

We want our jekyll site to look like the ODCA mocks and not necessarily the existing site. We should re-use the existing styles where possible but build towards the mocks if there is some divergence.

You can take a look at this branch for the disclosure-frontend converted LESS files in case it's helpful.

Help us shape our CSS architecture by documenting your work or suggesting better process and methods.

Moving the generated finance data to _data instead of the collection files will keep a cleaner distinction between the human-editable files and the finance data which is generated from disclosure-backend-static.

This is somewhat of an experiment, because I'm not really sure how it will work out.

Implement the office election redesign.

Part of #18.

We want our jekyll site to look like the ODCA mocks and not necessarily the existing site. We should re-use the existing styles where possible but build towards the mocks if there is some divergence.

You can take a look at this branch for the disclosure-frontend converted LESS files in case it's helpful.

Help us shape our CSS architecture by documenting your work or suggesting better process and methods.

We currently show total of expenditures opposing/supporting a candidate but this should link to a page showing the actual independent expenditures.

Part of #18 to style the referendum page.

We want our jekyll site to look like the ODCA mocks and not necessarily the existing site. We should re-use the existing styles where possible but build towards the mocks if there is some divergence.

You can take a look at this branch for the disclosure-frontend converted LESS files in case it's helpful.

Help us shape our CSS architecture by documenting your work or suggesting better process and methods.

https://caciviclab.org/odca-jekyll/referendum/oakland/2018-06-05/library-parcel-tax/

Part of #18 to style the committee page.

We want our jekyll site to look like the ODCA mocks and not necessarily the existing site. We should re-use the existing styles where possible but build towards the mocks if there is some divergence.

You can take a look at this branch for the disclosure-frontend converted LESS files in case it's helpful.

Help us shape our CSS architecture by documenting your work or suggesting better process and methods.

On the disclosure-frontend site, we have a page for office elections that list all the candidates for a particular office election (aka "race").

The only thing on the ballot is Measure D, the Library Parcel Tax.

Implement the new footer design.

Similar to what you see on the Candidate page.

Election totals are available on the backend. They Oakland-wide election total should appear on the landing page.

To implement, we need to copy the totals to the front end.

1. Add a gulp task to copy over the totals.
2. In the landing page template, fetch the totals for the cities you're interested (let's just start with Oakland).

In creating this experiment, I just wanted to show that it was possible to create a site around multiple localities and multiple elections but I didn't give a whole lot of thought into what would be the most effective way to present that information.

• Document the gulp tasks as an optional step to get the latest finance data
• Describe what this project is and how it fits in with ODCA
• Add some kind of CI and tests
• Describe any technical pre-reqs for development
• Link to project tasks in README
• Link to onboarding docs
• Add a deprecation notice to disclosure-frontend and instructions on where to go/what to do in order to participate (link to backend-static and this)
• Rename the repo to www.opendisclosure.io

Implement the new landing page.

Implement the new header design.

Also two lines are appearing under each contribution type

The total money raised to date used to be calculated in JS, it would be nice if this was calculated for us on the back end and stored on the committee.

We're not going to be doing candidate Bios for 2018, so let's remove them from all the candidate pages.

I think folks are leaning toward:

• webpack
• react
• mocha + karma

• candidate
• referendum
• committee
• ballot

Part of #18 to style the referendum supporting/opposing page.

We want our jekyll site to look like the ODCA mocks and not necessarily the existing site. We should re-use the existing styles where possible but build towards the mocks if there is some divergence.

You can take a look at this branch for the disclosure-frontend converted LESS files in case it's helpful.

Help us shape our CSS architecture by documenting your work or suggesting better process and methods.

We are overdue for a design review. Let's step through the site so far and create issues and fixes for where the site doesn't match the design.

I think we already have a GA analytics ID for ODCA, we just need to add it to the config.

The Library Parcel Tax does not have a number yet. Using the referendum number is the most straight forward way to identify a referendum (and what most humans would refer to it as). How should we identify it?

Note: that in order to be globally unique, we really identify it with the election, locality, and number.

This shows up when I'm pulling in supporting/opposing money for referendums and I noticed the slug for the Library Parcel Tax was missing.

We only show the candidate's latest data, so for a previous election, it will be using the current election's numbers (which is wrong).

Also, if for some reason the candidate is running in a new election, but hasn't filed, we'll show their old data in the current election.

Similar to whats' already on the Referendum page.

Part of #18.

We want our jekyll site to look like the ODCA mocks and not necessarily the existing site. We should re-use the existing styles where possible but build towards the mocks if there is some divergence.

You can take a look at this branch for the disclosure-frontend converted LESS files in case it's helpful.

Help us shape our CSS architecture by documenting your work or suggesting better process and methods.

For the header nav, let's try to keep it CSS-only and avoid pulling in any javascript at this point.

First data for the locality page! Contributions by origin are here!