-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pre-Election Reporting Dates Template #3227
Pre-Election Reporting Dates Template #3227
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #3227 +/- ##
===========================================
+ Coverage 74.6% 74.62% +0.01%
===========================================
Files 120 120
Lines 7160 7168 +8
Branches 633 633
===========================================
+ Hits 5342 5349 +7
- Misses 1818 1819 +1
Continue to review full report at Codecov.
|
{% endblock %} | ||
|
||
<article class="main container"> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add the main title in here? <h1 class="heading--main">{{ self.title }}</h1>
border: none; | ||
border-bottom: 1px solid $gray-light !important; | ||
position: relative; | ||
font-weight: bold; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the mockup, I think they are supposed to be bold
https://user-images.githubusercontent.com/31663028/64990128-27c1fb00-d89d-11e9-8d89-57055218bbb5.png
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we only want the column names to be bold, not the dates.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we want the "All footers" section to be in an accordion. I'm not sure how it impacts how this page is printed, but that's a concern for Info. I don't mind having the footers all there in the event that some of our users find clicking on the numbers/symbols difficult to do for accessibility reasons. But I'm open to discussing it further. If we do proceed with an accordion, it has to be in our current style, which this is not.
I think we should consider two page types for full-width page.
|
I agree, we should have two in a separate PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@johnnyporkchops This looks great!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything looks great! Thanks, @johnnyporkchops
tr { | ||
display: table-row ; | ||
&.row_display { | ||
display: table-row; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It isn't breaking anything but do we need this twice?
border: 1px solid $gray-light; | ||
|
||
&:first-child { | ||
border-left:none; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does the linter say about spaces after colons? It only affects anything when we're searching the code looking for something specific, like "border: "—really minor thing.
} | ||
|
||
tr.footnote_row { | ||
/*background: $inverse !important;*/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we remove the comments of unused code? (Or explain why we want them? (I know I add and then forget too many comments))
pfScriptElem.src = "{% asset_for_js 'polyfills.js' %}"; | ||
document.head.appendChild(pfScriptElem); | ||
} | ||
</script> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! Sorry I forgot that one.
Summary (required)
This is the full-width page Wagtail template and accompanying JS that will allow us to achieve the mocked up experience and responsive design in issue #3016
Include a summary of proposed changes.
Related PR: Closing #3188 in favor of this PR
Impacted areas of the application
modified: fec/static/scss/components/_table-styles.scss
modified: home/models.py
modified: ../fec/static/js/polyfills.js
modified: ../package-lock.json
modified: ../package.json
modified: fec/templates/base.html
new: fec/static/js/pages/reporting-dates-tables.js
new: home/migrations/0105_auto_20191002_1534.py
new: home/templates/home/full_width_page.html
new: home/migrations/0105_auto_20191002_1534
To Do: (All but the first one here are easy fixes)
All footnotes
section.data-init.js
(required for the A11Y dialog) interferes with the accordion trigger. I have left the nativeHTML5 Details
element here for now.#ddd
becomes$gray-medium
or whatever)!important
rules as possible - some may not be necessaryScreenshots
Screenshots to come soon
How to test
feature/3016-reporting-dates-table-template
Steps 2 through 6 are designed to keep your local
cfdm_cms_test
database in tact for working with other branches. You can forego this and just test this on feature.craetedb cfdm_cms_test_2019
pg_restore --dbname cfdm_cms_test_2019 --no-acl --no-owner <LOCAL PATH TO DUMP FILE NAME>
export DATABASE_URL=postgresql://:@/cfdm_cms_test_2019
(see step 14 to point back)./manage.py migrate
CD to /fec-cms and
rm -rf node_modules
npm install
npm run build
cd to fec-cms/fec/ and
./manage.py runserver
go to
127.0.0.1/admin
create a page of type
FullWidthPage
create three html blocks and paste in the sections from the attached files into the three blocks. This step simulates the content team members copy/pasting from Excel but leaves out the actual spreadsheet part here.
sample-data.txt
When you are done, point your local database env var back to export cfdm_cms_test:
export DATABASE_URL=postgresql://:@/cfdm_cms_test
or if you use a bash profile with your database env var saved, just run:unset DATABASE_URL