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

task: apply the Build with X / Build for X naming convention to Build tab titles

Abierto
  • ¿Algo no está bien?
#2,379 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
markdown
Área
documentation

Línea de trabajo

Read AGENTS.md sections 2, 4, and 6, then inspect the listed Build pages and their titles and sidebarTitle values. Decide which entries count as tools versus platforms and whether the two filenames should change; if renamed, update redirects, navigation, and inbound links. Run mint broken-links --check-redirects; done means the rule is recorded, labels follow it, and the check passes.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

chore priority:low

Follow-up from #2259 / #2368. The Build tab move did not touch page titles; the convention the issue asked for is still open.

What needs to be done?

The issue's convention: "Build with X" for tools and SDKs, "Build for X" for platforms. Titles and nav labels on the Build tab do not follow it consistently:

Page Current title Kind
build/mini-apps/overview Build for MiniPay platform: matches
build/build-with-farcaster Build with Farcaster platform: should be "Build for Farcaster"
build/build-with-self Build with Self tool or protocol: matches
build/build-with-defi Build with DeFi topic: decide
build/build-with-local-stablecoin Build with Local Stablecoins topic: decide
build/build-with-usat Build with USA₮ asset: decide
build/build-on-socialconnect Introduction to SocialConnect no pattern; file name says "on"
build/agents/overview Build with AI on Celo tool: matches, but the group is called "Agents"

Also decide whether the file names (build-with-farcaster, build-on-socialconnect) should change; if they do, each needs a redirect (AGENTS.md section 2) and inbound links updated.

Definition of done
  • A one-line rule recorded in AGENTS.md (section 4 or 6) naming which products count as tools and which as platforms
  • Every title and sidebarTitle in the Build tab follows it
  • Any renamed file has a redirect, an updated nav entry and updated inbound links
  • mint broken-links --check-redirects green
Priority

low

Size

S — hours

Refs #2259.

Lenguaje dominante
MDX
Estrellas
90
Forks
390
Merge medio
2 d 23 h
PR fusionados (30 d)
59

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 celo-org/docs

Todos los issues de celo-org/docs

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.