Archive:Community Pages: Difference between revisions
imported>Larry Sanger |
imported>Larry Sanger |
||
Line 26: | Line 26: | ||
* '''What are the best ways to achieve that purpose? What are some common tips, "best practices," etc.?''' | * '''What are the best ways to achieve that purpose? What are some common tips, "best practices," etc.?''' | ||
** Generally, think of the convenience of the contributor first and foremost. | |||
** Few mouseclicks to the most popular information. | ** Few mouseclicks to the most popular information. | ||
** A "logical," or "clear," or "common-sensical" sort of organization. Information should be where | ** Highlight (place higher, using larger font, etc.) the most popular information. | ||
** A "logical," or "clear," or "common-sensical" sort of organization. Information should be where most people would expect it to be. | |||
** Be highly modular, but have a kick-ass table of contents and navigation tools. There is certainly ''some'' benefit to having "extended narratives," but not enough to put off the people who don't want to read all that in one sitting. | ** Be highly modular, but have a kick-ass table of contents and navigation tools. There is certainly ''some'' benefit to having "extended narratives," but not enough to put off the people who don't want to read all that in one sitting. | ||
** Have extremely clear titles, but supplement them with ''brief'' but helpful subtitles that are placed/formatted so that they don't get in the way. | |||
** Have a "start here" page. Don't overwhelm people with data on that page. Let them choose what they want to find out about. Have just one ''brief'' introductory narrative, that is focused mostly on motivation, but also provides a few choice links to the most popular info. | |||
** Consider not using tables of contents. This implies: "too much information!" | |||
* '''Should the pages all be in the CZ: namespace, or should some go in the Help: namespace?''' | |||
Move everything to the CZ: namespace. We ''could'' put technical explanations in the Help: namespace, but there is no clear distinction to be made between "technical" issues and "policy" issues. Just get rid of "Help:" altogether (move it, of course). | |||
* '''We've said we want to have a minimal rule set. Is this really advisable? Why or why not? How can we describe the "minimum" ''adequate'' set of rules?''' | |||
* What is the overall ''structure'' of the pages? | * What is the overall ''structure'' of the pages? | ||
* Should we have categories or templates for navigation? | * Should we have categories or templates for navigation? |
Revision as of 13:25, 3 September 2007
Personal notes for reworking wiki pages, but open to comments. --Larry Sanger
I'm convinced that the whole set of introductory pages need a complete reworking. Here are some observations, questions, principles, etc.
- The landing page is simply too complicated. Too many links, too many words, will be off-putting to many people. It's all right to have a lot of links, perhaps, but it's not all right not to have a very simple presentation.
- It would be fine to have most of the detailed links on pages prominently linked from the main page, but they have to be quite obvious. They have to be clearly labelled, clearly placed, and most importantly, the whole set of them has to be clearly conceptually organized.
- Some candidate "top topics," i.e., categories of stuff that someone landing on CZ might be interested in: a few good articles; approved articles; entry points; an entertaining summation of "what we're all about"; donation; recent changes; project home; a welcome letter; explanation of how to get started as a contributor (for general public and for editors); policies.
Questions
OK, what are the questions or properties that I need to explore in organizing these various help and policy pages?
- Who are these pages for, and what is their purpose?
The pages are for (1) new people, who need both motivation and simple explanation; (2) regular contributors, who need clear, easy-to-find answers to help and policy questions; and (3) decision-makers, who need clearly-stated rules that they can proceed to interpret.
So the pages have basically two purposes: they motivate people to work; they explain policy at basic and in-depth levels. But policy explanations have at least two purposes: to get instructions for new content, and to make decisions about matters of controversy over existing content. (The latter distinction is similar to the help booklets released by government agencies that simplify the laws "on the books.")
- Should there be a distinction between "help" or "instructions" on the one hand, and policy statements on the other hand? How can this distinction best be drawn both in theory (what is the difference) and in practice (how do we distinguish the pages)?
I'm not at all convinced that there should be a difference. The central problem (for both Wikipedia and CZ) about managing policy and help pages is that people write as if there is a difference--as if the rules were like Statute Law, and the help pages were those little citizen booklets--when there isn't any practical difference. Ultimately, the analogy to statute law is terrible, because "the people" carry out the rules on a wiki. So the rules really should be written clearly and engagingly everywhere, and as such, there is no need for repetition.
So I propose that we have exactly one set of rules and instructions, and that the rules should be written more or less in the form of instructions. If there need to be boring details, the boring details can go in footnotes or on separate pages.
- What are the best ways to achieve that purpose? What are some common tips, "best practices," etc.?
- Generally, think of the convenience of the contributor first and foremost.
- Few mouseclicks to the most popular information.
- Highlight (place higher, using larger font, etc.) the most popular information.
- A "logical," or "clear," or "common-sensical" sort of organization. Information should be where most people would expect it to be.
- Be highly modular, but have a kick-ass table of contents and navigation tools. There is certainly some benefit to having "extended narratives," but not enough to put off the people who don't want to read all that in one sitting.
- Have extremely clear titles, but supplement them with brief but helpful subtitles that are placed/formatted so that they don't get in the way.
- Have a "start here" page. Don't overwhelm people with data on that page. Let them choose what they want to find out about. Have just one brief introductory narrative, that is focused mostly on motivation, but also provides a few choice links to the most popular info.
- Consider not using tables of contents. This implies: "too much information!"
- Should the pages all be in the CZ: namespace, or should some go in the Help: namespace?
Move everything to the CZ: namespace. We could put technical explanations in the Help: namespace, but there is no clear distinction to be made between "technical" issues and "policy" issues. Just get rid of "Help:" altogether (move it, of course).
- We've said we want to have a minimal rule set. Is this really advisable? Why or why not? How can we describe the "minimum" adequate set of rules?
- What is the overall structure of the pages?
- Should we have categories or templates for navigation?
- What's the maximum amount of information that should go on a page? What's the "right size" for a page?
- What are some basic requirements of clear exposition of rules and help pages?
- How should the structure be filled out?
List of things to organize
Introductory and getting-started
Help/how to
Policy
|
Organization
Initiatives
Article lists
Communication
Tools
Miscellaneous
|
New user observation
Hi Larry. Something that struck me as I have been educating myself about CZ these recent days has been the absence of a left menu "Help" link in the basic CZ page template. "Support" was the closest but that was not it. When I have wanted to learn something (either editing tips or policy matters) I have needed to hunt them down. I notice a help section mentioned above but thought it worth mentioning that a 'one-click' "Help" as a single line link at left of every page would really (ahem) help. --Ian Johnson 10:11, 27 July 2007 (CDT)