TheAlgorithms / TheAlgorithms/website
Add difficulty levels & views for each problem
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 220
- PR merge metrics
- No merged PRs in 30d
Description
Description of the feature request
There are a ton of algorithms present on https://the-algorithms.com, but I feel that they aren't presented as well. Don't get me wrong, the site is well made, however I think adding difficulty levels to the algorithms and showing the number of people that have viewed it would add 2 new filters for people to search with and find good algorithms and make it easier to categorize.
I know this site is just for educational purposes only and mostly meant to be used as a tool to find the solution which you need for your problems, however I think that it could also be extended to cater to the people who just want to browse through some algorithms in general, and maybe learn something new. People would be able to compare themselves and their knowledge to others, and improve as a whole, learning from each other. At the present, the site's elegant and highly functional, but it cannot cater to those groups of people as well. Because when you go to, let's say, problems under Math category, I don't exactly find anything new to learn from there (because I only see the names most of the time), neither do I know the level of the stuff in there. Some problems, like Fibonacci ones, are comparatively easy to stuff like Riemann Integration, etc.
The reason I'm also advocating for the addition of views is that, it could also allow people to know about popular topics, which are important to know for everyone. Like some stuff isn't always used by everyone, and can be very niche. Not everyone should be spending their time ignoring other well known topics which are useful to them and spending time to those niche algorithms. So it would help people to basically improve their strengths, rather than being jack of all trades. However I believe views may not be a good factor all the time, since the niche algorithms might get overshadowed. But that's up for debate.
Add screenshots of the feature request (optional)
No response
Add any other context about the feature request here
No response
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
The issue does not name any files, tests, or entry points. Start by reviewing the existing problem browsing and category views, then clarify how difficulty levels and view counts should be defined, stored, displayed, and filtered before implementation. Done should include an agreed design and working filters and views.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100