-
-
Notifications
You must be signed in to change notification settings - Fork 777
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standardize how 'Overview' links open pdf files #2211
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Hi @abdiaz2018, thank you for taking up this issue! Hfla appreciates you :) Do let fellow developers know about your:- You're awesome! P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :) |
Availability: 3 hours |
Developer has added the following comment in the homepage launch issue: #2481 (comment). Thus, I'm closing this issue as completed. |
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:
Action Items
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
The text was updated successfully, but these errors were encountered: