NOTE: This should only be attempted at times when the schema is not being used for anything to avoid disruption.
== Background
Currently, we have specific conditions in WikimediaEvents for the Vector 2022 and Minerva skins, which leads to less efficient code and potential issues in the future. The goal is to create a mechanism so all skins can have the same string that can be queried for the current event's font-size preference.
Currently mobile logs the following values: xlarge, large, small, regular
Desktop logs: 0, 1,2, 3
== User story
As a data analyst I want consistent values across the mobile and desktop schemas for font-size
Requirement
Standardize font-size values logged by WikimediaEvents across mobile (Minerva) and desktop (Vector) skins. The mobile schema will align with the desktop values to ensure consistency in the instrumentation of font size preferences. No changes will be made to the Vector skin itself, and only WikimediaEvents will be updated to log uniform values for both mobile and desktop.
BDD
```
Feature: Standardize Font Size Values in WikimediaEvents Across Skins
Scenario: Log consistent font-size values in WikimediaEvents for Minerva and Vector skins
Given the user adjusts the font size in Minerva or Vector skin
When the font size is logged in WikimediaEvents
Then the mobile schema should log the values as shown below
| Skin | Text | Logged Value |
| Minerva | Standard | 1 |
| Minerva | Medium | 2 |
| Minerva | Large | 3 |
| Vector | Small | 0 |
| Vector | Standard | 1 |
| Vector | Large | 2 |
```
Test Steps
Test Case 1: Verify Standardized Font Size Logging in WikimediaEvents
1. Adjust the font size in the Minerva skin.
2. **AC1:** Confirm that font size adjustments in Minerva are logged as 1, 2, or 3 in WikimediaEvents.
3. Adjust the font size in the Vector skin.
4. **AC2:** Confirm that font size adjustments in Vector are logged as 0, 1, or 2 in WikimediaEvents.
== Design
- Add mockups and design requirements
== Acceptance criteria
- Add acceptance criteria
== Communication criteria - does this need an announcement or discussion?
N/A
== Rollback plan
N/A. We are not actively using the schema right now.
//This task was created by Version 1.2.0 of the [[ https://mediawiki.org/w/index.php?title=Reading/Web/Request_process | Web team task template ]] using [[ https://phabulous.toolforge.org/ | phabulous ]] //
Proposed Solution: