OpenSourceOrg / OpenSourceOrg/dotOrg

Update Slug for Alumni Board members

Open
#115 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
12
Forks
6
Avg merge
13h 26m
Merged PRs (30d)
12

Description

Description

Partner noticed the slug for the Alumni shows https://opensource.org/blog/status/alumni and would like to update to https://opensource.org/about/board-of-directors/alumni or https://opensource.org/about/alumni.

The changes should be made on the staging site for partners review before merging to production.

https://opensource.org/about/alumni

We can use the /about/alumni URL path to add the Alumni Board members and create a link on the About page as well

Once that is done, we can create a redirect from https://opensource.org/blog/status/alumni to https://opensource.org/about/alumni.

Note: The partner also noticed https://opensource.org/status/alumni was gone and instead it found it at https://opensource.org/blog/status/alumni and wants to know why that happened.

In addition:

CPTs and their taxonomies should not use /blog slugs in their URLs. Here’s a list of all CPTs which highlights where the issue is:

The /blog slug should only apply to blog post types.

A few related PRs:

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Review related PRs 56, 58, 59, and 61 first, then inspect the Board Member, License, and Press Mentions CPT URL behavior. Validate the changes on the staging site: alumni should have an /about/alumni page and redirect, while CPT and taxonomy URLs should not use /blog. Confirm the partner-facing URLs before production merge.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
backend, content
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.