Update Project Profile: Spare (Description and Status)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript, jekyll
- Domain
- content
Research direction
Open _projects/spare.md and review its YAML front matter. Replace the description with the wording from the issue and change the status to Closed, preserving the other project fields. Run the local site and check the Spare project page and Projects page; confirm the description and status display correctly and include verification screenshots in the PR.
Written by the indexing model from the issue text.
Description
Overview
We need to update the Spare project profile on the Hack for LA website to reflect its closed status and revised description.
Action Items
- Open
_projects/spare.md. - Review the existing YAML front matter.
- Replace the current
descriptionvalue.
Current description:
A fun new project project that connects people in need of clothing and other essentials with people in the community who have things to spare. It's kind of like one on one Goodwill. The main objective is to foster interactions between the housed and unhoused. The donation is the mechanism for building these connections throughout our community.
New description (copied from #8752):
The Spare project was designed to explore the viability building a software application to connect people in need of clothing and other essentials with community members who have items to give. The software application would have facilitated direct, one-on-one exchanges to foster connections between housed and unhoused community members.
- Change
status: On Holdtostatus: Closed. - Preserve all other project information.
- Verify the updated description and status on the Spare project page in the local development environment.
- Check the Projects page to confirm that Spare is displayed with the correct Closed status.
- Include verification screenshots in the PR.
Resources / Instructions
- Parent Epic: #8752
- Prerequisite issue (closed): #8776
- File:
_projects/spare.md - Source: https://github.com/hackforla/website/blob/gh-pages/_projects/spare.md
- Issue-making reference: https://github.com/hackforla/website/wiki/Update-Project-Profile-Template
Acceptance Criteria
- The Spare description matches the approved wording in #8752.
- The project status is
Closed. - The project information displays correctly in the local development environment.
- No unrelated project fields are modified.
Note for Merge Team
The proposed description is copied verbatim from #8752. Please confirm whether "viability building" should be changed to "viability of building" before implementation.
- Dominant language
- JavaScript
- Stars
- 365
- Forks
- 872
- Avg merge
- 8d 19h
- Merged PRs (30d)
- 2
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hackforla/website
-
Complexity: See issue making label epic good first issue Issue Making: Level 1 P-Feature: Project Info and Page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt time sensitive
Difficulty 1/5 Under an hour Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Complexity: Small ER Feature: Refactor GHA Issue Making: Level 2 ready for merge team role: back end/devOps size: 0.25pt
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
hackforla/website#8871 · 1 comment ·
Maintainers usually reply within 1 day
-
Complexity: Small ER Feature: Refactor GHA Issue Making: Level 2 ready for merge team role: back end/devOps size: 0.25pt
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
hackforla/website#8870 · 1 comment ·
Maintainers usually reply within 1 day
-
Complexity: Small ER Feature: Refactor CSS Issue Making: Level 2 P-Feature: Projects page ready for merge team role: front end size: 0.25pt
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
hackforla/website#8860 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue P-Feature: Project Info and Page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in hackforla/website
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
discovery:other factory-active task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
vercel/ai#25068 · 4 comments ·
Maintainers usually reply within 1 day
-
needs-triage typo
Difficulty 1/5 Under an hour Newbie friendliness 88/100
llm-d-incubation/llm-d-scaling-manager#122 ·
Maintainers usually reply within 1 day
-
create-strapi-app doesn't await writing license.txt, so a failed write skips its error handlingOpenflag: invalid template issue: bug severity: low source: cli status: pending reproduction version: 5
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
strapi/strapi#28637 · 1 comment ·
Maintainers usually reply within 2 days