jlord / federal-gov

Hello, there!

Link exchange with friends^?:

---

federal-gov's Issues

Add RSS Feed

It's been requested 👍

Contributions!

Starting a discussion on contributions.

Tech Contributions

Here on GitHub as Pull Requests of course! In the coming weeks I'll be working more on the underlying library, sheetsee.js, but typos and CSS fixes (or whole new/better layouts!?) and whatnots can definitely happen here.

Article Contributions

I've had a project with a totally open spreadsheet before and that was tough to manage and revert when bad input was entered. And because of the nature of the contents the submissions will need to be checked to be real anyways so here's what I'm thinking (and have set up):

1. Fill out Google Form with new submission.
2. New submissions are reviewed via response spreadsheet (anyone can comment).
3. Submissions are copied onto final spreadsheet data for site (anyone can comment).

Google Form Submissions

Hi @jlord,
Thank you for starting this project.

I find that having two different platforms for collaboration a bit cumbersome.
Especially when the chat system on Google Spreadsheets doesn't lend itself well to asynchronous collaboration.

Suggestion

What if Google Form submissions/responses end up as JSON blobs that are pull-requested into, say, data/ directory that lives at the root of this project?
PROS

• Allow for collaboration and communication on one unified platform.
• Each article in question could be reviewed, modified/edited/changed in isolation.

CONS

• The page would have to send one GET request per article, which could slow down the perfomance of the site in the long run.
• Example GET request would look like:

  <script src="https://raw.githubusercontent.com/jlord/federal-gov/master/data/president-elect-son-in-law-senior-white-house-advisor.json" type="application/json"></script>
  

  • This leads to tight coupling of static page(s) and content.