Change Details

== Background We would like to study and explore what the technical requirements for building out dark mode would be. Goals: 1. Create a proof of concept for dark mode which can work across multiple wikis 2. Based on this, create a list of spikes and tickets required to begin building dark mode Per last discussion: # We want this ticket to be completed within a timeframe of 3 days. # To ensure efficient management, let's timebox the task. # It would be beneficial to divide this task into multiple subtasks. # Considering the potential complexities, it might be wise to limit the number of components you will target for prototyping.

== Background We would like to study and explore what the technical requirements for building out dark mode would be. We would like to follow the guidance in the playbook here, in particular the step: in [[ https://docs.google.com/spreadsheets/d/10hEd2iHP-nqc4appkToOzPMDNp7Xy2_ueNu1qzTlFL4/edit#gid=1459779795 | the playbook ]] "Hold an early team shallow dive into the problem space. " Goals: 1. Create a proof of concept for dark mode which can work across multiple wikis 2. Based on this, create a list of spikes and tickets required to begin building dark mode 3. Hold a meeting AND/OR setup a meeting to do an early team shallow dive into the problem space # sign off steps [] Make sure the meeting for team shallow dive has occurred or is in the calendar [] Make sure [[ https://docs.google.com/spreadsheets/d/10hEd2iHP-nqc4appkToOzPMDNp7Xy2_ueNu1qzTlFL4/edit#gid=1459779795 | the playbook ]] is updated with outcomes of the meeting (if the meeting has not occurred move this sign off step to a more appropriate place) Per last discussion: # We want this ticket to be completed within a timeframe of 3 days. # To ensure efficient management, let's timebox the task. # It would be beneficial to divide this task into multiple subtasks. # Considering the potential complexities, it might be wise to limit the number of components you will target for prototyping.

== Background We would like to study and explore what the technical requirements for building out dark mode would be. We would like to follow the guidance in the playbook here, in particular the step: in [[ https://docs.google.com/spreadsheets/d/10hEd2iHP-nqc4appkToOzPMDNp7Xy2_ueNu1qzTlFL4/edit#gid=1459779795 | the playbook ]] "Hold an early team shallow dive into the problem space. " Goals: 1. Create a proof of concept for dark mode which can work across multiple wikis 2. Based on this, create a list of spikes and tickets required to begin building dark mode 3. Hold a meeting AND/OR setup a meeting to do an early team shallow dive into the problem space # sign off steps [] Make sure the meeting for team shallow dive has occurred or is in the calendar [] Make sure [[ https://docs.google.com/spreadsheets/d/10hEd2iHP-nqc4appkToOzPMDNp7Xy2_ueNu1qzTlFL4/edit#gid=1459779795 | the playbook ]] is updated with outcomes of the meeting (if the meeting has not occurred move this sign off step to a more appropriate place) Per last discussion: # We want this ticket to be completed within a timeframe of 3 days. # To ensure efficient management, let's timebox the task. # It would be beneficial to divide this task into multiple subtasks. # Considering the potential complexities, it might be wise to limit the number of components you will target for prototyping.