Both the mentorship module and the help module contain ways to post questions on other pages. Some newcomers may look for answers by returning to their homepage to try to get over to the place where their question has been posted. This feature may help them find and read their answers more easily.
Specifications
- Mockups for this capability are visible here, shown with the mentorship module.
- When the newcomer has asked a question, a new header should appear under the "Ask the help desk"/"Ask your mentor a question" button that reads, "Your recent questions".
- Listed under that header should be the most recent three questions that the user has asked via that module.
- They should be listed with a snippet from the beginning of the text with an ellipses. So if the user's question was, "hello Cloud atlas, how do i add a photo to an article?", the snippet might read, "hello Cloud atlas, how do i a..."
- Underneath the snippet, we should list how long ago the question was posted.
- Today: "Posted today"
- Yesterday: "Posted yesterday"
- 2 days ago or more: "Posted 65 days ago". That said, it would be ideal to use the same logic here that we used in T217105 to break this timeline into weeks, months, and years.
- If a link to a question no longer works, because the page has been archived or the question has been deleted/reverted:
- The snippet of the question should be greyed out and italicized.
- The line underneath should read like "Posted 65 days ago (archived)". If the revision is available (hasn't been deleted) then "archived" should be a link to go to the revision where the question was originally posted.
- This should all have a tooltip that reads, "This question has been archived likely because it was asked a long time ago."
- After posting a question via mentorship or help, the module display should be updated without requiring a page reload.
The biggest open concern is how to handle the cases when questions are no longer present at their original links because they have been archived, deleted, or reverted. We don't want to silently take something away from the user. See T215986 for a discussion of these situations and ideas for how to deal with them.