Keep for SHDT discussion

I will summarize the conversation the engineers had about this today and ask Olga about next steps as part of sign off.

Sorry for the delay here. The engineers chatted about this topic in SHDT. Since we're not clear which of these experiments will be a success we took a high level look at what paint points in each experimentation would lead to. These are meant as talking points and all hypothetical:

Sidebar recommendations

• Main issues would relate to layout and we'd likely need to rethink the layout from a design perspective. For example: How does that work with things are collapsed? Does layout need to be changed? Is it another pinned menu? Does pinning scale for yet another use case?
• Would likely need us to consider and potentially address previous concerns with feature management
• Would likely need new Codex components so work with DST or at very least modification to existing components

Empty search

• Mobile and desktop are built differently so we would need to address this issue. We do not want to build this out twice.
• We would likely need to add some hooks to the Codex components to allow us to inject the results.

Summaries

• Generating summaries at scale has various issues that would need to be thought through carefully at a larger scale such as when to generate them, how often to generate them, how to invalidate them, where to store them so much larger at a scale is going to require a lot more consideration and what to do when they are not available.
• We'd need to consult with a DBA and SRE as we'd need to store summaries somewhere.
• Is moderation possible? If so, what does moderation look like? Are summaries stored as a wiki pages or something else? Is this on wiki or a completely new wiki e.g. summaries.wikipedia.org?
• We'd need more guidance around the goal of these summaries. If they are editable are these essentially community notes? If not, what are they.