## Overview When we transition dark mode to Beta, we will need to provide formal support according to our [feature maturity guidelines](https://docs.gitlab.com/ee/policy/experiment-beta-support.html). We can minimize our support burden by polishing dark mode on high-traffic pages while we're still in Experimental. We will work directly with the designers of these groups to ensure their pages provide a satisfactory dark mode experience. ## Process ### Self-serve See https://gitlab.com/gitlab-org/gitlab/-/issues/516233+ ### For groups directly supported by ~"group::design system" We will work with one stage group at a time. For each group, we will work through the following steps. * Designers in ~"group::design system" will coordinate with product designer and product manager for the target stage group to understand which pages are most important. * Designers in ~"group::design system" will perform initial audit of these pages to understand scope of work. * Designers in ~"group::design system" will collaborate with design and engineering in target stage group to understand changes necessary to bring pages into alignment with dark mode vision. This will primarily be accomplished by ensuring the target stage group is making good use of design tokens and our dark mode design vision. If we find an area where our tokens and design vision don't work, ~"group::design system" will take that feedback into account on our side. * Parties will capture scope of work in a dedicated epic for the target stage group underneath this epic. This will be led by ~"group::design system" UX team members since they will have the best understanding of the work required. * We will prioritize and schedule this work according to our typical processes. Engineers in ~"group::design system" will implement the necessary changes in collaboration with the engineers in the target stage group. * Designers in target stage group will audit output to confirm that the results are satisfactory. ## Why this process? This process will ensure: 1. That we're able to validate our design vision against more areas of the product and iterate as needed 2. That we're able to validate our design token inventory and iterate as needed 3. That we learn what kind of support / documentation teams need so they can start self-serving ## Current stage groups (Oct '24) <details> <summary>Expand</summary> - [x] foundations:import_and_integrate - [ ] foundations:personal_productivity - [x] foundations:design_system - [x] foundations:ux_paper_cuts - [ ] plan:project_management - [ ] plan:product_planning - [x] plan:knowledge - [ ] plan:optimize - [x] create:source_code - [ ] create:code_review - [ ] create:remote_development - [ ] create:editor_extensions - [ ] create:code_creation - [ ] verify:ci_platform - [x] verify:pipeline_execution - [ ] verify:pipeline_authoring - [ ] verify:runner - [ ] verify:hosted_runners - [ ] package:package_registry - [ ] package:container_registry - [ ] secure:static_analysis - [ ] secure:secret_detection - [ ] secure:dynamic_analysis - [ ] secure:composition_analysis - [ ] secure:vulnerability_research - [ ] deploy:environments - [ ] govern:authentication - [ ] govern:authorization - [ ] govern:security_policies - [ ] govern:threat_insights - [ ] govern:compliance - [ ] govern:anti-abuse - [ ] govern:pipeline_security - [ ] monitor:analytics_instrumentation - [ ] monitor:platform_insights - [ ] fulfillment:provision - [ ] fulfillment:utilization - [ ] fulfillment:fulfillment_platform - [ ] fulfillment:subscription_management - [ ] growth:acquisition - [ ] growth:activation - [ ] systems:cloud_connector - [ ] systems:distribution_build - [ ] systems:distribution_deploy - [ ] systems:gitaly_cluster - [ ] systems:gitaly_git - [ ] systems:geo - [x] data_stores:global_search - [ ] data_stores:database - [ ] data_stores:tenant_scale - [ ] platforms:delivery - [ ] platforms:scalability - [ ] platforms:dedicated - [ ] platforms:switchboard - [ ] platforms:pubsec_services - [ ] modelops:mlops - [ ] modelops:dataops - [ ] ai-powered:ai_framework - [ ] ai-powered:duo_chat - [ ] ai-powered:duo_workflow - [ ] ai-powered:ai_model_validation - [ ] ai-powered:custom_models - [ ] mobile:mobile_devops - [ ] engineering_productivity:gdk - [ ] engineering_productivity:engineering_productivity - [ ] unlisted_stage:quality - [ ] unlisted_stage:contributor_success - [ ] unlisted_stage:infrastructure - [ ] unlisted_stage:technical_writing - [ ] unlisted_stage:engineering_analytics </details>