Skip to content

Added link to the program area title in the Program Area page template#8664

Open
egcuriel wants to merge 1 commit into
hackforla:gh-pagesfrom
egcuriel:egcuriel/8487-add-links-program-areas
Open

Added link to the program area title in the Program Area page template#8664
egcuriel wants to merge 1 commit into
hackforla:gh-pagesfrom
egcuriel:egcuriel/8487-add-links-program-areas

Conversation

@egcuriel
Copy link
Copy Markdown
Member

@egcuriel egcuriel commented May 28, 2026

Fixes #8487

What changes did you make?

  • Revised the template that builds the Program Areas page
  • Made the title of each Program Area clickable so that it links to its its respective subpage

Why did you make the changes (we will use this info to test)?

  • To create links between each of the program area subpages and the Program Areas page
  • The subpages contain the details for each of the products referenced under each program area in the Program Areas page

CodeQL Alerts

After the PR has been submitted and the resulting GitHub actions/checks have been completed, developers should check the PR for CodeQL alert annotations.

Check the PR's comments. If present on your PR, the CodeQL alert looks similar as shown

Screenshot 2024-10-28 154514

Please let us know that you have checked for CodeQL alerts. Please do not dismiss alerts.

  • I have checked this PR for CodeQL alerts and none were found.
  • I found CodeQL alert(s), and (select one):
    • I have resolved the CodeQL alert(s) as noted
    • I believe the CodeQL alert(s) is a false positive (Merge Team will evaluate)
    • I have followed the Instructions below, but I am still stuck (Merge Team will evaluate)
Instructions for resolving CodeQL alerts

If CodeQL alert/annotations appear, refer to How to Resolve CodeQL alerts.

In general, CodeQL alerts should be resolved prior to PR reviews and merging

Screenshots of Proposed Changes To The Website (if any, please do not include screenshots of code changes)

Visuals before changes are applied
Desktop
Mobile
Visuals after changes are applied
Desktop
Mobile

@github-actions
Copy link
Copy Markdown

Want to review this pull request? Take a look at this documentation for a step by step guide!


From your project repository, check out a new branch and test the changes.

git checkout -b egcuriel-egcuriel/8487-add-links-program-areas gh-pages
git pull https://github.com/egcuriel/website.git egcuriel/8487-add-links-program-areas

@github-actions github-actions Bot added role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers P-Feature: Program Area https://www.hackforla.org/program-areas Complexity: Small Take this type of issues after the successful merge of your second good first issue size: 0.5pt Can be done in 3 hours or less labels May 28, 2026
@egcuriel egcuriel changed the title Added links each program area title to their respective subpages Added links to the program area titles in the Program Area page May 28, 2026
@egcuriel egcuriel changed the title Added links to the program area titles in the Program Area page Added link to the program area title in the Program Area page template May 28, 2026
@castillios castillios self-requested a review May 28, 2026 04:06
@castillios
Copy link
Copy Markdown
Member

Review ETA: Thurs 5/27 by EOD
Availability: Thursday before 7PM, Friday before 8PM, Saturday all day

@Tomlu60220244
Copy link
Copy Markdown
Member

ETA: 5/29 by EOD
Availability: evenings in these two days.

@sushma110396
Copy link
Copy Markdown
Member

ETA: 05/28/2026
Availability: Weekdays after 6PM PST

Copy link
Copy Markdown
Member

@sushma110396 sushma110396 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change looks good! I have verified it locally. All the required steps have been followed:

  • There is a linked issue
  • Screenshots of visual changes look good
  • Branch name is correct

PR approved.

Copy link
Copy Markdown
Member

@castillios castillios left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @egcuriel! I ran your changes locally and each of the program titles are linked correctly! As for the code changes, they are clean and organized with the indentation you've added.

PR and Issue Logistics

  • Issue has been correctly linked and branch has been correctly set
  • CodeQL alerts checked off
  • In original issue, action items checked off, project status correctly set, and availability is shared
  • Screenshots of visual changes shared for desktop & mobile provided

Great work on the PR! I've approved your changes.

@github-project-automation github-project-automation Bot moved this from PR Needs review to PRs ✅ waiting for merge team in P: HfLA Website: Project Board May 28, 2026
Copy link
Copy Markdown
Member

@Tomlu60220244 Tomlu60220244 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything looks good! I checked out the PR locally and tested the Program Areas page.

What was done well:

  • The branch name and target branch look correct.
  • The Program Area titles are now clickable and link to their respective subpages.
  • I tested multiple Program Area title links locally, including Environment, and they routed correctly under /program-areas without a 404.

Nice work! This PR looks good to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Complexity: Small Take this type of issues after the successful merge of your second good first issue P-Feature: Program Area https://www.hackforla.org/program-areas role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less

Projects

Status: PRs ✅ waiting for merge team

Development

Successfully merging this pull request may close these issues.

Add Links to Each Program Area

4 participants