creativecommons / creativecommons/search

[Bug] Remove Unused Commented Code to Improve Readability

Open
#295 2 comments 0 reactions 0 assignees View on GitHub
💻 aspect: code 🛠 goal: fix 🟩 priority: low 🧹 status: ticket work required
Dominant language
CSS
Stars
27
Forks
112
PR merge metrics
No merged PRs in 30d

Description

## Description
The current 404.html code for the CC Search Portal contains commented-out sections. Keeping unused code can make the file cluttered.This can make it harder for future developers to read and maintain it.The best practice would be to remove unnecessary code to improve its clarity and maintainability.
## Reproduction

1. Navigate towards the 404.html page in the src folder
2. Locate the commented code

## Expectation
Removing unused commented code will lead to a cleaner codebase and this will improve maintainability and reduce confusion for future contributors.

## Screenshot
![404html1](https://github.com/user-attachments/assets/fad990b9-911d-4961-913c-73312da38ac7)
![404html2](https://github.com/user-attachments/assets/dc2cac40-f3df-4915-a8e1-180e1da5fe48)

## Environment

- Device: (_eg._ iPhone Xs; laptop)
- OS: (_eg._ iOS 13.5; Fedora 32)
- Browser: (_eg._ Safari; Firefox)
- Version: (_eg._ 13; 73)
- Other info: (_eg._ display resolution, ease-of-access settings)

## Additional context
If the commented code is intended for use in the future then it can be documented more clearly .
## Resolution

- [x] I would be interested in resolving this bug.

Contributor guide

Open the contributing guide

Research direction

Open src/404.html and inspect the commented-out sections identified in the issue and screenshots. Confirm which comments are unused, remove only that code, and check that the 404 page remains intact and readable afterward.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
frontend
Issue type
Refactor
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.