Fill in the empty Platforms section of the README
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
Open the README and find the empty “Platforms” section. Review the existing platform badges and links, then add a short description and a beginner friendly problem link for each listed platform. Done when the section briefly covers LeetCode, Codewars, HackerRank, CheckiO, and GeeksforGeeks in a compact format.
Written by the indexing model from the issue text.
Description
The README has a "Platforms" heading with nothing under it. The badges at the top already link to LeetCode, Codewars, HackerRank, CheckiO, and GeeksforGeeks, but there is no text explaining them.
Time: about 15 minutes
Skills: basic Markdown
What to do
- Write one or two lines per platform: what it is good for and who it suits
- Link to a beginner-friendly problem on each platform
- Keep it short, a small table works well
Only the README needs to change.
Who can take this
Anyone. Beginners, experienced developers, students, and people who do not code. Any language, any level. If you want to help, you are welcome here.
How to contribute
- Comment on this issue so nobody else starts the same thing
- Fork the repo
- Clone your fork and create a branch
- Make your change
- Commit, push, and open a Pull Request
Never opened a pull request before? Start with First Contributions or watch this walkthrough.
Stuck on anything? Ask in the comments. Basic questions are fine.
If this repo helps you or you like where it is going, a star is a nice way to say thanks and helps other people find it. Entirely optional, and you do not need it to contribute.
- Dominant language
- Python
- Stars
- 3
- Forks
- 2
- Avg merge
- 2h 33m
- Merged PRs (30d)
- 6
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 Huerte/algo-solutions-python
-
5-minutes algorithm all-levels any-language beginner-friendly codewars easy good first issue hackerrank hacktoberfest help wanted interview-prep leetcode open-source students
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Huerte/algo-solutions-python#144 · 1 comment ·
-
30-minutes community documentation enhancement good first issue hacktoberfest help wanted
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Huerte/algo-solutions-python#143 ·
-
5-minutes all-levels beginner-friendly codewars documentation good first issue hackerrank hacktoberfest interview-prep leetcode no-code-needed open-source students
Difficulty 2/5 Under an hour Newbie friendliness 68/100
Huerte/algo-solutions-python#140 ·
-
15-minutes 5-minutes algorithm any-language beginner-friendly c cpp csharp easy go good first issue hacktoberfest help wanted java javascript kotlin python rust swift typescript
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Huerte/algo-solutions-python#138 ·
-
30-minutes algorithm all-levels beginner-friendly codewars data-structures documentation dynamic-programming good first issue hackerrank hacktoberfest help wanted interview-prep leetcode no-code-needed open-source students
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Huerte/algo-solutions-python#134 ·
All issues in Huerte/algo-solutions-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ComposioHQ/awesome-claude-skills#2398 ·
Maintainers usually reply within 2 days
-
bug converter
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
grafana/sigma-rule-deployment#435 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
datamodel-code-generator/datamodel-code-generator#5589 ·
Maintainers usually reply within 1 day
-
Shell: serve the home app's Cookie Policy on a hard reloadPossibly taken @2001anshkaushik claimed this today. Openfeature module:ai
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
rocketride-org/rocketride-server#2899 · 1 comment ·
Maintainers usually reply within 2 days
-
GEFSv12
Difficulty 2/5 1-3 hours Newbie friendliness 70/100