Skip to content

Add Citizen Engagement Example Page#8355

Merged
daras-cu merged 2 commits intohackforla:gh-pagesfrom
Hiroeme:add-citizen-engagement-example-pg-8202
Oct 4, 2025
Merged

Add Citizen Engagement Example Page#8355
daras-cu merged 2 commits intohackforla:gh-pagesfrom
Hiroeme:add-citizen-engagement-example-pg-8202

Conversation

@Hiroeme
Copy link
Member

@Hiroeme Hiroeme commented Sep 30, 2025

Fixes #8202

What changes did you make?

  • Add copy of program-area-pages-cards.html called program-area-pages-cards-example.html in _includes directory.
  • Add copy of citizen-engagement.html called citizen-engagement-example.html in pages directory.
  • Change citizen-engagement-example.html to include newly copied program-area-pages-cards-example.html content.

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

  • We want to create an example of citizen-engagement.html so that Quality Assurance (QA) can reference the original example page when making changes to the citizen engagement 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

image

  • Accessing localhost:4000/citizen-engagement-example before changes.
Visuals after changes are applied

image

  • Accessing localhost:4000/citizen-engagement-example after changes.

@github-actions
Copy link

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 Hiroeme-add-citizen-engagement-example-pg-8202 gh-pages
git pull https://github.com/Hiroeme/website.git add-citizen-engagement-example-pg-8202

@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 P-Feature: Citizen Engagement https://www.hackforla.org/citizen-engagement size: 0.25pt Can be done in 0.5 to 1.5 hours labels Sep 30, 2025
@caz002 caz002 self-requested a review September 30, 2025 23:02
@caz002
Copy link
Member

caz002 commented Sep 30, 2025

  • Availability: After 7PM on Weekdays
  • ETA: 10/3/25

@santi-jose
Copy link
Member

Availability: 5-8PM Monday - Friday
ETA: 8PM 10/1/2025

@myronchen-git
Copy link
Member

Availability: 12 - 7 PM, Wednesday & Thursday
ETA: 11PM 10/2/2025

Copy link
Member

@myronchen-git myronchen-git left a comment

Choose a reason for hiding this comment

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

Good job on completing this small complexity issue.


Done Correctly

  • The merge from and to branches have been correctly set.
  • The issue has been correctly linked.
  • The pull request title is named properly.
  • The whats and whys in the pull request description is well written.
  • The CodeQL alerts have been correctly checked off.
  • Code changes have been correctly made.
  • In the issue, you've properly checked off action items and gave your availability and ETA.

Other Notes

  • For PRs, Hack for LA's convention is to have no assignees. I don't believe it will affect anything if there is one.

Copy link
Member

@caz002 caz002 left a comment

Choose a reason for hiding this comment

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

Thank you for working on this issue @Hiroeme !

Things Done Well

  • PR description and images accurately describes changes and why they were made
  • Only the files requested by the issue are changed, and website still functions as expected
  • Correct issue is linked
  • PR does not trigger any Code QL alerts and passes pipeline

Changes to Make

None

I approve this pull request.

@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 Oct 1, 2025
@Hiroeme Hiroeme removed their assignment Oct 1, 2025
Copy link
Member

@santi-jose santi-jose left a comment

Choose a reason for hiding this comment

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

Hi @Hiroeme good job working on this issue!

Things Done Well

  • Pull request is done with the correct branch
  • Issue is linked to PR
  • Used descriptive title
  • Made applicable changes requested by the issue
  • Code was changed as requested by the issue
  • Changes preserve the integrity of the website
  • CodeQL Alerts properly checked
  • What & Why sections of PR are answered
  • Included pictures showing the changes affect the website

Changes to Make

  • None

Nice work!

@daras-cu daras-cu merged commit 51b853a into hackforla:gh-pages Oct 4, 2025
11 of 13 checks passed
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: Citizen Engagement https://www.hackforla.org/citizen-engagement 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.25pt Can be done in 0.5 to 1.5 hours

Projects

Development

Successfully merging this pull request may close these issues.

Make a Citizen Engagement Example Page for Future Reference

5 participants