You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Check that what we do separates SYE specific stuff from the more generic code
Data
π House of Representatives - We have data for the House of Representatives in EP (around 300 members), but it appears under the name βNational Assemblyβ. The National Assembly includes both the House of Representatives and the Senate. (issue to rename it)(PR to rename it). Name changed.
π Governors - We have data for the governors through Struanβs scraper (around 30 members) which seems similar to what is displayed now in the Jekyll site
π Not a module but add a boolean featured field in the summaries frontmatter in prose.io
Scripts
π Finish deploy script to clone the prose repo, clone the sinatra repo, run the app, scrape the site and push to the static repo. Set up a webhook for prose?
Pages
All those "nice-to-have" comments: It's probably better to leave them for when the rest of the site is finished
π Posts - Maybe add a method to show a summary instead of the whole post contents.
From the requirements document:
Nice to have would be the most current blogs from the current month on the news page with a side menu bar that allows you to see blogs organised via month + year ( eg July 2016)
π Post
404 - easy ---> WE MAY NOT NEED IT β¨
π About
π Democracy resources
π Government officials
π§ Government officials/Senators - similar to reps
π Government officials/Representatives
Government officials/Governors - similar to reps. May need to interact with morph API to get the data or add a webhook to download the csv everytime the file changes?
π Places. the links point to the reps and senators pages.
π§ Places/subpages the official site has three subpages more. They are all static pages that render EP data.
π§ Place page
π Events. From the document:
Nice to have would be the most current events from the current month on the events page with a side menu bar that allows you to see events organised via month + year ( eg July 2016)
Nice to have would be a calendar for events.
π Person page
The url adds the house slug, but the official site doesn't have it. We must remove it in the route. Also, check the requirements document and the official site as there are more things than in the Jekyll site. We also need to implement:
π§ summary
π Home
π Elections. From the requirements document:
Desirable: Links to pages in the desirable section on voting information, Past Elections and re-runs.
π§ Elections/subpages - According to the document, seems like they want them listed in a submenu dropdown. They are all static pages edited by them, so will be available on prose.
Other
Map Pombola slugs to person pages
Add coveralls βοΈ
Add metrics
Add rubocop βοΈ
PR to prose to fix filenames saved with a date?
Tables in markdown
Update README and also add relevant badges βοΈ
html validation?
To think about
Summaries: We can save them with the member id as filename, then add an edit button in the person page. Prose gives you a nice url pointing to the edit page of a document. This url could be passed in the person page inside of an edit button that they can click to edit a person summary. If you are not logged in you can edit but not save. We would have to think if there can be any security issues with access although that may be handled by github (access permissions to repos) βοΈ
How to extract a gem from viewer-sinatra shared code. We don't need any of the pages there except maybe the TermTable page, but the PersonCard class seems like it is waiting to be simplified.
Create a rake task that checks out a specific sha of the prose directory before running the tests? or leave our prose directory always at that sha? βοΈ
How to import Struan's governors βοΈ
What could be extracted into a parliament monitoring site gem
Probably only just what's in the lib folder, so avoid having SYE specific stuff entangled with the code there?
Another thought: We could make some kind of generator like the ones you can build with yeoman. then we could put the generator into a gem, and just do something like pm-site-generator new sitename, just as Jekyll provides jekyll new sitename. That would generate a sinatra skeleton with our extra pm stuff. We could still move some of the code inside lib to tiny gems
To-Do list
Legend:
All the time
Data
but it appears under the name βNational Assemblyβ. The National Assembly includes both the House of Representatives and the Senate. (issue to rename it)(PR to rename it). Name changed.Extra modules
featured
field in the summaries frontmatter in prose.ioScripts
Pages
All those "nice-to-have" comments: It's probably better to leave them for when the rest of the site is finished
From the requirements document:
π Post
404 - easy ---> WE MAY NOT NEED IT β¨
π About
π Democracy resources
π Government officials
π§ Government officials/Senators - similar to reps
π Government officials/Representatives
Government officials/Governors - similar to reps. May need to interact with morph API to get the data or add a webhook to download the csv everytime the file changes?
π Places. the links point to the reps and senators pages.
π§ Places/subpages the official site has three subpages more. They are all static pages that render EP data.
π§ Place page
π Events. From the document:
π Person page
The url adds the house slug, but the official site doesn't have it. We must remove it in the route. Also, check the requirements document and the official site as there are more things than in the Jekyll site. We also need to implement:
π Home
π Elections. From the requirements document:
Other
To think about
How to extract a gem from viewer-sinatra shared code. We don't need any of the pages there except maybe the TermTable page, but the PersonCard class seems like it is waiting to be simplified.What could be extracted into a parliament monitoring site gem
Probably only just what's in the lib folder, so avoid having SYE specific stuff entangled with the code there?
Another thought: We could make some kind of generator like the ones you can build with yeoman. then we could put the generator into a gem, and just do something like
pm-site-generator new sitename
, just as Jekyll providesjekyll new sitename
. That would generate a sinatra skeleton with our extra pm stuff. We could still move some of the code insidelib
to tiny gemsThings to maybe implement in the future:
gh-pages
branchThe text was updated successfully, but these errors were encountered: