Page MenuHomePhabricator

Outreachy 32: Vector 2022 Codex PHP migration
Closed, DeclinedPublic

Description

Project title:
Vector 2022 Codex PHP migration

Brief summary:
Replace Button and Icon components in the Vector 2022 skin with standardized components from the new Codex PHP library.

Expected outcomes:
Button and Icon UI elements (excluding dropdown menus) will be converted from using the current custom-built Php components into standardized PHP-based components provided by the Codex PHP library. This work is not expected to introduce any functional changes. Instead, it aims to improve code quality, reduce technical debt, and lower the long-term maintenance burden of the Vector 2022 skin. Success will not be measured by how many lines of code will be add, but by how many lines will be removed.

As we implement Codex PHP in Vector, enhancements and needed changes will be documented and if small, implemented.

Skills required/preferred:
This work will focus on the MediaWiki skin layer, specifically the Vector 2022 skin. Required skills include the following:

  • PHP - UI elements in Vector 2022 are server-rendered, so the ability to navigate and code PHP is required.
  • HTML/CSS/JS - This project requires replacing UI components, which have HTML CSS and JS functionality associated with them. CSS is written using the Less CSS preprocessor. Javascript is written without a framework, and HTML is currently provided by Mustache templating.
  • Git and Gerrit - The ability to submit git patches through the Gerrit code-review system will be essential for uploading work for code-review.
  • Visual regression testing - Since the changes to this code will be affecting core features of the Vector skin, testing these changes through various means will be essential.

Not required but very helpful:

  • Design systems - This project might require small changes to the Codex Php codebase
  • Accessibility - Web accessibility is important to the skin architecture and implementation of UI elements
  • VueJS - This project might involve minor changes to the CSS or documentation of Codex

Mentors:
@bwang, @Volker_E , @Catrope , Reader Experience team engineers.

Rating:
medium-hard

Microtasks:

Any other additional information for contributors:
Candidates need to be willing to meet with engineers from the Reader Experience team during the course of this project over Google Meet in order to communicate about the project. Most of the Reader Experience team is in the EDT (UTC -4) and CDT (UTC -5) timezones, so the ability to communicate during those working hours is preferred.

What WMF priority does this project align with?
Web Readers Experience Essential Work

Why are you proposing it?

The purpose of this project is to clean up old code and migrate UI components to a new library. Since there is no end-user impact of this change, it's unlikely to get prioritized on our project roadmap, but it has clear maintenance benefits. This work is somewhat experimental as well since the Codex PHP library is new, and this is a good opportunity to validate the library in a real-world setting.

What is the expected impact? What does success look like? How will this affect the needs you have identified?

  • Reduced technical debt in the Vector 2022 skin
  • Improved consistency with the Codex design system
  • Validation and enhancements to Codex PHP in a real-world MediaWiki skin environment
  • Preparing for Codex Php menu enhancements

Event Timeline

Thanks @bwang for your submission! Please be sure to add your microtasks asap as we cannot accept the project without these.

Hi @bwang, @Volker_E , @Catrope - reminder that submissions close tomorrow and we need your microtasks in order to accept this project. Thanks!

Hi @bwang, @Volker_E , @Catrope - reminder that submissions close tomorrow and we need your microtasks in order to accept this project. Thanks!

Sorry for the delay! Bernard and I met this morning and I just filed and added a list of microtasks.

Hi, my name is Dior.
I'm an Outreachy applicant and I'm looking forward to contributing.
I'm having trouble joining the slack chat using the link from the projects detailed information page. The login screen gives an options to sign in with Okta or use a guest account.
My wikimedia credentials did not work here.
Is there a step that I'm missing?

Hello , my name is Kosi and I'm an Outreachy applicant interested in the "Vector 2022 Codex PHP Migration" project.

I tried joining the Slack workspace using the provided link, but I'm encountering issues with the Okta/guest login process. I attempted to use my existing Wikimedia account credentials but couldn't log in. Would it be possible to receive an email invitation to the Slack workspace? If so, should I provide my email address here, or will it be sent to the email associated with my Wikimedia account?

Hiiieee,
I'm Eileen Blessing and I'm interested in the Vector 2022 Codex PHP migration project. I have some experience with PHP, HTML, CSS and JavaScript and I am excited to start contributing.

Hello , my name is Goodness and I'm an Outreachy applicant interested in the "Vector 2022 Codex PHP Migration" project.
Please i am finding it difficult to join the slack ...

I tried joining the Slack workspace using the provided link

Please i am finding it difficult to join the slack ...

On which page (full URL) to see some provided Slack link?

Hi everyone my Name is Living Enaanasebh i am so happy to be contributing to this project. please how can i join the slack channel.

My question was: On which page (full URL) to see some provided Slack link? I did not ask for a Slack link.

@Aklapper
I found the Slack link on the Outreachy page for the Vector 2022 Codex PHP migration project.

My question was: On which page (full URL) to see some provided Slack link? I did not ask for a Slack link.

https://www.outreachy.org/outreachy-may-2026-internship-cohort/communities/wikimedia/#vector-2022-codex-php-migration

here is the link to the page, ypu will find the link to the slack chaannel under the "How do I work with the Wikimedia Foundation community?" heading

@Aklapper
I found the Slack link on the Outreachy page for the Vector 2022 Codex PHP migration project.

My problem is I can't seem to login. Where can I open a guest or Okta account

Has any outreachy applicant been able to login to their slack channel? That's the information I am looking for

This comment was removed by Vanny.

Hello, my name is Aderonke, and I’m an Outreachy applicant interested in the “Vector 2022 Codex PHP Migration” project.

I attempted to join the Slack workspace using the provided link but encountered issues with the Okta/guest login process. I also tried using my existing Wikimedia account credentials without success. Could I please receive an email invitation to access the workspace? Kindly let me know if I should share my email address here or if it will be sent to the one linked to my Wikimedia account.

Thank you.

Hello everyone, I'm Ajim.
I've also been having difficulties joining the slack channel, and I see it's a general issue.
However, I think we can start working on the mircro projects in the meantime.

We know by now that joining Slack does not work. No repeated comments needed. Thanks.

@Aklapper
Are there still tasks to work on? I see most of them have already been assigned

I'm not sure why you're asking me. :)

Hi, I'm an Outreachy applicant for May 2026. I can see most of the listed microtasks are already assigned or have patches submitted. Are there additional tasks available for applicants to contribute to?"

@bwang @Volker_E

Hi all - re: the Slack channel, this is currently private. If you are selected for this project, the mentors will invite you into the Slack instance at that time. In the meantime you contact the mentors via Phabricator.

@Volker_E Hi Good evening i wanted to know if outreachy applicants can work on something other than the microtask because i noticed there has been a lot of duplicate solutions to each task

Good Morning Hi everyone my Name is Amarachi Ordor i am so happy to be contributing to this project

Good Morning Hi everyone my Name is Amarachi Ordor i am so happy to be contributing to this project

Hi Amara hi welcome.

Thanks to all the candidates who showed an interest in this project. Unfortunately, due to changing circumstances, the mentor team is no longer able to move forward with this project proposal. We appreciate all the work that’s been put into this already, and wish all the candidates the best in your future work.