shift-org / shift-org/shift-docs
Evaluate Font Awesome usage
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 25
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
The front end theme uses Font Awesome, but only in a few places. If our usage is minimal and can be replaced with a few custom icons, we could consider dropping it as a dependency.
If we do want to keep it, note that we're using an old, unmaintained version (v4.7.0; see https://fontawesome.com/versions). I'm not aware of anything particularly problematic about using an old icon library, but worth looking at the newer versions to see what they offer.
Contributor guide
No contributing guide indexed for this repository
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 front-end theme's Font Awesome dependency and every place its icons are used. Compare the current v4.7.0 usage with newer versions and assess whether custom icons are practical. Done means a documented decision to remove, upgrade, or retain the dependency, with the affected usage identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100