Update how 'Overview' link opens for Civic Tech Structure

[macho-catt]

Overview

As a user, clicking on the 'Overview' link for the Civic Tech Structure 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 Civic Tech Structure's pdf file currently opens
How it should open

Action Items

• Download a copy of Civic Tech Structure'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
• Release dependency on Standardize how 'Overview' links open pdf files #2211

Resources/Instructions

Markdown file
Project Page
Location for pdf files
Jekyll Static Files

[SAUMILDHANKAR]

@riddle015 Request to please add your availability and ETA for completing the issue once you pick up an issue. Thanks.

[JessicaLucindaCheng]

@riddle015 Also, please move this issue into the "In Progress" column since you are actively working on it.

[riddle015]

Progress: Just starting
Blockers: None
Availability: ~7 hours
ETA: 2/6

[github-actions]

@riddle015

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Monday, February 7, 2022 at 11:17 PM PST.}

[github-actions]

@riddle015

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Monday, February 14, 2022 at 11:18 PM PST.}

[SAUMILDHANKAR]

@riddle015 Just wanted to follow up regarding your progress on this issue. Please let us know if you have any questions or need help. Thanks.

[github-actions]

@riddle015

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Wednesday, February 16, 2022 at 5:39 PM PST.}

[github-actions]

@riddle015

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Wednesday, February 16, 2022 at 5:47 PM PST.}

[github-actions]

@riddle015

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Thursday, February 17, 2022 at 2:43 AM PST.}

[riddle015]

Progress: "None"
Blockers: "None"
Availability: "2 hours"
ETA: "2/20/2022"

[github-actions]

@riddle015

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Monday, February 28, 2022 at 11:18 PM PST.}

[github-actions]

@riddle015

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Monday, March 7, 2022 at 11:18 PM PST.}

[SAUMILDHANKAR]

@riddle015: Just wanted to follow up regarding your progress on this issue. Please let us know if you have any questions, need help or if there is any change in your availability. I will leave a slack message as well about the same. Thanks.

[riddle015]

@SAUMILDHANKAR I need help on this issue. I'm having trouble accessing the correct file structure.

Thanks

Hiram

[SAUMILDHANKAR]

@SAUMILDHANKAR I need help on this issue. I'm having trouble accessing the correct file structure.

Thanks

Hiram

@riddle015 Thanks for getting back. Requesting @JessicaLucindaCheng to follow up on this. Thank you.

[JessicaLucindaCheng]

@riddle015

I'm having trouble accessing the correct file structure.

• I assume you already added the pdf to /assets/pdfs. If you mean you are having trouble figuring out how to format the link in markdown, here are a couples examples from the current codebase:

  • website/_projects/100-automations.md

    Lines 52 to 53 in b883cd0

    	- name: Overview
    	url: '../assets/pdfs/100-Automations-Project-One-Sheet.pdf'

  • website/_projects/ballot-nav.md

    Lines 67 to 68 in b883cd0

    	- name: Overview
    	url: '/assets/pdfs/BallotNav-Project-One-Sheet.pdf'

• If the link formatting looks right but you don't see the changes when you use Docker, try the instructions in 2.7.b.i. What if you cannot see your changes locally within Docker? in CONTRIBUTING.md.

• If it is something else, please specify.