Closed Bug 446079 Opened 14 years ago Closed 11 years ago

Thank you and explanation page after saving an edit

Categories

(support.mozilla.org :: Knowledge Base Software, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE
Future

People

(Reporter: cilias, Unassigned)

Details

Attachments

(1 file, 2 obsolete files)

After saving an article edit, there should be a page that thanks the person for contributing, and explains that the edit was made on a staging copy and will require approval before going live.
Very good suggestion. Suggested text and placement?
Target Milestone: --- → 0.6.2
How about a box on top of the page itself after saving with the text in it, rather than a separate page?
Attached image postsave box
Right now, after saving an edit, the contributor is taken to the staging copy of the article, which already has a box:
"This is the staging copy of the approved version of this page.  Latest changes will be synchronized after approval."

I suppose we can make it more obvious (in addition to added thank you text).
Yep, and that's hardcoded - should be rather trivial to fix.

What kind of text should appear there? I'll prepare a patch then.
Assignee: nobody → mail
Lucy or Chris, could you suggest what text you would like to see here?
Attached file thank you text (obsolete) —
Here's a draft of the text. If we can make "Your edit will be reviewed soon." a heading, that would be great.

For clarification, this text can only be used after an article edit.
Attached file thank you text w/note about credits (obsolete) —
Here's a new version. I decided to add something about the contributor's name being added to the article credits.
Attachment #333812 - Attachment is obsolete: true
Target Milestone: 0.6.2 → 0.6.3
I de-commatized it a bit... How about:

---
Thank you for improving the Firefox Support Knowledge Base. Your contributions are very appreciated. 

What's next? In order to ensure that the information is accurate and follows the <Knowledge Base content guidelines*>, your edit will be reviewed. If approved, the change will be applied to the Knowledge Base article and your name will be added to the credits section.
---

*) Link to http://support.mozilla.com/en-US/kb/Improving+articles or http://support.mozilla.com/en-US/kb/Best+Practices+for+Support+Documents ?

I don't think this text needs to be shown for approvers, so the added paragraph for approvers seems superfluous to me. We could have an entirely separate text for approvers though. Ideally this would be a content block, so we could change this as we wish.
I fear that with "Thank you for improving the Firefox Support Knowledge Base" being the first sentence, contributors may assume it's just a thank you message, and not bother reading the rest.

The link should be to <http://support.mozilla.com/en-US/kb/Knowledge+Base+policies>, but for some reason it won't load. 
See bug 451152 [Can't load KB policies page].
(In reply to comment #9)
> I fear that with "Thank you for improving the Firefox Support Knowledge Base"
> being the first sentence, contributors may assume it's just a thank you
> message, and not bother reading the rest.
> 

Then make the "What's next?" sentence bold; that should make sure people continue reading, me thinks.
ok
Attachment #334002 - Attachment is obsolete: true
Just to clarify, I want to start with a thank you, because that's one of the things I think we should be better at; being more thankful I mean. I do see your point though, which is also why I separated the paragraph before "What's next?".
Should we start out with a header that just says Thank you! and then follow with the what's next, and close with the more detailed thank you?

__Thank you!__

Your edit has been successfully submitted. In order to ensure that the information is accurate and follows
the <Knowledge Base content guidelines*>, your edit will be reviewed. If
approved, the change will be applied to the Knowledge Base article and your
name will be added to the credits section.

Thank you for improving the Firefox Support Knowledge Base. Your contributions
are very appreciated. 
I think contributors are only going to glance over that text, assuming it's just a thank you message. Particularly if the first sentence is "Your edit has been successfully submitted."

45% of contributors that took the survey, did not know about the staging system.

I just remembered that in Toronto, we discussed having a thank you page after an edit has been made, and using it to introduce the contributor to different possible ways to contribute. What do you think of adding something like that to this bug? Maybe a link to the Contributors forum?
Well we've got 3 goals here:

1. Let the reader know their help is appreciated
2. Let them know what to expect, so that they don't get upset when their edit isn't live right away
3. Encourage them to help out more

1 helps accomplish 3, and 2 helps enable 3 rather than block it, however we also want to make sure everything is read.  People won't do 3 even if 1 happens if they don't understand 2, so I think you're right about being careful to make sure 2 is placed where it will most likely be read.  David is also right though, we need to make sure users also see 1 or they won't go for 3.

I think we can tie in 2 and 3. Our how to contribute sections already explain the process.  So we might want to have some line about "to find out more about what happens now, or to see other ways you can help us out, check out [link].

I think you're right about the successfully submitted line, it's probably not necessary, otherwise they wouldn't be getting a Thank You! page.  Maybe start with some version of "Your edit will appear on our site as soon as our reviewers have had a chance to look it over."
This is why I'm proposing this is a content block, so we can edit this after we implement it. 
Pushing to 0.6.4
Target Milestone: 0.6.3 → 0.6.4
Target Milestone: 0.6.4 → Future
Targeting to 1.4 to keep this on the radar. If we implement a content block that we can change easily from the admin interface (and localize), we can experiment with different wordings.
Assignee: mail → nobody
Target Milestone: Future → 1.4
Target Milestone: 1.4 → Future
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.