Project:页面命名指南

  • 版本网址缩略名: Project:页面命名指南
  • 版本标题: 页面命名指南
  • 版本 id: 282518
  • 创建于:
  • 创建者: Mhoudg
  • 是否是当前版本?
  • 评论 New page: 这个页面目前没有中文链接,或者中文链接不正确,因此暂时提供英文版本 [[Page Naming Guide]] 中文化翻译正在进行中 From MDC How to help: contents Li...

修订内容

这个页面目前没有中文链接,或者中文链接不正确,因此暂时提供英文版本 Page Naming Guide 中文化翻译正在进行中

From MDC

How to help: contents Lists

   Documentation wishlist 
   Editing/review to do list 
   Migration list 

Guides

   Getting started 
   Writer's guide 
   Writing interface reference documentation 
   Page naming guide 
   Disambiguation pages 
   Localizing MDC 
   Copyrights and licensing 

References

   Wiki markup reference 
   Custom CSS classes 
   Custom templates 
   MediaWiki extensions 
   External redirects 
   Needs redirect

Page naming for the MDC Wiki is relatively straightforward, but it's important you get it correct in order to take full advantage of the custom breadcrumb extension that we have added.

Please also refer to the Writer's guidelines when choosing a page name. Contents {{mediawiki.external('hide')}}

   * 1 General conventions
         o 1.1 Capitalization
   * 2 One-page articles
         o 2.1 Content with a unique title
         o 2.2 Content with a non-unique title
   * 3 Multiple-page content

General conventions Capitalization

Page names should use sentence style capitalization (only capitalize the first word and any proper nouns) rather than headline style capitalization:

   * Correct: "A new method for creating JavaScript rollovers"
   * Incorrect: "A New Method for Creating JavaScript Rollovers" 

For the time being these capitalization rules for page names apply only to new pages. There are a large number of pages in our wiki that do not conform to these rules, but please do not correct those at this time. We will sort out the logistics and fix older page names at some point in the future. Thanks. -- dria 09:20, 14 March 2006 (PST) One-page articles Content with a unique title

If you are adding an article or other content that only requires a single page in the wiki, simply use the name of that article as the page name.

For example, the page for a one-page article called "A new approach to JavaScript rollovers" would be, simply A new approach to JavaScript rollovers. So long as your content title is unique, this is the easiest and preferred approach. Content with a non-unique title

Wherever possible, you should try to create content with unique titles, in order to simplify the page naming as much as possible. If this is impossible, prefix the title with the topic, followed by a colon and no spaces.

For example, if I needed to add a page called "Optimization", simply calling the page "Optimization" would create a possible conflict as Optimization can apply to a wide variety of topics within the wiki. If my Optimization article was specifically about CSS, I would expand my title so it is unique (ie: CSS optimization).

If there are two or more pages which have the same "natural" title, a disambiguation page should be created.

It is a best-practice within this wiki to have unique article titles wherever possible. Multiple-page content

If the content you are adding to the wiki requires multiple pages, use the following page naming method. This method takes advantage of the breadcrumb extension.

   * Learning JavaScript - Main table-of-contents page
   * Learning JavaScript:Introduction
   * Learning JavaScript:A layperson's view
   * Learning JavaScript:More advanced scripting
   * Learning JavaScript:Next steps 

Note the addition of the initial "Learning JavaScript" page. In order for the breadcrumb extension to work, each part of the colon-delimited page names has to exist as a separate and navigable page.

If you want to use the breadcrumb extension for navigational hierarchy in your pages, you must use the colon-delimited page naming system described here.

修订版来源

<p>这个页面目前没有中文链接,或者中文链接不正确,因此暂时提供英文版本 <a href="cn/Page_Naming_Guide">Page Naming Guide</a>
中文化翻译正在进行中
</p><p>From MDC
</p><p>How to help: contents
Lists
</p>
<pre class="eval">   Documentation wishlist 
   Editing/review to do list 
   Migration list 
</pre>
<p>Guides
</p>
<pre class="eval">   Getting started 
   Writer's guide 
   Writing interface reference documentation 
   Page naming guide 
   Disambiguation pages 
   Localizing MDC 
   Copyrights and licensing 
</pre>
<p>References
</p>
<pre class="eval">   Wiki markup reference 
   Custom CSS classes 
   Custom templates 
   MediaWiki extensions 
   External redirects 
   Needs redirect
</pre>
<p>Page naming for the MDC Wiki is relatively straightforward, but it's important you get it correct in order to take full advantage of the custom breadcrumb extension that we have added.
</p><p>Please also refer to the Writer's guidelines when choosing a page name.
Contents
{{mediawiki.external('hide')}}
</p>
<pre class="eval">   * 1 General conventions
         o 1.1 Capitalization
   * 2 One-page articles
         o 2.1 Content with a unique title
         o 2.2 Content with a non-unique title
   * 3 Multiple-page content
</pre>
<p>General conventions
Capitalization
</p><p>Page names should use sentence style capitalization (only capitalize the first word and any proper nouns) rather than headline style capitalization:
</p>
<pre class="eval">   * Correct: "A new method for creating JavaScript rollovers"
   * Incorrect: "A New Method for Creating JavaScript Rollovers" 
</pre>
<p>For the time being these capitalization rules for page names apply only to new pages. There are a large number of pages in our wiki that do not conform to these rules, but please do not correct those at this time. We will sort out the logistics and fix older page names at some point in the future. Thanks. -- dria 09:20, 14 March 2006 (PST)
One-page articles
Content with a unique title
</p><p>If you are adding an article or other content that only requires a single page in the wiki, simply use the name of that article as the page name.
</p><p>For example, the page for a one-page article called "A new approach to JavaScript rollovers" would be, simply A new approach to JavaScript rollovers. So long as your content title is unique, this is the easiest and preferred approach.
Content with a non-unique title
</p><p>Wherever possible, you should try to create content with unique titles, in order to simplify the page naming as much as possible. If this is impossible, prefix the title with the topic, followed by a colon and no spaces.
</p><p>For example, if I needed to add a page called "Optimization", simply calling the page "Optimization" would create a possible conflict as Optimization can apply to a wide variety of topics within the wiki. If my Optimization article was specifically about CSS, I would expand my title so it is unique (ie: CSS optimization).
</p><p>If there are two or more pages which have the same "natural" title, a disambiguation page should be created.
</p><p>It is a best-practice within this wiki to have unique article titles wherever possible.
Multiple-page content
</p><p>If the content you are adding to the wiki requires multiple pages, use the following page naming method. This method takes advantage of the breadcrumb extension.
</p>
<pre class="eval">   * Learning JavaScript - Main table-of-contents page
   * Learning JavaScript:Introduction
   * Learning JavaScript:A layperson's view
   * Learning JavaScript:More advanced scripting
   * Learning JavaScript:Next steps 
</pre>
<p>Note the addition of the initial "Learning JavaScript" page. In order for the breadcrumb extension to work, each part of the colon-delimited page names has to exist as a separate and navigable page.
</p><p>If you want to use the breadcrumb extension for navigational hierarchy in your pages, you must use the colon-delimited page naming system described here.
</p>
恢复到这个版本