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

Career functionality v2 scope

Abierto
  • ¿Algo no está bien?
#672 5 comentarios 3 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

@fcoveram ya está trabajando en esto.

Desde el 11/6/2026.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
php
Área
design, web-dev

Línea de trabajo

Comienza revisando los elementos no marcados en las secciones Now, Next y Later, junto con el issue original de career-functionality y los comentarios de testing vinculados. Aquí no se nombran archivos, pruebas ni puntos de entrada; para completar el trabajo es necesario acotar el alcance, resolver las necesidades de diseño y acordar cómo se implementarán los trabajos relacionados con el perfil seleccionado y jobs.wordpress.net.

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

Descripción

[Site] Jobs [Site] Profiles

Building off of the original request to add career functionality, this issue seeks to capture some near time items for a v2 to keep momentum and focus. At a high level, the aim is build out career functionality (find jobs, post jobs, share career moments) within the WordPress.org network in line with this original source of feedback from Matt:

even better, what would it look like if we actually made our profiles as useful and iconic as Githubs, and how can we embed jobs and job-seeking into the product of the main website rather than a side thing. x.com does a really good version of this

I'm going to use the Now/Next/Later approach since there's not a set timeline for this work nor is it tied to any release cycle. Part of what's here is pulled directly from feedback from design that's been given to me (from @marko-srb) and from this dedicated call for testing that's ongoing. I will keep this updated as the work evolves as I work with @bor0 here.

Now

Profiles:

Enhancements:

  • Add dropdown for each job for type of employment: Freelance, Contract, Full-time, and Part-time (feedback source).
  • Add ability to upload CV to automatically fill jobs, accomplishments, etc.
  • Show "Edit and Remove" buttons consistently in the same spot for key accomplishments and editing jobs (feedback source).

Bugs:

Jobs.wordpress.net:

Enhancements:

  • Incorporate badges into candidate section (feedback source)
  • Remove "Open to work" badge as it's redundant (feedback source).
  • Emphasize "how to apply" more when viewing individual jobs (feedback source)
  • Center page content (like FAQ) to be more similar to either centered format pages like Philosophy or Documentation format pages.
  • Add search functionality to both jobs and candidates (reuse search field approach from WordPress showcase for consistency).
  • Remove WordPress logo in header.
  • Swap nav font weight to a thinner variant.
  • Make the green labels smaller for jobs. Right now, they are too prominent.
  • Replace/reuse filtering from WordPress showcase to filter by type of job.
Next

Profiles:

TBD

Jobs.wordpress.net:

  • Add ability to filter candidates by location https://github.com/WordPress/wordpress.org/issues/661 This will need design shaping first.
  • Add ability to filter jobs by location (including remote) and type (part time, full time, contract, etc).
  • Link the company name on single-job view.
  • Budget field normalization. This would be a plugin change, likely requiring folks to select a currency OR a description of the budget field when submitting a job.
  • Polish hero section on homepage. Needs design help.
Later

Profiles:

TBD

Jobs.wordpress.net:

  • Enable a way to have event specific job and candidate interactions. For example, a WCEU focused job fair that can have a dedicated landing page with candidates and employeers who are IRL at an event. Here's a thread with more context.
Lenguaje dominante
PHP
Estrellas
165
Forks
229
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 WordPress/wordpress.org

Todos los issues de WordPress/wordpress.org

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.