Add links to best practices, style guide, and policies at the top of the editor

VERIFIED FIXED in 0.8.2

Status

VERIFIED FIXED
10 years ago
9 years ago

People

(Reporter: cilias, Assigned: paulc)

Tracking

unspecified
0.8.2

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: sumo_only template)

Attachments

(1 attachment)

(Reporter)

Description

10 years ago
When editing an article, there's a notice at the top, saying "You are editing the staging copy of the approved version of this page. Changes will be merged in after approval."

We can make people more aware of the system and documentation by enlarging that notice, by adding links to:
http://support.mozilla.com/en-US/kb/Best+Practices+for+Support+Documents
http://support.mozilla.com/en-US/kb/Style+Guide
and the policies page (bug 446066)

Updated

10 years ago
Assignee: nobody → paul.craciunoiu
Target Milestone: --- → 0.8

Updated

10 years ago
Target Milestone: 0.8 → 0.9
(Assignee)

Comment 1

10 years ago
Should these links be shown only when editing the staging copy, or also when editing an approved version?
(Assignee)

Comment 2

10 years ago
{tr}For more information, please read <a href="http://support.mozilla.com/en-US/kb/Best+Practices+for+Support+Documents">best practices</a>, <a href="http://support.mozilla.com/en-US/kb/Style+Guide">style guide</a>, or <a href="http://support.mozilla.com/en-US/kb/Knowledge+Base+policies">policies</a>.{/tr}

Here's a sample text that would be added inside the same notice. Sound good?
(Reporter)

Comment 3

10 years ago
Theoretically, the only reason someone would be have a KB copy in the editor (rather than the staging copy) would be to move the article out of the KB category, or to implement something like a redirect. So it won't hurt if this doesn't apply when editing the KB copy.

I'll suggest wording after I've got some sleep. :-) But this isn't really a "For more information..." thing, but more of a "Make sure you read..." thing. The policies page is the important one.
(Assignee)

Comment 4

10 years ago
Got it :-)... waiting for review.
(Reporter)

Comment 5

10 years ago
Here's something to replace the entire box. I'm unsure that box is localizable, but the contributor docs are, so I took out the locales from the URLs. CCing David. David could you review this text:

"You are editing the <strong>staging copy</strong> of the article. Changes will be applied after review, to make sure your changes are accurate and follow <a href="http://support.mozilla.com/kb/Knowledge+Base+policies">Knowledge Base policies</a>. For guidelines, please read our <a href="http://support.mozilla.com/kb/Best+Practices+for+Support+Documents">Best Practices for Support Documents page</a>, and <a href="http://support.mozilla.com/kb/Style+Guide">Manual of Style</a>."
(Assignee)

Comment 6

10 years ago
David, could you review Chris's text? :)
(Reporter)

Comment 7

10 years ago
I don't think David will be back from vacation in time to review this. CCing Cheng and Matthew.
(Reporter)

Comment 8

10 years ago
What am I saying? This is a 0.9 bug, not a 0.8.1 bug! :-)

Comment 9

10 years ago
A few nitpicks:
Changes will be applied after [a] review [no comma] to make sure [they] are accurate and follow [the] <a
href="http://support.mozilla.com/kb/Knowledge+Base+policies">Knowledge Base
policies</a>.

Also no comma before the last "and".
(Assignee)

Comment 10

10 years ago
Sounds good. Shall I go ahead and "fix" the bug? :)
(Reporter)

Comment 11

10 years ago
Yup. Thanks Cheng!

Comment 12

10 years ago
Yeah, sorry, that's definitely a go.

Updated

10 years ago
Target Milestone: 0.9 → 1.1
(Assignee)

Comment 13

10 years ago
r21676 / r21677
There we go.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Target Milestone: 1.1 → 0.8.2
Created attachment 358235 [details]
Post-fix screenshot (staging)

Comment 16

10 years ago
As I already said to Paul, I found two additional issues in translating the strings:

1) The strings are two and are too long. English words are usually shorter than Italian words, and so I had to leave something outside in order to fit the maximum length permitted. This problem could be easily experienced for other languages.

So I think each string should be in turn split in other two strings, or the maximum string length should be increased (the first option is better, IMO).

2) The Italian translated strings do not show up. They are in the translation table (search the word "policies" for it and you can check it), but I still see them in English.

Ok, if one is able to translate a page he should as well be able to read the two strings in English, but I think this is still a problem :-) 

Bye
(Reporter)

Comment 17

10 years ago
If there are any issues, it's best to file separate bugs for each of them. That way, each issue can be tracked, with assignees, patches, and QA. It's a lot harder to make sure each bug gets fixed, if we can't track each one separately.

Updated

9 years ago
Whiteboard: sumo_only template
You need to log in before you can comment on or make changes to this bug.