Refactor accordion HTML into template tags
Open
Nobody has claimed this yet.
Good First Issue
- Dominant language
- Python
- Stars
- 12
- Forks
- 21
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 5
Description
There's quite a bit of boilerplate HTML needed for the accordion sections on the FAQ and the GARDEN about pages. It might be worth moving all of the repeated accordion-related HTML into a template tag to make the code DRY-er and easier to maintain/modify, and to ensure that the accordion sections are consistent across the site.
Contributor 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.
Research direction
Start by locating the FAQ and GARDEN about pages and comparing their repeated accordion HTML, then inspect how template tags are organized in the project. Done means the shared accordion markup is rendered through one template tag and the sections remain consistent across both pages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend, web-dev
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100