Segmenting non-end user pages
Jason Barnabe (np)
list, style guide, etc.)? Are we going to put them in a separate
category or something?
Nelson Ko
wrote:
> How are we going to segment non-end user pages (e.g. article tracking
> list, style guide, etc.)? Are we going to put them in a separate
> category or something?
Yes. Putting them into a separate category is ideal. Chris has already
put them into the "Staging Area" already to keep them from non-end
users. We can create more categories but we might not want too many
categories because contributors will then have to make a more
complicated choice of which category to use when they create a new
article. But of course, 2, 3 or 4 should be OK.
Jason Barnabe (np)
That sounds good. The categories I think we should have are
Mozilla Knowledge Base (public)
Staging (things that will become public)
Administration (style guides, etc.)
Sandbox
Chris Ilias
I want to bring some attention back to this discussion, because after
reading the associated bug [1], I want to clear any misunderstandings.
They way the KB is working now, is not what is intended. The plan, from
the beginning, was that we never *ever* want misinformation to be live
on Sumo. In order to achieve this, new contributors need to prove that
they can be trusted to make edits on the site. How do they do that? We
review their edits before the edits go live. Sounds easy, when the
initial pages are being built, but after they go live, it becomes much
more difficult.
The way we've been building content now, articles have been live right
away; because the site itself was a staging site. However, we're going
to eventually put a guard at the door.
Now that we've got a decent amount of content, I'd like to start
implementing this system ASAP. Last night, I moved all articles not
deemed ready for beta, to the staging area.
[1]<https://bugzilla.mozilla.org/show_bug.cgi?id=392513>
--
Chris Ilias <http://ilias.ca>
List-owner: support-firefox, support-thunderbird, test-multimedia
Chris Ilias
I want to bring some attention back to this discussion, because after