Dev: Add the Our Locations Information to the About Page

Overview

We need to add the Our Locations information from the events page to the About Us page to highlight that we were an active in person organization that moved to remote meetings.

Details

Since Covid 19 shutdowns are no longer active and the team is no longer doing regular in person meetups. We can modify this information and add it to the About page.

ChatGPT mockup of new About page section

Action Items

Identify the Our Locations section from the events page (resource 1.03).
Create an html file for the Our Locations' section in the _includes/about-page` directory (resource 1.04). Title the file:
```
about-card-our-locations.html
```
Copy the our-locations-content.html file from the _includes/events-page directory (resource 1.05) into the _includes/about-page directory (resource 1.04). Change the name of the file to our-locations-images.html
Within about-card-our-locations.html, use the new text/layout guidance (resource 1.06) to make the new 'Our Locations' section:
- Use the other about-card html files in the about page directory as a guide for the card formatting
- Use the text/layout from resource 1.06 and the mockup under Details above as the content of the card
- The three location images can be included using the our-locations-images.html file, as seen on the Events page (resource 1.03). The include statement will need to be edited to reflect the new file name, from
```
{% include events-page/our-locations-content.html %} 
```
  to
```
{% include about-page/our-locations-images.html %}
```
In pages/about.html (resource 1.07), use an include statement to add the about-card-our-locations.html you created after the about-card-accomplishments.html card
In the sticky-nav element, add a li for the new card. Make sure 'Our Locations' is showing on the sticky menu and is highlighted when you scroll to the card.
Save/commit the changes.
Create a pull request, including screen shots of the new card on the About page.

Instructions for Merge Team

After the PR for this issue is merged, remove the dependency on issue Content Audit: Remove the Our Locations Section from the Events Page #8432
Add a screenshot of the Our Locations section in the About page to Content Audit: Remove the Our Locations Section from the Events Page #8432

Resources/Instructions

1.01 Events page
1.02 About Us page
1.03 Events code
1.04 About Us folder
1.05 Our Locations` images code

1.06 New text and layout:

From In-Person Events to Remote Collaboration

In 2013, Hack for LA began as an in-person civic tech community, hosting events across Los Angeles—including the Westside, Downtown LA, and South LA—bringing volunteers together in shared spaces.

During the COVID-19 pandemic, the organization transitioned to a fully remote operating model, expanding access and enabling broader participation beyond geographic boundaries.

Former in-person event locations across Los Angeles

[ WESTSIDE ] [ DOWNTOWN LA ] [ SOUTH LA ]
(image card) (image card) (image card)

Today, Hack for LA continues to serve Los Angeles as a remote-first organization, supporting a distributed network of contributors.

1.07 About page code

i. Availability: 9/19/26 6:00 PM - 11:00 PM PST
ii. ETA: 9/19/26 11:00 PM PST

For this issue, am I supposed to only add the "raw" html content and not add any of the styling clases (flex classes etc.)?

I wasn't sure if those are going to be smaller issues for other devs to work on later?

In other words, should my feature branch line up exactly with the image in the Issues "Design" drop down?

This is what I currently have: https://github.com/KyleA99/website/tree/add-locations-info-about-page-8431

@daras-cu

@daras-cu @castillios For this issue, my feature branch matches the desktop mockup fairly well. However, the issue did not include any mockup for what the page should look like on mobile. As of now, we don't display any images on mobile. Should I change the mobile behavior of my page to match the mobile drop down behavior as the locations section of the hackforla/events?

Some reviewers on my PR mentioned we may need to correspond with UI/UX. Not sure what the process is for this. We can discuss on tonight's meeting, or if it is preferable, we can converse in a separate meeting? Whatever you all prefer, I can accommodate.

@KyleA99

24. @daras-cu @castillios For this issue, my feature branch matches the desktop mockup fairly well. However, the issue did not include any mockup for what the page should look like on mobile. As of now, we don't display any images on mobile. Should I change the mobile behavior of my page to match the mobile drop down behavior as the locations section of the hackforla/events?
Some reviewers on my PR mentioned we may need to correspond with UI/UX. Not sure what the process is for this. We can discuss on tonight's meeting, or if it is preferable, we can converse in a separate meeting? Whatever you all prefer, I can accommodate.

Spoke to @KyleA99 over DM during 10/13's dev meeting.

This issue did not contain a mobile mockup, so this may call for a separate issue(s). Since the resulting PR has had a lot of back and forth I feel it'd be best to continue with a fresh slate when addressing out of scope issues. In terms of the original issue, I tested its changes locally and I believe Kyle has satisfied the requirements!

Kyle mentioned he would document issues/deficiencies. I advised to leave documentation of this in a comment here, then to ping Danielle on #hfla-site with a link to that documentation's comment. This could serve as a source for additional ERs to be made out of this.

@castillios

23. > 24. @daras-cu @castillios For this issue, my feature branch matches the desktop mockup fairly well. However, the issue did not include any mockup for what the page should look like on mobile. As of now, we don't display any images on mobile. Should I change the mobile behavior of my page to match the mobile drop down behavior as the locations section of the hackforla/events?
> Some reviewers on my PR mentioned we may need to correspond with UI/UX. Not sure what the process is for this. We can discuss on tonight's meeting, or if it is preferable, we can converse in a separate meeting? Whatever you all prefer, I can accommodate.
 Spoke to [@KyleA99](https://github.com/KyleA99) over DM during 10/13's dev meeting.
 This issue did not contain a mobile mockup, so this may call for a separate issue(s). Since the resulting PR has had a lot of back and forth I feel it'd be best to continue with a fresh slate when addressing out of scope issues. In terms of the original issue, I tested its changes locally and I believe Kyle has satisfied the requirements!
 Kyle mentioned he would document issues/deficiencies. I advised to leave documentation of this in a comment here, then to ping Danielle on #hfla-site with a link to that documentation's comment. This could serve as a source for additional ERs to be made out of this.

Hello, as @castillios mentioned above, there is some ambiguity with the issue - no mobile mockup was required so I'm unsure if we should focus on the mobile build for a subsequent issue. Currently, my feature branch aligns fairly closely with the desktop mockup included in Issue #8431. However, the mobile version of my branch does not show the images.

I was thinking we could emulate/follow the other Location-Images behavior in the Events Page. The attached screenshot shows the Events Page's Mobile behavior (there is a drop down to expand that has images). However, it may be a good idea to move that to a separate issue as @castillios mentioned above?

@KyleA99

@KyleA99 @castillios Thanks for bringing this up, I agree the mobile view should be a separate issue. Since the Locations section is already a dropdown I think they can just be visible in the same square format the events page currently uses when the Locations dropdown is open. Kyle let us know if you're able to write an ER for that, you don't have to write any code or instructions just fill in the basic problem and what the format should be on the ER template. Also since I know you've been working on this for a while, let us know about how long you've spent and we can update the issue size if needed. Thanks for sticking with it and being so thorough!

@daras-cu

25. @KyleA99 @castillios Thanks for bringing this up, I agree the mobile view should be a separate issue. Since the Locations section is already a dropdown I think they can just be visible in the same square format the events page currently uses when the Locations dropdown is open. Kyle let us know if you're able to write an ER for that, you don't have to write any code or instructions just fill in the basic problem and what the format should be on the ER template. Also since I know you've been working on this for a while, let us know about how long you've spent and we can update the issue size if needed. Thanks for sticking with it and being so thorough!

@daras-cu thank you! Yes, I will look into writing an ER for the mobile portion of this component. I likely spent ~10 hours in total for this issue/correspondences.

Navigation Menu

Repository navigation

Dev: Add the `Our Locations` Information to the About Page #8431

Overview

Details

Action Items

Instructions for Merge Team

Resources/Instructions

47 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Dev: Add the Our Locations Information to the About Page #8431

Description

Overview

Details

Action Items

Instructions for Merge Team

Resources/Instructions

Activity

github-actions commented on Nov 19, 2025

47 remaining items

HackforLABot commented on Sep 16, 2026

KyleA99 commented on Sep 16, 2026

KyleA99 commented on Sep 21, 2026

KyleA99 commented on Oct 13, 2026

castillios commented on Oct 14, 2026

KyleA99 commented on Oct 14, 2026

daras-cu commented on Oct 14, 2026

KyleA99 commented on Oct 15, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Dev: Add the `Our Locations` Information to the About Page #8431