OpenSourceOrg / OpenSourceOrg/dotOrg
Update Slug for Alumni Board members
Nessuno ha ancora preso questa issue.
- Lingua principale
- PHP
- Stelle
- 12
- Fork
- 6
- Merge medio
- 13h 26m
- PR unite (30g)
- 12
Descrizione
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.
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:
- Board Member CPT:
(Correct) Board members: https://opensource.org/board-member/chris-aniszczyk
Status: https://opensource.org/blog/status/alumni
Seat type: https://opensource.org/blog/seat-type/affiliate - License CPT:
(Correct) License: https://opensource.org/license/blue-oak-model-license
License Steward: https://opensource.org/blog/steward/apache-software-foundation
Category: https://opensource.org/blog/license-category/international - Press Mentions CPT:
(Correct) Press mentions: https://opensource.org/press-mentions/meta-is-accused-of-bullying-the-open-source-community
Publications: https://opensource.org/blog/publication/adda-24-7
The /blog slug should only apply to blog post types.
A few related PRs:
- Blog post migration: https://github.com/OpenSourceOrg/dotOrg/pull/56
- “removing blog path from author page: https://github.com/OpenSourceOrg/dotOrg/pull/58
- Omitting /blog/ from CPTs: https://github.com/OpenSourceOrg/dotOrg/pull/59
Related: https://github.com/OpenSourceOrg/dotOrg/pull/61
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Esamina prima le PR correlate 56, 58, 59 e 61, quindi verifica il comportamento degli URL dei CPT Board Member, License e Press Mentions. Convalida le modifiche sul sito di staging: alumni dovrebbe avere una pagina /about/alumni e un reindirizzamento, mentre gli URL dei CPT e delle tassonomie non dovrebbero usare /blog. Conferma gli URL rivolti ai partner prima del merge in produzione.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- php, wordpress
- Ambito
- backend, content
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 25/100