Support/Kitsune/KB/context scenarios/Bela

Bela: reviewing an edit on the page

1. Bela has received a few messages about needed reviews 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 statistics 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 except one change, so she rejects that change and writes a note in the comment field about why that edit was rejected.
4. The edit is significant, so she checks an option 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 her that Fred edited an article that needs review.
2. Bela isn't in the mood to review right now, but she 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: rejecting spam/vandalism

1. Bela opens the localization dashboard to see if there are article edits waiting for review. There is an article with an edit waiting for review, so she clicks on "review" and gets a nice and detailed visual diff about what changed since the last approval of the article.
2. As it turns out, the edit is simply vandalism. The spammer has not changed any article text, but added a pornographic image to the article.
3. She rejects that change, but instead of writing a note in the comment field, she marks the edit as spam. As a result, not only is the change rejected, but no notification is sent to the spammer, any images and videos added in that edit are deleted, and the account that edited the article is deleted.

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: Subscribe to a category

1. Instead of monitoring each individual article, Bela decides she wants to monitor the entire KB.
2. She visits the category landing page, and just like regular KB articles, there is a link to monitor the article.
3. She clicks on the link, and a notice at the top of the page confirms that she has subscribed.
4. She will get a notification whenever someone edits or comments on an article in that category.

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. From her KB Editors group dashboard, Bela clicks on the "create a new article" item.
2. She is taken to a new article in Edit View.
3. She adds the main article title (doing this also creates a discussion forum for the article)
4. The article already contains one resizable section with a rich text editor.
5. Bella drags the bottom right corner to create some room for her to work.
6. She then starts by writing the introduction.
7. Since this article will apply to many different OSes and Firefox versions, she sets these in the Showfor section of the sidebar.
8. As she continues to work on the introduction, she gets to a section that will contain information for different OSes. She writes them out in one sentence. Then she highlights some text that applies only to Windows and Fx4, clicks the Showfor button and chooses what tags this highlighted section of text will apply to. The result is that section of text now has a corresponding background color in the editor. Example
9. Next Bela wants to add some Step-by-Step instructions she clicks the "Add a new section" button below the previous section that she was working on. This gives her a new blank section to work in. Again she drags the bottom right corner to create some more room for her to work in.
10. She adds a section heading and a brief description. Then before the first step, Bela clicks the "New Step" button and a visual indication is added to the document. Example
11. For this first step Bela drags a screencast she's made into the article window. (Example) The video gallery window pops up and asks her to name the video and select the showfor tags. Then she clicks save and a proxy is added to the document while the video is compressed into multiple formats and uploaded in the background.
12. Next Bela adds the text for that step below the video.
13. Then Bela starts a new step by clicking the New Step button.
14. This time Bela wants to add a screencast that's already in the video gallery so she clicks the insert video button. The video gallery pops up and she chooses the video she wants by clicking on it. It's then inserted in the article complete with it's showfor information. Example
15. Realizing that she's been working on this for a while now, Bela clicks "Save and Continue" before moving on.
16. Once she's done with that Step-by-Step section, Bela creates another one by again clicking the "New Section" button below the current section.
17. This next step-by-step section will contain images instead of videos.
18. Bela continues adding steps with images via drag and drop and the image gallery. Example, Example
19. One of Bela's screenshots could use some additional explanation so she decides to add a note to it. To do that Bela just clicks and drags on the image to create a red box that she can position anywhere on the image. There is also a place for her to enter the on hover text. Example
20. Now that she's just about done, Bela switches to the Article View/Preview view to see how things will look and work for the user.
21. Switching back to Edit View, Bela decides to reorder the sections of the article. She can easily do this by grabbing each section's handle and dragging it into the order she wishes. Example (works like a Netflix queue)
22. Now that she's done writing the article, Bela makes sure all of the article's meta information is set - category, type of article, table of contents on or off, keywords, etc.
23. She also adds a summary of the edits she's made.
24. Finally, she clicks submit.

Bela: Create a new article from the forum

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 article title field has been automatically filled in.
5. She then continues editing the article.

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.