Support/Kitsune/KB/context scenarios/Bela

Bela: reviewing an edit on the page

1. Bela got a few mails about needed reviews alsready and decides that it is time to bring that number down. She opens the dashboard and looks at the "review needed" section. It lists the articles together with some statistcs about date of the review request, popularity of the article etc.
2. She choses "How to set the homepage", a highly popular article for which Fred had requested review a week ago. She clicks on "review" and gets a nice and detailed visual diff about what changed since the last approval of the article.
3. For every change she can accept or reject the changes. She is happy with everything, but one change, so rejects that change, writes a note in the comment field.
4. The edit is significant, so she check marks a box that will mark translations of the article as "Needs updating" in the localization dashboard.
5. She submits the review so that the article becomes visible to all users. Fred receives an email that Bela reviewed his article with the lines that were rejected and the note that Bela made.

Bela: reviewing an edit by mail

1. Bela is working on her computer and gets an email informing him, that Fred edited an article that needs review.
2. Bela isn't in the mood to review right now, but want's to peek at what changes Fred made. Luckily the email already contains information about that and a link to a more friendly view. Fred had only changed a few lines, so Bela decides to accpet that by clicking the "accept changes" link in the mail.

Bela: Review an article

1. Bela gets an email notifying her that an article thread has been marked as ready for review.
2. She clicks on a link to the article in the email, and reviews the article contents. Article discussion is also available to her, so she can see the reasoning behind the article.
3. She decides that the article text is great, but the article needs some screenshots; so she creates a screenshot on her computer, and clicks on "edit this article".
4. The article editor opens, and she places the cursor where she wants to add a screenshot, then clicks "Add screenshot" to upload here image.
5. She is then asked to choose which Firefox version and operating system the image is of. She chooses Firefox 4.0 and Windows, then clicks "Insert". The image gets automatically inserted where the cursor was on in the article, and made available to her in an image library for the article.
6. She doesn't want to be notified of any future changes to the article, so before saving her edit, she unchecks a box that will subscribe her to email notifications for any future edits to that article or posts in the corresponding article discussion thread.
7. She saves her edit, which then takes her back to the article draft. She chooses to approve the article, and clicks on "Approve".
8. The article is then made public, a staging copy is automatically created, and the article thread is automatically resolved.

Bela: Subscribe to an article without editing it

1. Bela wants to keep up with changes to an article she has not edited, so she goes to the article and clicks on subscribe.
2. She is then notified that she is subscribed to all edits and thread posts to the article, and given a link/button to unsubscribe.

Bela: view poll data for one article

1. Bela previously edited an article, and now she wants to see if her edit has made the article better. She goes to sumo and logs in.
2. After logging in she is taken to her dashboard, which lists edits she has previously made, and links her to a view of the article history.
3. She clicks on the link to the article she previously edited, and it takes her to the articles history page with a graph displaying how the helpfulness score of the article has changed since over time, with markings for when each edit was made. It highlights her edit, and the difference in the score since her edit.

Bela: edit more than one article

1. The text on a Firefox setting has changed in a new version of Firefox. Bela wants to update the KB for this change. She goes to the approvers dashboard, and launches Find and Replace for the KB.
2. She enters the text that needs to be replaced in the KB, and the Find and Replace feature displays all affected articles, with a snippet of the content in the article where text appears.
3. After looking at the affected pages, she sees that the text on one of the pages is referring to something completely different, so she does another search, but this time includes the markup that is usually around the text she is looking to replace.
4. This time only articles that will need to be updated are displayed, so she goes ahead and enters the replacement text. As before, a list of affected articles appears, but this time she can preview each article with a change.
5. She decides to go ahead and apply the change, so she selects each article she wants to apply the change to, and confirms the action.
6. The changes are applied to the staging copy of each article, and await the same review process as regular article edits.

Bela: Edit a sub-page

1. Bella sees wants to add a screenshot to the sub-page, so she visits an article that contains one of the sub-pages.
2. She opens that page in the article editor. Near the pointer (include) to the sub-page, is a link to edit the sub-page. She clicks on that link, and a new editor window opens, where she can edit the sub-page.
3. She adds a screenshot to the sub-page, and saves her edit.
4. The edit is saved in a staging copy of the sub-page, where it awaits review.

Bela: Create a new article

1. A discussion in the contributors forum reveals the need for a new KB article.
2. Bela starts a new thread in the articles forum which automatically creates a new article with the name of the thread.
3. Following the link in the thread she just created, Bela is taken to the article editor.
4. In the article editor Bela notices that the editable url field has been automatically filled in for the article. She decides to use the default url for the moment.
5. Next Bela chooses from number of different templates that are grouped by article type (troubleshooting, tutorial, reference, etc)
6. Once she chooses a template the editor window is filled in with wiki markup in a medium gray color and sample content in red text.
7. By default the editor's active tab is for Windows content for the latest version of Firefox (Fx 4).
8. Bela then goes about replacing the sample content with her own writing which is in black text.
9. Once she is done with the windows version, she switches over to the Mac tab which is now a copy of the Windows content that she just wrote.
10. Bela then edits the info in the Mac tab, making the instructions specific to Macs.
11. She continues this process for each of the tabs (linux, Fx3.6, etc.)
12. Once she's done writing, Bela decides to upload some screencasts that she's made.
13. She switches back to the Windows, Fx 4 tab and drags the video from her desktop to the section where she wants the screencast to appear. She gets a notification and a progress bar while the SUMO add-on compresses her video into the required formats and uploads them to SUMO in the background.
14. While the video is compressing and uploading she moves on to adding a screenshot.
15. Again, Bela just drags the image she wants to use to the part of the article where she wants it to appear.
16. After a brief wait (some kind of activity indicator during the wait) the image is uploaded to SUMO and the code is displayed.
17. Once the video is done compressing and uploading it's code shows up in the editor.
18. When Bela is done creating the article she clicks the preview tab where she can see the article as it will appear when published.
19. In the article preview she can also add notes to the screenshots in the article. She clicks and drags to draw a red outline over the image and then types the note into the attached text box. The notes also support wiki markup like lists and links.
20. Also in the preview she can edit the video's poster frame from a selection of frames that were grabbed and uploaded by the SUMO add-on.
21. Once she is done checking over the preview, she clicks the submit for review button which adds the article to the review queue.

Bela: Rename an article via the article

1. Bela doesn't like the name of an article, and after some discussion in the article thread, it is decided that she will rename the article.
2. She goes to the article, and clicks on "edit this article". The article editor opens, containing a text field with the article name.
3. She replaces the text in the article name field, and adds the old name to an optional "alternate names" field, then saves her edit.
4. The article, its staging copy, and the article thread are renamed, maintaining translations. The old URL now redirects to the new URL.

Bela: Rename an article via the articles forum

1. Bela doesn't like the name of an article, and after some discussion in the article thread, it is decided that she will rename the article.
2. On the original post in the thread, she clicks on a link to edit the thread title.
3. She replaces the text in the article name field, and adds the old name to an optional "alternate names" field, then saves her edit.
4. The article, its staging copy, and the article thread are renamed, maintaining translations. The old URL now redirects to the new URL.

Bela: Remove an out of date warning via dashboard

1. Bela looks at the Localization Dashboard, and sees that one article is marked as "needs updating", so she clicks on the link to the article from the dashboard, which opens the article in the editor.
2. The editor also contains a diff view of changes made to the English article as well as a summary of each change. She makes the appropriate changes to the article and saves the edit.
3. The article remains under the "needs updating" section of the dashboard, but the status is set to "needs review".
4. When the edit is approved, the warning is removed from the article, and the article goes back to being marked as "Translated" in the dashboard.

Bela: Remove an out of date warning via dashboard

1. Bela visits an article and sees that it has a "Content may be out of date" warning, so she clicks on the "edit this article",which opens the article in the editor.
2. The editor also contains a diff view of changes made to the English article as well as a summary of each change. She makes the appropriate changes to the article and saves the edit.
3. The article remains under the "needs updating" section of the dashboard, but the status is set to "needs review".
4. When the edit is approved, the warning is removed from the article, and the article goes back to being marked as "Translated" in the dashboard.

Bela: tweak search results

1. Bela sees that a trended search phrase is "clear cash". Knowing that those users probably want the "How to clear the cache" article, she goes to the article, and clicks edit.
2. Within the editor is a section to add search keywords. There, she adds the term "cash", then saves her edit.
3. After the edit is saved, she approves her edit, and that change is documented in the article history.

Bela: translate a sub-page

1. Bela is translating an article and comes across a sub-page. SUMO recognizes that he sub-page is not translated into Bela's language, so there is a link provided beside the sub-page for her to create a translation of it.
2. She clicks on the link, and a new tab opens, and follows the same steps as she would to translate any other article.