edgi-govdata-archiving / 100days Goto Github PK
View Code? Open in Web Editor NEWWebsite for EDGI 100 Days Report
Home Page: https://100days.envirodatagov.org
License: Other
Website for EDGI 100 Days Report
Home Page: https://100days.envirodatagov.org
License: Other
Re-ticketed from #53
ULs and the sub- and sub-sub-headings in the ToC are at 1rem font size, rather than the 1.1rem the main body is. Can we make font size consistent in the body and the ToC at least as large as body copy?
Re-ticketed from #53
review commented out sections
Moving from Slack (https://edgi.slack.com/archives/C3EF5T7T6/p1497259423181120):
the report is distributed with https:// in the url, we need to make sure that works when visiting the site.
@patcon -- you dug up that gist: https://gist.github.com/cvan/8630f847f579f90e0c014dc5199c337b
Can you tackle this asap? I'm out until Monday but can revisit then
I think it would be good to give people "follow/hear more" hooks direct from 100 days, see edgi-govdata-archiving/edgi-website#40 as an example for the main website
https://www.google.com/url?q=
at the beginning and a trailing &...
unique per link)bugs/features
style/ux
questions
Figures in the 100 Days drive here: https://drive.google.com/drive/folders/0B1eR9Fjlv3o6S3ByQ3dna19jc3c
Re-ticketed from #53
on both the part 2 and the ali interview page there should be a link back to the overall first 100 days report somewhere, right now the EDGI link takes you there but that should probably take you the main EDGI site?
If the EDGI logo at top-left is the nav element to the 100 Days homepage, it might be nice to have a link somewhere (just on homepage?) back to main EDGI site
Re-ticketed from #53
There are some extra files we need to trim (imageN vs. part2figureN)
Reticketed from #1 (review)
EDGI logo makes sense but probably we want some kind of a cover image as well?
cc: @titaniumbones
naming, etc. could be improved for screen reader software
Re-ticketed from #53
Request from Sara: can we float the icon nav menu so it stays visible as the page is scrolled?
Re-ticketed from #53
data
add data to github and link from data methods page
Just realized the logo on the stop left doesn't display in FF (comparison with chrome)
I'm wondering if the issue is the path in post.css:
https://github.com/edgi-govdata-archiving/100days/blob/master/assets/post.css#L257
(and related to eventual v. expected deployment)
Our process got ugly on NameCheap.
There are two options that come to mind:
Re-ticketed from #53
the visual links to the interview and part 1 aren't appearing at the bottom of the report page?
Re-ticketed from #53
Should we consider linking to larger versions of the figures and tables from each, in case anyone wants to zoom in?
We should update the readme to cover steps to deploy, as we got more of these coming down the pipe!
Re-ticketed from #53
Should we use same link styling in this site as we do on main EDGI site? No underline and different hover effect?
Re-ticketed from #53
the anchor links for the references are slightly off, so if you link to a reference you have to scroll up to see the number referenced.
From @patcon in edgi-govdata-archiving/edgi-website#41 (repo for main EDGI site):
See: https://100days.envirodatagov.org/epa-under-siege.html
On a high-resolution screen (like a 4K) or when zooming out to a comparable degree via browser controls, the bottom of the page starts displaying very oddly, with tons of whitespace and a jumpy, glitchy scrollbar. By the way the glitching happens, it might be related to the "Back to Appendix Themes" button that hovers when at the bottom of page.
cc: @dcwalk
From Slack conversations (https://edgi.slack.com/archives/C4ER5PRD0/p1497857485718831):
Looks like we can pull from GitHub directly to the server, there may be reasons not to, but we can can/should discuss!
Reticketed from #32
https://rtyley.github.io/bfg-repo-cleaner/
Biggest image is 1.3MB, so anything over 2MB is probably something we could strip out (?)
Blocked on #33 bc existing PRs will break after this
@shaqsingh was lamenting over drinks the lack of analytics on the 100days site. I will admit she was torn about wanting them, but not liking trackers (if i'm remembering correctly).
We floated the idea of self-hosting analytics, of which I'm aware of Piwik.
Perhaps we should instead open an issue in overview repo on formulating a general analytics policy?
Related issue for EDGI website: edgi-govdata-archiving/edgi-website#27
Conversation in Slack RE: more social sharing, suggestion to add basic OG metadata, especially the image!
Re-ticketed from #53
The Chlorpyrifos map key covers a lot of the map and info box on mobile (worth hiding on mobile?)
Re-ticketed from #53
on peer reviews distinguishing between the review and our revisions
Not able to load CC license image:
I think the best fix is to add to assets instead of loading remotely, but that tends to be my preference. Any thoughts @shaqsingh and @patcon
These definitely aren't issues but just a couple ideas for quick updates that might be nice:
Make the words "download the PDF" a link to the PDF as well, on this page: https://envirodatagov.org/publication/the-epa-under-siege/, just for folks that aren't familiar with the PDF viewer and which button is the download.
Space the whole report out a bit more, for easier reading (between paragraphs and around pullout quotes), but especially add and standardize spacing before section headings. If we could use the same spacing that we do above "IX. APPENDIX: INTERVIEW COMPENDIUM" above the other section headings, it'd be nice to be consistent and seems like that spacing works a bit better.
Match the formatting of the figure captions to that of the table caption, which is indented from the body copy. Would be nice to be consistent and that seems to work a bit better to delineate the caption from the body.
EDIT: @patcon turned into checklist
Re-ticketed from #53
Fix alignment of author byline on Part II report page, so it's not cut off at smaller screen widths
I recall with the first chapter there were some visualizations where data processing happened (can't remember if those got cut.
It would be neat in future chapters if we could link from the report to our scripts and document data sources (and seems very EDGI 🥇 to me).
Would that make sense @shaqsingh?
Re-ticketed from #53
Images are not compressed, might want to include 2x scaling for hires
link to bios of contributors
Re-ticketed from #53
I think it’s nice to add a little space before/after figures/images, so they’re more distinct from copy.
Twitter/facebook share button on the reports might be nice so readers can quickly share, as they would with a news article.
There are some different reasons to
Re-ticketed from #53
Treatment of report page cover image/title not consistent on Part I and Part II (should we just use same layout for Part I as Part II?)
Re-ticketed from #53
Should we increase the offset of ULs so they stand out a bit more from body copy?
Re-ticketed from #53
I really think it aids readability of sections if there is more space around subheadings, and especially before them. Ideally, there’s slightly more space above a section heading than below it, so that the heading is visually associated with its content. There’s a lot of space before main headings, which is nice; would be good to add more around sub- and sub-sub-headings, too.
Does this need to be so tall? I feel like we are getting some odd length issues on small screens (i.e. this could be much more compact.) Probably doesn't belong in this PR so I can open an issue
I'm wondering if we could shorten the max-height and probably adjust the background-position
to better feature elements of each image.
Looks like we aren't using https for JS loads (and maybe we want to serve locally anyway): https://github.com/edgi-govdata-archiving/100days/search?utf8=%E2%9C%93&q=script&type=
Convo from:
https://edgi.slack.com/archives/C4ER5PRD0/p1497883588497433
I think related to #4
I think an issue with relative path is causing this console error:
Can fix here I think: https://github.com/edgi-govdata-archiving/100days/search?utf8=%E2%9C%93&q=assets%2FCH1.png&type=
Re-ticketed from #53
re-enable disqus comments
I'm moving @patcon's comments from #41 over here:
wonder if we should think a bit more about the title for SEO...?
Here's how we currently show up in Google search results:
![screenshot of 100 days report search result][https://imgur.com/UWZdMKD.png)
Note that there is nothing about "environment" in the words that show there. This is probably something to avoid? Perhaps we could either expand "EDGI" or add a secondary title mentioning what the 100 days site is?
I was using this "preview" tool here to see what some things looked like:
https://moz.com/learn/seo/title-tagAfter some fidgeting around, this seemed to be a decent option:
100 Days and Counting - An environmental report series | EDGI
Re: "-" vs "|". No solid pref, but bar seems to take up less space, assuming search engines are clever and consider the width of characters when choosing what to display. Mozilla also seems to recommend "-" for separate primary and secondary titles, and "|" for separating the brand.
@re: prev "The First 100 Days and Counting" vs new "100 Days and Counting". It seems that the new titles perhaps needlessly uses up valuable characters in the search results, which are perhaps better used on a secondary title mentioning the environment? Might we be able to use "100 Days and Counting" just in the title, to conserve space?
Could we ditch the "part 1" in the header? I know it's important to us, but unsure if it's important to people who might see it in search results, so perhaps a distraction?
Thoughts on something like this?
"EPA Under Siege - Part of an environmental report series | EDGI: 100 Days and Counting"
I think we need to rebuild static and ensure we are only pulling down the static site, not templates to productions
Re-ticketed from #53
There’s a stray extra linebreak or two. Maybe one of us should address minor formatting glitches in a PR?
Per conversation in #27 and in Slack, we should move to a more idiomatic use of Jekyll in advance of the remaining chapters publication!
Looks like the horizontal alignment isn't working quite as intended for the Peer Reviews section; I believe image should center and scale with charcoal background, as it does on main report page.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.