I agree.

After conversation with Connie we know that to be able to track comments and votes on wishes and focus areas are hard to track in our case. The best way we can do it is to add specific edit tags for these events. e.g add edit tag "focus-area-voting" to edits that add {{Support}} template to focus area talk pages; and add edit tag "wish-comments" on edits that comment on wish pages

Open question:

Just taking some notes here on the ones I know of, so we can continue discussing and planning:

@MusikAnimal Will this still be a valid with your breakthrough approach?

@JWheeler-WMF I wish notifications would actually reach me on Phabricator, closing this one as a duplicate

@dmaza I think this could even be 3 tasks. One for adding the accordion, one for adding content to one accordion tab and another one for the other accordion tab.

I would like it if I had permission in the future, so I wouldn't have to bother you with tasks like that. :-)

That's what I thought being in the ACL group, but somehow I don't have permissions:

@Aklapper I need a second form, that's why I had to make another request. We want different custom template for stories and epics.

@JWheeler-WMF We could potentially remove this from the MVP as Control+F would make it quick to search by name? Up to you.

@JSengupta-WMF The default wiki table allows sorting all columns, it would be more work to allow sorting only by date. Can we leave it like that?

Change: Error validations states have become important again as we don't have a draft mode.

We are not implementing error validation states anymore.
As per the decision made on June 5th, 2024.
Reason: this is extra scope. While it is an optimization and potentially better UX, we don't know how users will interact with the form, and users will still be able to "draft" wishes in their sandbox environments. We can implement draft mode as a fast follow.