Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Build a simple static website to browse the solutions

Open
  • Is something wrong?
#127 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
css, html, javascript
Domain
frontend, web-dev

Research direction

Start by inspecting the repository’s solution folders and index, then choose whether the site should read a generated JSON file or the index file. Build a static page that lists each solution’s problem name, language, and file link, with language filtering and text search, and verify it works on GitHub Pages without a build step.

Written by the indexing model from the issue text.

Description

1-hour all-levels codewars css enhancement hackerrank hacktoberfest hard help wanted html interview-prep javascript leetcode open-source students website

A small GitHub Pages site could let people search and filter solutions by language and topic instead of digging through folders.

Time: a few hours, can be split across contributors
Skills: HTML, CSS, JavaScript

Rough idea
  • A page that lists solutions with problem name, language, and a link to the file
  • A language filter and a text search
  • Works without a build step so GitHub Pages can serve it directly
  • Reads from a generated JSON or from the index file

Comment with your plan before starting so the work does not get duplicated. Partial contributions (just the layout, just the data script) are welcome.

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

  1. Comment on this issue so nobody else starts the same thing
  2. Fork the repo
  3. Clone your fork and create a branch
  4. Make your change
  5. 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Huerte/algo-solutions-python

All issues in Huerte/algo-solutions-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.