Update
On 9 February, the Editing Team met to discuss how we will make prototypes available of the various Topic Container design concepts we will be inviting volunteers to experiment with and share feedback about.

In this meeting we came to learn:

• Offering section collapsing on desktop will require some additional investigation/work.
  • Note: @Esanders has a WIP patch here: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/DiscussionTools/+/647717/6; we could also leverage the work that's been done to offer section collapsing on mobile: https://doc.wikimedia.org/MobileFrontend/master/php/classMobileFormatter.html.
• It's possible to offer people the ability to experiment with multiple Topic Container design concepts on a single wiki provided those concepts share common HTML.
  • Note: See task description's ===Open question(s) section.
• Unique patch demo instances need to be created for RTL and LTR languages; however, multiple languages can co-exist on the same patch demo instance

Issues for me:
In the ... dropdown:

• We don't yet have a permalink feature
• I initially read the "Edit" link as being "Edit this comment" (which we don't have).
• If that is the section edit link, there are potentially two on some wikis (edit/edit source)
• I think moving section edit links behind another click is a "big" change which has potential to cause experienced users to not want this feature.

Other issues:

• What does an H2 section which don't contain any comments look like?
• @iamjessklein Can you post static mockups? The GIFs are hard to work from.

Notes: 23 Feb Team Meeting

Below are the actions and questions that emerged during today's team discussion.

Actions

• Editing Engineering to create a patch demo prototype that demonstrates the two Topic Container design variations:
  • 1. All Actions Exposed: this version will expose all section-level actions (Edit, Subscribe, and Copy Link) within the Topic Container rather than having some of these actions stored in an overflow menu.
  • 2. Some Actions in Overflow: this version will expose the Subscribe button within the Topic Container and the (Edit and Copy Link) actions within an overflow menu within the the Topic Container.
  • Notes:
    • Ideally, Editing Engineering can implement the above Topic Container design variations on a single patch demo instance so that volunteers can easily switch between the two.
    • Editing Engineering is going to pause before embarking on implementing functionality that would require "significant" effort (e.g. making section edit links placed within the overflow menu work).
• Editing Engineering + @iamjessklein are going to ensure both prototypes mentioned above accommodate the three potential edit link variations:
  • Variation #1: [ edit ]
  • Variation #2: [ edit source ]
  • Variation #3: [ edit | edit source ]
• Editing Engineering + @iamjessklein are going to ensure the sans serif font used to style the == H2 == text present within Topic Containers works well with the existing sans serif font used to style == H3 == and == H4 == level section headings

Questions

• What – if any – changes will need to be made to the current Topic Container design in order for it to work well on discussion pages that contain some sections that do NOT contain discussions?
  • We will explore this question in T302450.

Here is a screenshot of the Heading hierarchy sizes. It should work quite well as it's comparable to what's happening on article pages. I've added a layer in the figma file now to help with documentation called "Talk Page text styles" to cross reference.

Mobile heading sizes:

Desktop heading sizes:

Editing Engineering + @iamjessklein are going to ensure both prototypes mentioned above accommodate the three potential edit link variations

Here's what @Esanders and I propose:

In T301139#7738202, @iamjessklein wrote:

Here is a screenshot of the Heading hierarchy sizes. It should work quite well as it's comparable to what's happening on article pages.

Nice and +1: the headings you've shown in T301139#7738202 seem to compliment each other nicely.

On Friday, 25 Feb, @iamjessklein met to revisit the changes proposed in T301139#7733531. The outcomes of that discussion are listed below.

25 February Meeting Outcomes

• The DESKTOP version of the Topic Container prototype will NOT include an overflow menu. Instead, Edit and Subscribe) actions will be exposed within the Topic Container. Note: the MOBILE version of the Topic Container prototype will include an overflow menu (•••) which will contain the Edit link.
• We will NOT show Copy link affordances in the MOBILE or DESKTOP versions of the Topic Container prototypes at this time.

8 March Meeting Outcomes

• Work to implement Topic Containers on mobile will happen in a separate task: T303362
• Topic Subscriptions will NOT be fully functionality in these initial Topic Container prototypes (desktop (T301139) and mobile (T303362)).
  • "NOT fully functional" in this context means: the 🔔 Subscribe button will change state when people click/tap on it; HOWEVER people will not be notified when new comments are posted in the section they are subscribed to and the 🔔 Subscribe button will revert to the "unsubscribed" state whenever a talk page is reloaded.

Next Steps

• @iamjessklein: can you please review the latest version of the desktop prototype [i] and comment any edits you think ought to be made to it to before T302120 begins ?
  
  Note: the only thing I saw as needing adjusting was removing section collapsing. I've noted this in the task description's ===Open questions section.

i. https://patchdemo.wmflabs.org/wikis/daa71e218a/w/