Skip to content

Standardize how 'Overview' links open pdf files #2211

New issue
New issue
Closed
Closed
Standardize how 'Overview' links open pdf files#2211
Assignees
abdiaz2018
Labels
Complexity: SmallTake this type of issues after the successful merge of your second good first issueFeature: InfrastructureFor changes on site technical architectureP-Feature: Project Info and PageA project's detail page (e.g. https://www.hackforla.org/projects/100-automations)epicrole: front endTasks for front end developerssize: 1ptCan be done in 4-6 hoursstatus: UpdatedNo blockers and update is ready for review
Milestone
03.02 Onboarding flow
@macho-catt

Description

@macho-catt
macho-catt
opened on Aug 31, 2021

Dependency

Overview

As a user, clicking on the 'Overview' link for each project page should act the same way. Currently, the 'Overview' links for each project act differently. Clicking the link should open a new tab to the pdf file directly. We will convert each action item into an issue and create a pull request to close the corresponding issue. Then, as a last action item, we will check all overview links appear on the homepage to make sure they are all working the same way.

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 pdf files currently open
How pdf files should open

The process for a developer would involve:

  • Use the newly created directory for pdf files: /assets/pdfs
  • Place a copy of a project's pdf overview file into the /assets/pdfs directory
  • Change the 'Overview' link for a project to point to the pdf file living under /assets/pdfs
  • Ensure that the links in both the home page and the project's dedicated page open the pdf file properly after the change

Action Items

  • Check all overview links that appear on the Projects page to make sure they are all working the same way and opening the pdfs the same way
    • If the overview links do not work the same way nor open the pdfs the same way, let a Merge Team member or Technical Lead know so that they can help you with writing issues to fix the overview links.
    • If the overview links all work the same way and open the pdfs the same way, add a new comment to the homepage launch issue Initiative: homepage launch #2481 stating all the overview links work correctly and adding this link to your comment: Standardize how 'Overview' links open pdf files #2211

Resources/Instructions

How pdf files currently open
How pdf files should open
Project Page
Each individual landing page for affected projects: 100 Automations as an example
Location for pdf files
Jekyll Static Files

Metadata

Metadata

Assignees

Labels

Complexity: SmallTake this type of issues after the successful merge of your second good first issueFeature: InfrastructureFor changes on site technical architectureP-Feature: Project Info and PageA project's detail page (e.g. https://www.hackforla.org/projects/100-automations)epicrole: front endTasks for front end developerssize: 1ptCan be done in 4-6 hoursstatus: UpdatedNo blockers and update is ready for review

Type

No type

Projects

P: HfLA Website: Project Board

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions