User:Junkie/Help:Wiki structure

wiki 页面制作? 想知道在 MediaWiki 中页面是怎么命名的? 这页告诉你当产生新页面或者移动老的内容时候我们是怎么让 wiki 结构化的. 一致性是好的，它灌输一种信心给读者. 这些规则 和 [[Help:Editing] 规则旨在使用 MediaWiki 的功能, 并且适合 Fedora Project 的需要, 同时使贡献者和读者更加方便.

页面命名
使用此命名新的页面和区域. Also use it for planning where to move nested content migrated from the old wiki.

一般命名规则
这些规则用于页面和章节.


 * Do not nest pages in sub-folders, e.g. Topic/FAQ
 * Exception: Sub-projects with existing ProjectName/ nesting may choose to continue using one-level of nesting.  All pages below that one level should be made to otherwise follow these rules
 * Use natural language naming (as opposed to nesting)
 * Use capital letters only for the initial word in a title or section title: "Like this"
 * Exceptions: Sub-project names, proper nouns, and the titles/chapters of formal, full documentation guides that are converting to XHTML/XML
 * Example: Join the Foo Project; Setting up USB boot media; FAQ on SELinux; Standing in the middle of the field.

最终用户集中的页面
这些页面集中在最终用户所有级别, 初学者经验非常丰富的. 这些页面都是没有在某个子工程或 SIG 下.


 * Name pages within a single, flat namespace; do not use directory-like hierarchies:
 * no : FedoraLiveCD/USBHowTo
 * yes : How to boot a live Fedora image from USB

Project and SIG focused pages for contributors
These are pages focused on contributors who are working in one or more areas of Fedora. Some content may be end-user focused but belong within the project/SIG for reference.

The content here may be divided by one nesting level. Any further nesting needs to be squashed to the one sub-level with a natural language title. The best solution is to entirely rename without nesting, putting all pages in an appropriate Category:Foo Project category.


 * If pages are in a single nested level:
 * no : SIGs/ISV/Join
 * yes : ISV_SIG/Join
 * Content within the single nesting must be in a flat namespace with spaces
 * no : EPEL/PackageMaintainer/GenericJobDescription
 * yes : EPEL/FAQ
 * yes : EPEL/Package_Maintainer_Generic_Job_Description
 * best : Frequently_asked_questions_about_EPEL; Generic_job_description_for_package_maintainers

名字空间
MediaWiki 名字空间由一个后面跟着冒号的特别单词表示, 这样使得内容处于不能的名字空间区域里.

能被自动搜索的名字空间

 * Main:
 * FedoraProject: (default project)
 * Help:
 * Category:

User: namespace
The User: namespace is somewhere you can put drafts and other personal material that you do not want searched and indexed by engines like Google. For instance, the user jpublic can build any wiki materials as desired under User:Jpublic, using subpages. If you need to know what pages you've built under your personal User: namespace, use the Special:Prefixindex page.

Archive: namespace
Move old content to this namespace. This gets it out of the regular search index but keeps it available for future needs.

If you are archiving old content while renaming a set of pages, do not give the page a new, natural language name in the Archive: namespace. It should remain under its old name in the new namespace, to make it easier to find in historical contexts. For example, FooProject/Some/OldStuff moves to Archive:FooProject/Some/OldStuff.

Meeting: namespace
Use this namespace for naturally named pages related to project and SIG meetings. For example, Meeting:Docs IRC log 20080806.

Categories

 * Use as many categories as needed that make sense:
 * Category:SIGs Category:Meeting Logs Category:EPEL
 * The category pages are the aggregation pages. Point to them prominently as the way to find all of something on a topic/within a category.
 * "To review a list of all docs currently in draft, refer to the Category:Draft Documentation."
 * "Useful end-user docs are found in the Category:Documentation."
 * "To learn more about the Documentation Project, refer to the Category:DocsProject.