Update how 'Overview' link opens for Engage

[macho-catt]

Overview

As a user, clicking on the 'Overview' link for the Engage project should open a new tab to the pdf file directly. This is made as an action item of #2211

Details

When clicking the 'Overview' link, each project page acts differently. Some open to a google docs page, others open to a github page that hosts the pdf file, and another downloads the pdf file locally to the machine. There needs to be a standard in how the pdf files open. Developers decided during the backend meeting that pdfs should be opened as a separate tab to the file directly, since modern browsers have the ability to view pdfs.

Example:
How Engage's pdf file currently opens
How it should open

Action Items

• Download a copy of Engage's overview pdf and put it in /assets/pdfs
• Change the 'Overview' link for the markdown file to point to the pdf file living under /assets/pdfs
• Ensure that the links in both the project page and the project's dedicated page open the pdf file properly after the change

Resources/Instructions

Markdown file
Project Page
Location for pdf files
Jekyll Static Files

[BrianCodes33]

Is there a reason why there are two .pdf extensions at the end of the file name? Don't think I've ever seen that. I also changed the markdown fiile, and it's still linking to Github for some reason.

here is the code i edited in md file: url: '../assets/pdfs/Engage-Product-One-Sheet.pdf.pdf'

[BrianCodes33]

Availability for this week: Evenings M-F
ETA: 2-3 Days

[JessicaLucindaCheng]

@BrianCodes33

Is there a reason why there are two .pdf extensions at the end of the file name? Don't think I've ever seen that. I also changed the markdown fiile, and it's still linking to Github for some reason.

here is the code i edited in md file: url: '../assets/pdfs/Engage-Product-One-Sheet.pdf.pdf'

• Good catch! The name of the file should be Engage-Product-One-Sheet.pdf. Once you download the file, you can rename it so it only has one .pdf extension.
• If you make changes to code and don't see it when you use Docker to view the website locally on your computer, run docker-compose down, then clear your cache and delete the file .jekyll-metadata and the directory _site, and then run docker-compose up. You should see changes locally.