Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Add the URL encoder to the README, the home share card and package.json

Abierto
  • ¿Algo no está bien?
#153 4 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@Abhishek764 ya está trabajando en esto.

Desde el 19/10/2026.

  • #1 de @Abhishek764 — fusionado
  • #167 de @ciperx — cerrado sin fusionar
  • #195 de @Abhishek764 — abierto

Evaluación

Este issue todavía no se ha evaluado.

Descripción

documentation good first issue hacktoberfest

The URL Encoder & Decoder is our fifth tool. Everything that reads the tool registry picked it up, but a few hand-written lists still name only the first four.

Where to look

  • README.md, "Tools" section: the image gallery (lines 43 to 60) and the list under it (lines 62 to 65)
  • .github/assets/: one share image per tool and og-home.png, but no og-url-encoder.png
  • lib/og.tsx, renderHomeOgImage (line 205): the description on the home share card
  • package.json: description (line 5) and keywords
  • CONTRIBUTING.md, "Adding a tool"

What to do

  • Add the URL encoder to the README gallery and list, in the same style as the other four.
  • Save its share image as .github/assets/og-url-encoder.png. Run npm run dev, open http://localhost:3000/url-encoder and look for the og:image tag in the page source. Open that path on localhost and save the PNG. The path has a suffix (something like /url-encoder/opengraph-image-190rzf), and without it you get a 404.
  • Name the URL encoder in the home card's description in lib/og.tsx. There is room for two lines of text there, so check http://localhost:3000/opengraph-image and shorten the sentence if it wraps to a third.
  • Save the new home card over .github/assets/og-home.png (the README shows it at the top).
  • Add it to description and keywords in package.json.
  • Add a step to "Adding a tool" in CONTRIBUTING.md that lists these places, so the next tool doesn't miss them.

Acceptance criteria

  • The README gallery and list show five tools, and the new image loads on GitHub
  • .github/assets/og-url-encoder.png is the tool's own share image, 1200 x 630
  • The home share card names the URL encoder, its description stays on two lines, and og-home.png matches it
  • package.json description and keywords include the URL encoder
  • "Adding a tool" in CONTRIBUTING.md mentions the README, .github/assets/, the home share card and package.json
  • npm run lint && npm run test && npm run build passes

The tool goes live on tools.codercops.com with the next release, so https://tools.codercops.com/url-encoder may still be a 404 when you test the README link.

Want to work on this? Comment below and I'll assign it to you. Please take one issue at a time, branch off develop, and open your PR against develop with Closes #153 in the description.

Lenguaje dominante
TypeScript
Estrellas
1
Forks
9
Merge medio
9 h 50 min
PR fusionados (30 d)
105

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de codercops/toolbelt

Todos los issues de codercops/toolbelt

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.