Add Links to Each Program Area

[nadiaspn0503]

Overview

We need to revise the template that builds the program areas page, so that each program area links to its subpage.

Details

• Program areas titles (e.g., Citizen Engagement) should link to their respective subpages. Currently, these titles are not clickable. Update the following line of code in resource 1.02 so each program area name links to its corresponding subpage.

          <h2 class="title4">{{program_areas.name}}</h2>

• When implementing dynamic linking, note that each program area page URL is derived from its file name (excluding the .md extension). e.g. Citizen Engagement should link to https://www.hackforla.org/program-areas/citizen-engagement [Resource 1.03].

Action Items

• In your IDE, open pages/program-areas.html [Resource 1.02]
• Change the following line from

          <h2 class="title4">{{program_areas.name}}</h2>

to

          <h2 class="title4"><a href="{{program_areas.slug}}">{{program_areas.name}}</a></h2>

• Using Docker, verify changes on the Program Areas page [Resource 1.01]

Resources/Instructions

• 1.01 Program Areas page: https://www.hackforla.org/program-areas
• 1.02 Program Areas code: https://github.com/hackforla/website/blob/gh-pages/pages/program-areas.html
• 1.03 Subpages Links:
  • https://www.hackforla.org/program-areas/civic-tech-infrastructure
  • https://www.hackforla.org/program-areas/diversity-equity-inclusion
  • https://www.hackforla.org/program-areas/environment
  • https://www.hackforla.org/program-areas/justice
  • https://www.hackforla.org/program-areas/social-safety-net
  • https://www.hackforla.org/program-areas/vote-representation
  • https://www.hackforla.org/program-areas/workforce-development
• 1.04 Jekyll Variables (specifically slug): https://jekyllrb.com/docs/variables/

[github-actions]

Hi @nadiaspn0503.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Role

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels