If the user has chosen "yes" or "no" on any of the link suggestions, then after the user selects the "Publish" button (which may say "Submit" if they have not chosen "yes" for any links), they get the edit summary dialog. If they have //not// chosen "yes" or "no", and have only skipped the suggestions, the publish button will not be active, and so the user can't even get to this state.
* **Overall**
** This special edit summary shares little with the default edit summary in the visual editor. The only components that remain the same are the header, cancellation "X", and publish buttons, the disclaimer about Terms of Use, and the "Review your changes" button.
** It does not contain any free text field for an edit summary, or checkboxes for "watch this page" or "minor edit".
* **Header**
** Just as it usually does, the header should contain a back arrow to close it (mobile) or an "X" to close it (desktop).
** Just as it usually does, the header should say, "Save your changes".
** If the user has chosen "yes" on any suggestions, the publish button should say, "Publish" (mobile) or "Publish changes" (desktop), just like it usually does.
** If the user has not chosen "yes" on any suggestions, the publish should say, "Submit".
* **Body**
** Header: "Summary"
** Below the header should be a table summarizing the work the user did in the task. It should have two columns.
*** Suggestion column
**** Header: robot icon followed by "Suggestion".
**** Each row should show, for each suggestion in the order presented in the article: the link text, followed by an arrow, followed by a "link" icon, followed by the link target. E.g. "stovetop --> đź”— stovetop"
*** Linked column
**** Header: "Linked?"
**** If the user accepted the suggestion: blue checkmark.
**** If the user rejected the suggestion: red X.
**** If the user skipped the suggestion: gray dash.
** Below the table is where we put the publishing disclaimer which is unique to each wiki: "By publishing changes, you agree to the..."
* **Footer**
** If the user has chosen "yes" for any links, then just as it usually does, the footer should have a "Review your changes" button. This should open up the visual diff review, just like it usually does.
** If the user has not chosen "yes" for any links, then that button should not be present.
* **Publishing**
** If the user has chosen "yes" for any links, then those changes should be published to the wiki with an edit summary that reads like this: "Link suggestions: 7 accepted, 2 rejected, 1 skipped."
** If the user has chosen "yes" for any links, the page should be automatically added to the user's watchlist.
** If the user has not chosen "yes" for any of the links, then nothing gets published to the article.
** No matter what the user has and has not chosen, a log entry gets created per T266473.
| //Mobile mockups as of 2021-01-12:// {F34011479} | //Desktop mockups as of 2021-01-12:// {F34011477}
**NOTE:** Refer to Figma for up-to-date detailed redline mocks and specs:
!!Mobile: https://www.figma.com/file/2SONd8P1tsexIB5coMOp8h/Growth-Structured-tasks?node-id=181%3A65!!
!!Desktop: https://www.figma.com/file/2SONd8P1tsexIB5coMOp8h/Growth-Structured-tasks?node-id=112%3A0!!
==== Instrumentation ====
//See {T268034} for details.//
We need to record when the user attempts to advance to the edit summary screen, which can be done either through selecting the explicit “Publish/Submit” button or by advancing/skipping from the last link suggestion. When they do this, we should record which route they took.
If the user has not skipped all suggestions, they’ll go to the edit summary screen. We need to record:
* Impression for the screen, along with counts for its contents, e.g. “7 accepted, 2 rejected, 1 skipped”
* An event when the user selects the option to “Review your changes”
* An event when the user selects the arrow to return to the article.
* An event when the user selects the Publish/Submit button.