Change Details

We will use this ticket to: 1) Define the final state of Topic Containers we intend to deploy in T282639 2) Centralize the requirements that will guide the QA that will precede T282639 //and// 3) Relate/attach the various patches related to Topic Containers we've written to-date.* //*Note: once this initial set of patches is deployed, we'll work on iterative improvements in new tickets.// === Requirements ==== Desktop + Mobile - Namespace(s): **User talk** + **Article talk** //per T304750// ==== Desktop //Meta// - Skin(s): **All** (T306730) //User Experience// - The `== H2 ==` section title should contain affordances that enable people to do the following: -- Subscribe to be notified when other people add new comments to the conversation happening within the boundaries of the section they are viewing (if logged in) -- //Unsubscribe// from being notified when other people add new comments to the conversation happening within the boundaries of the section they are viewing (if logged in) -- Open the source for the specific section/topic they are viewing so they can edit and/or inspect it - Beneath the section title, the following pieces of metadata should appear -- Priority position (left-most in LTR; right-most in RTL): when the latest comment was posted within the topic. --- //Note: people should be able to click the date the last comment was published and be taken to that comment highlighted in context. See: T309751.// -- Middle position: The total number of unique people who have posted a comment within a topic. --- //For now, the # of people count will NOT be interactive. We will revisit this in T309752.// -- Last position: The total number of unique comments that people have posted within the topic ==== Mobile //Meta// - Skin(s): **Minerva Neue** (T306730) //User Experience// - The `== H2 ==` section title should contain affordances that enable people to do the following: -- Subscribe to be notified when other people add new comments to the conversation happening within the boundaries of the section they are viewing (if logged in) -- //Unsubscribe// from being notified when other people add new comments to the conversation happening within the boundaries of the section they are viewing (if logged in) -- Edit a discussion. //Note: the edit button should live inside an overflow menu (e.g. •••) that will appear within the top-right of the Topic Container in LTR languages and in the top-left of the Topic Container in RTL languages.// --- //More context in T308021.// - Beneath the section title, the following pieces of metadata should appear -- When the latest comment was posted within the topic --- //Note: people should be able to click the date the last comment was published and be taken to that comment highlighted in context. See: T309751.// === Designs |Mobile (Minerva Neue)|Desktop (Vector 2022)|Desktop |---|---|--- |//{F35267400}//|//{F35267530}//|//{F35267533}// NOTE: @KieranMcCann to populate the table above with final mocks from the [Talk Page Visual Improvements Figma file](https://www.figma.com/file/DDPwDc8T6b97Vy7uNYyBUp/Talk-Pages-Visual-Improvements-T269950?node-id=3037%3A37007. === Open questions - [ ] 1. Does the design of the mobile Topic Container work well in languages where the "Latest comment" indicator is likely to span multiple lines? //We'll explore this question once the design has been implemented, potentially in a separate ticket.// === Done - [ ] Answers to all `Open questions` are documented - [ ] All `Requirements` are verified as having been implemented as they've been described

We will use this ticket to: 1) Define the final state of Topic Containers we intend to deploy in T282639 2) Centralize the requirements that will guide the QA that will precede T282639 //and// 3) Relate/attach the various patches related to Topic Containers we've written to-date.* //*Note: once this initial set of patches is deployed, we'll work on iterative improvements in new tickets.// === Requirements ==== Desktop + Mobile - Namespace(s): **User talk** + **Article talk** //per T304750// ==== Desktop //Meta// - Skin(s): **All** (T306730) //User Experience// - The `== H2 ==` section title should contain affordances that enable people to do the following: -- Subscribe to be notified when other people add new comments to the conversation happening within the boundaries of the section they are viewing (if logged in) -- //Unsubscribe// from being notified when other people add new comments to the conversation happening within the boundaries of the section they are viewing (if logged in) -- Open the source for the specific section/topic they are viewing so they can edit and/or inspect it - Beneath the section title, the following pieces of metadata should appear -- Priority position (left-most in LTR; right-most in RTL): when the latest comment was posted within the topic. --- //Note: people should be able to click the date the last comment was published and be taken to that comment highlighted in context. See: T309751.// -- Middle position: The total number of unique comments that people have posted within the topic -- Last position: The total number of unique people who have posted a comment within a topic. --- //For now, the # of people count will NOT be interactive. We will revisit this in T309752.// ==== Mobile //Meta// - Skin(s): **Minerva Neue** (T306730) //User Experience// - The `== H2 ==` section title should contain affordances that enable people to do the following: -- Subscribe to be notified when other people add new comments to the conversation happening within the boundaries of the section they are viewing (if logged in) -- //Unsubscribe// from being notified when other people add new comments to the conversation happening within the boundaries of the section they are viewing (if logged in) -- Edit a discussion. //Note: the edit button should live inside an overflow menu (e.g. •••) that will appear within the top-right of the Topic Container in LTR languages and in the top-left of the Topic Container in RTL languages.// --- //More context in T308021.// - Beneath the section title, the following pieces of metadata should appear -- When the latest comment was posted within the topic --- //Note: people should be able to click the date the last comment was published and be taken to that comment highlighted in context. See: T309751.// === Designs |Mobile (Minerva Neue)|Desktop (Vector 2022)|Desktop |---|---|--- |//{F35267400}//|//{F35267530}//|//{F35267533}// NOTE: @KieranMcCann to populate the table above with final mocks from the [Talk Page Visual Improvements Figma file](https://www.figma.com/file/DDPwDc8T6b97Vy7uNYyBUp/Talk-Pages-Visual-Improvements-T269950?node-id=3037%3A37007. === Open questions - [ ] 1. Does the design of the mobile Topic Container work well in languages where the "Latest comment" indicator is likely to span multiple lines? //We'll explore this question once the design has been implemented, potentially in a separate ticket.// === Done - [ ] Answers to all `Open questions` are documented - [ ] All `Requirements` are verified as having been implemented as they've been described

We will use this ticket to: 1) Define the final state of Topic Containers we intend to deploy in T282639 2) Centralize the requirements that will guide the QA that will precede T282639 //and// 3) Relate/attach the various patches related to Topic Containers we've written to-date.* //*Note: once this initial set of patches is deployed, we'll work on iterative improvements in new tickets.// === Requirements ==== Desktop + Mobile - Namespace(s): **User talk** + **Article talk** //per T304750// ==== Desktop //Meta// - Skin(s): **All** (T306730) //User Experience// - The `== H2 ==` section title should contain affordances that enable people to do the following: -- Subscribe to be notified when other people add new comments to the conversation happening within the boundaries of the section they are viewing (if logged in) -- //Unsubscribe// from being notified when other people add new comments to the conversation happening within the boundaries of the section they are viewing (if logged in) -- Open the source for the specific section/topic they are viewing so they can edit and/or inspect it - Beneath the section title, the following pieces of metadata should appear -- Priority position (left-most in LTR; right-most in RTL): when the latest comment was posted within the topic. --- //Note: people should be able to click the date the last comment was published and be taken to that comment highlighted in context. See: T309751.// -- Middle position: The total number of unique comments that people have posted within the topic -- Last position: The total number of unique people who have posted a comment within a topic. --- //For now, the # of people count will NOT be interactive. We will revisit this in T309752.// -- Last position: The total number of unique comments that people have posted within the topic ==== Mobile //Meta// - Skin(s): **Minerva Neue** (T306730) //User Experience// - The `== H2 ==` section title should contain affordances that enable people to do the following: -- Subscribe to be notified when other people add new comments to the conversation happening within the boundaries of the section they are viewing (if logged in) -- //Unsubscribe// from being notified when other people add new comments to the conversation happening within the boundaries of the section they are viewing (if logged in) -- Edit a discussion. //Note: the edit button should live inside an overflow menu (e.g. •••) that will appear within the top-right of the Topic Container in LTR languages and in the top-left of the Topic Container in RTL languages.// --- //More context in T308021.// - Beneath the section title, the following pieces of metadata should appear -- When the latest comment was posted within the topic --- //Note: people should be able to click the date the last comment was published and be taken to that comment highlighted in context. See: T309751.// === Designs |Mobile (Minerva Neue)|Desktop (Vector 2022)|Desktop |---|---|--- |//{F35267400}//|//{F35267530}//|//{F35267533}// NOTE: @KieranMcCann to populate the table above with final mocks from the [Talk Page Visual Improvements Figma file](https://www.figma.com/file/DDPwDc8T6b97Vy7uNYyBUp/Talk-Pages-Visual-Improvements-T269950?node-id=3037%3A37007. === Open questions - [ ] 1. Does the design of the mobile Topic Container work well in languages where the "Latest comment" indicator is likely to span multiple lines? //We'll explore this question once the design has been implemented, potentially in a separate ticket.// === Done - [ ] Answers to all `Open questions` are documented - [ ] All `Requirements` are verified as having been implemented as they've been described