Replying v1.1: Create mockups
Closed, DuplicatePublic
Actions

Assigned To

None

Authored By

	ppelberg
	Oct 30 2019, 3:17 PM

Description

Rationale

T235592's task description contains the overarching rationale for why this feature is prioritized.

This particular version – v1.1 – is intended to expand basic reply functionality to ensure it satisfies the needs of Senior Contributors to the extent feature can be deployed to all wikis and to encourage "productive" interactions.

User stories

As a contributor I can...

Adjust the size of the text input area
Opt-in/out of watching the talk page before posting my reply
Edit a reply I've posted without having to navigate to a separate view (T242562)
Pre-populate reply with @ mentions of person who authored the comment you are responding to

Details

Platform(s): desktop
Namespaces: all talk namespaces

"Done"

Mockups are created for the entire Replying to a specific comment... workflows for the platforms listed in the "Details" section above.

Text input area: the place where contributors write their comments.

Related Objects
Search...

Status	Assigned	Task
Open	None	T233443 [Epic] Reply Tool
Resolved	ppelberg	T235285 [Design Epic] Mockup workflows for talk page replies
Resolved	ppelberg	T235923 Replies v1.0: release replying to specific comments
Resolved	• iamjessklein	T235592 Replies v1.0: Create mockups
Invalid	None	T242561 Replying v1.1: release to target wikis
Duplicate	None	T236916 Replying v1.1: Create mockups

Event Timeline

@iamjessklein I've updated the task description to include the decisions we arrived at in the OWC/Reply-Versioning.

This task should now be considered the "single source of truth" for what we will end up creating in v1.1.

ppelberg mentioned this in T236918: [Epic] Improvements to talk pages (read mode).Oct 30 2019, 3:23 PM

ppelberg mentioned this in T233443: [Epic] Reply Tool.Oct 31 2019, 6:08 PM

ppelberg updated the task description. (Show Details)Dec 4 2019, 6:50 AM

ppelberg renamed this task from Replies v1.1: Create mockups to Replying v1.1: Create mockups.Jan 12 2020, 11:50 PM

ppelberg added a parent task: T242561: Replying v1.1: release to target wikis .

ppelberg removed a subtask: T242562: Develop a technical approach for editing a specific comment.Jan 12 2020, 11:55 PM

@ppelberg re:requirements

Based on the feedback in T238177, I believe there are a few additional requirements for v1.1 - can you confirm? Here is the complete list:

enable preview boxes to expand
slow down the preview (ellipsis animation)
Customize my edit summary when replying on a talk page
Opt-in/out of watching the talk page before posting my reply
Edit a reply I've posted without having to navigate to a separate view [1]

Additionally, I'm wondering if there are any known gadgets that have conventions for following a conversation? Perhaps @AronManning knows? I'm asking because I believe that the only conventions for following an article or conversation is the star ⭐ icon for watching a page and I'd like to be intentional about creating a new affordance for this.

• iamjessklein added a subscriber: • Demian.Jan 20 2020, 2:50 PM

@iamjessklein, two things:

Per our conversation today, the requirements for v1.1 are now listed in this task's description and
Responses to the requirements posted in T236916#5817118 are below

In T236916#5817118, @iamjessklein wrote:

Based on the feedback in T238177, I believe there are a few additional requirements for v1.1 - can you confirm? Here is the complete list...

enable preview boxes to expand

This is not a requirement for v1.1. In T238177#5813231, I was referring to adding a requirement where the text input area (the place where contributors will write their comments) expands/extends.

Thinking: let's wait to see if the size of the preview becomes an issue before making changes to how it is presented.

slow down the preview (ellipsis animation)

This is not a requirement for v1.1.

Thinking: let's see if the preview is in fact distracting before taking any action. I also wonder if the potential for distraction will be minimized if the preview is below the text input area.