Potential new mini project | BEP website

[iteles]

Having built the BEP app, CU are looking to build a static website to promote it or have as a gateway into the application.

The budget for this is tiny so we will be looking to reuse as much of the work we did for the Quodl website as possible.

Tasks

• [x] Initial call
• [x] Follow up summary of potential agreement
• [x] Agreement on scope
• [x] Estimate budget
• [x] Send through budgets
• [x] Discuss project with dwylers and determine interest/availability
• [x] Agree timelines
• [x] Send contracts to dwylers

[iteles]

Proposed starting point for scope sent, awaiting reply.

[iteles]

Current scope for estimating, based on Quodl site @Cleop @RobStallion @parkhabit:

• Homepage
  • Similar sections to Quodl but replace the section with the Quodl badges with a video demo of the product in action or some text with screenshots - 2hrs
  • Remove blog section at the bottom - 25min
  • Quotes from people who have said how good the app is - new functionality - (estimate created in mind of this being just on the homepage) - 2hrs with customisable reviews
  • The above plus the ability for these to rotate using a bank of reviews, but this should be estimated as an extra - 4hrs (hard coded reviews not customisable on apostrophe) (Ability to make it customisable dependent on designs and would require spike)
  • Something on importance of evidence-based practice and how app fits, possibly in an existing section - 1hr
• About - keep this page and ensure content is updated - 1hr (to change the button link and copy... subject to change with designs)
• New Page - Something on how to appraise papers: validity, results, relevance - Awaiting designs
• New Page - Page with embedded graphics from redash (can be just screenshots that PO -updates through CMS at a push but ideally not) - Awaiting designs. Using an updated version fed from Redash would be longer and require research into Redash API and how to achieve this.
• Pricing - we maintain this layout as is and just update the content to reflect BE - 1hr
• Replace blog page with 'Latest Publications' (exact name of page TBC)
  • We either:
  • Keep the blog 'format' where the 'Latest Publications' page has a little box for each of the publications/studies etc (like http://quodl-site.herokuapp.com/blog) and then the visitor clicks into the titles of the ones they want to know more about (I would recommend this). - 4hrs
  • Create something more akin to the 'About' page, but I think this could get a bit too long - other layouts can be explored - dependent on more info
  • Search will need to be added functionality to this page - 1 day plus 2hr spike (need to determine exact functionality of the search and need to see if Apostrophe has a module for searching)
• How to use BE - this is a new page, following the contents of the PDF guide Amanda sent through - dependent on styling 4hrs
  • Format would be similar to the Quodl About page
• New page - Examples of questions and successful use of app with people able to submit own examples to us -
  • Examples of successful use are longer stories with a clinical background, detailed search, explanation of why a a particular paper was selected, how it resolved an uncertainty and different to the testimonials on the homepage - estimate based on a page containing free text and some images (1 page for multiple case studies) with a contact form at the bottom where people could add their own examples (estimate subject to designs) - 4hrs
• Contact - Same as the current one: http://quodl-site.herokuapp.com/contact - 25mins subject to styling

Set up time: 1 day (set up S3, new DB, deploy to heroku, fork the repo, remove tag manager) Make the contact form emailable: 1 day see: https://github.com/cul-2016/site/issues/42

Total: 4days 3hrs (plus bug fixing/documentation time and awaiting designs) Plus: 2days 4hrs for separate issue

For separate estimate:

Something about planned developments with opportunity for people to rank their importance (E.g. Vote up our down) and send further suggestions - this would be new functionality entirely - 4hr spike needed and estimate dependent on the spike but potentially 2 days.

[iteles]

Thanks @Cleop @RobStallion and @parkhabit for estimating!

Sent to CU 👍

[iteles]

Confirmed! @parkhabit will be starting on this today, with @RobStallion joining her tomorrow 🎉

Assigning to @rub1e for contracts.