Repository navigation
Open
Labels
Complexity: LargeEREmergent RequestEmergent RequestIssue Making: Level 2Make issue(s) from an ER or EpicMake issue(s) from an ER or EpicP-Feature: Projects pagehttps://www.hackforla.org/projects/https://www.hackforla.org/projects/P-Feature: Toolkithttps://www.hackforla.org/toolkit/https://www.hackforla.org/toolkit/p-feature: Projects-checkWe use this page to check to make sure that teams are using the Technology section correctlyWe use this page to check to make sure that teams are using the Technology section correctlyready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritizationneeds a senior review either to do some re writing or to approve it for ready for prioritizationrole: front endTasks for front end developersTasks for front end developerssize: 0.5ptCan be done in 3 hours or lessCan be done in 3 hours or less
Description
Emergent Requirement - Problem
We need to update the styling for the Projects page layout to prevent the Filters column from shifting inward when no results are returned.
Currently, the Toolkits page contains the correct behavior. We can resolve this by refactoring the styling rule in the Toolkits SCSS, and moving that rule into a shared file so that the fix applies for both Projects and Toolkits pages at once.
How to replicate
- Navigate to the Hack for LA Projects page
- Select filters that return zero results:
a. Under "Program Areas" select "Citizen Engagement" and "Civic Tech Infrastructure" (link to selected filters) - Observe the layout shift, the Filters column should shift right. This is unexpected behavior.
- Note the expected behavior in the Toolkits page when no results return
Screenshots of bug & expected behavior
Issue you discovered this emergent requirement in
Date discovered
10-8-2026
Did you have to do something temporarily
- YES
- NO
Who was involved
What happens if this is not addressed
If this is not addressed, it may disrupt the overall user experience of the Projects page. We also want to migrate any SCSS rules into a single shared rule to reduce any redundant code.
Resources
Hack for LA Projects Page: https://www.hackforla.org/projects/
Recommended Action Items
- Make a new issue
- Discuss with team
- Let a Team Lead know
Potential solutions [draft]
- Create a medium issue that addresses & implements a fix for the UI bug using a Blank Issue Template. Title the issue to briefly capture the scope of the problem.
- At the top of the issue above the
Overviewsection, add the followingPrerequisitesection:### Prerequisite 1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our [Getting Started page](https://www.hackforla.org/getting-started) and attend an onboarding session. 2. Before you claim or start working on an issue, please make sure you have read our [How to Contribute to Hack for LA Guide](https://github.com/hackforla/website/blob/7f0c132c96f71230b8935759e1f8711ccb340c0f/CONTRIBUTING.md). - Under Action Items section, create checklist items that address the following changes. Feel free to change the wording of the following and group them in the issue as you see fit.
- In
_sass/components/_toolkit.scss, remove the.toolkit-content-filter-containerclass - Navigate to
_sass/elements/_dropdown_filters.scss, and reuse.toolkit-content-filter-containeras a generic.filter-containerclass above the existing.filter-toolbarclass:.filter-container { flex: 0 1 392px; } - In
_sass/components/_projects-page.scssfind the.projectsclass and adddisplay: flexandalign-items: flex-start:.projects { background: $color-pink; padding: 32px 16px; display: flex; align-items: flex-start; } - In the same file, define the
.projects-and-filtersclass above the.search-tip-linkclass. This will allow the project cards container to maintain its width and prevent filter column shifting. (Note:.projects-and-filtersalready exists in HTML but it has not yet been defined in any SCSS file):.projects-and-filters { flex: 1 1 auto; width: 100%; max-width: 800px; } - In
_includes/current-guides.html, replace the.toolkit-content-filter-containerclass, changing it from:to:<section class="toolkit-content-container filter-content-container content-section"> <div class="toolkit-content-filter-container"> <nav class="filter-toolbar toolkit-filters" aria-label="Filter Navbar"> <div class="filtersDiv filtersDiv-background"> <h3 class="filters-title"><section class="toolkit-content-container filter-content-container content-section"> <div class="filter-container"> <nav class="filter-toolbar toolkit-filters" aria-label="Filter Navbar"> <div class="filtersDiv filtersDiv-background"> <h3 class="filters-title"> - In
_includes/current-projects.html, locate<nav class="filter-toolbar" aria-label="Filter Navbar">near the top of the file:<section class="content-section projects filter-content-container"> <nav class="filter-toolbar" aria-label="Filter Navbar"> - Then implement the fix by nesting the entire
navtag with a filter container div,<div class="filter-container">:<section class="content-section projects filter-content-container"> <div class="filter-container"> <nav class="filter-toolbar" aria-label="Filter Navbar"> - Ensure proper indentation and closing tags. The
.filter-containerdiv should be siblings with the.projects-and-filtersdiv:... </nav> </div> <!-- Projects and Filters container --> <div class="projects-and-filters"> - In your local environment, verify the layout shift bugs no longer occur & the refactor works on the following pages: Toolkits, Projects, Projects-Check
- In
Metadata
Metadata
Assignees
Labels
Complexity: LargeEREmergent RequestEmergent RequestIssue Making: Level 2Make issue(s) from an ER or EpicMake issue(s) from an ER or EpicP-Feature: Projects pagehttps://www.hackforla.org/projects/https://www.hackforla.org/projects/P-Feature: Toolkithttps://www.hackforla.org/toolkit/https://www.hackforla.org/toolkit/p-feature: Projects-checkWe use this page to check to make sure that teams are using the Technology section correctlyWe use this page to check to make sure that teams are using the Technology section correctlyready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritizationneeds a senior review either to do some re writing or to approve it for ready for prioritizationrole: front endTasks for front end developersTasks for front end developerssize: 0.5ptCan be done in 3 hours or lessCan be done in 3 hours or less
Type
Projects
- StatusShow more project fieldsNew Issue Approval


Activity
castillios commentedon Nov 10, 2026
Please let me know if I should alter the proposed solution, thanks!