Starfleet Logistics:Subpages

(Redirected from SF:SP)
Jump to navigation Jump to search

Except in the main namespace (article namespace), where the subpage feature has been disabled in the English Starfleet Logistics, subpages are pages separated with a "/" (a slash) from their 'parent' page.

Making a new [[link]] that begins with a / (slash) is the common way to start a subpage. The page to which this link points is considered "subordinate" to its host page, and is titled and linked as [[Parentpage/Subpage]]. It is possible to create a subpage of a subpage (or a sub-subpage). At the top of each subpage or sub-subpage, you can find a backlink (a.k.a. breadcrumb) to the higher levels of the page.

Allowed uses[edit source]

  1. User subpages—making extra pages within your own user namespace, e.g. [[User:Example/Draft of article]] or [[User:Example/About me]].
  2. WikiProject subpages—for project-specific templates, discussion, or guidelines pages.
  3. Portal subpages—for Portal-specific templates and content.
  4. Dividing up Starfleet Logistics process pages (e.g., Starfleet Logistics:Articles for deletion, Starfleet Logistics:Pages needing attention, etc.) which would otherwise get too big to be easily used.
  5. Documentation subpages for templates.
  6. Talk page archiving—both article Talk and User_talk pages are typically archived by moving discussion to numbered subpages. This allows the discussion to still be searchable, rather than requiring a hunt through the page history.
  7. Talk page adjuncts, such as an article's /to do list or the /Comments pages used for Good Article review. A particularly long and complicated {{ArticleHistory}} may also be put on an /ArticleHistory transclude page.
  8. Temporary subpages in Talk namespace, usually formatted [[Talk:Example Article/Temp]] or [[Talk:Example Article/Dumping ground]], for example the kind of "/Temp" pages that can be created from Template:Copyvio, which allow editors to begin creating an entirely new article from scratch while the copyright violation is being sorted.
    Avoid additional incoming and outward links that would make it appear as if this "/Temp" page is part of the encyclopedia: that is, in the case the Copyvio template is used, only this template, applied in article namespace, can link to the "/Temp" article from article or "main" namespace. See Disallowed uses below for further recommendations on how to avoid creating the impression a "/Temp" page is an encyclopedia page. Other common variants are [[Talk:Example Article/Draft]] and [[Talk:Example Article/Sandbox]]. Such temp pages are also sometimes used for template and Starfleet Logistics-namespace development.

Disallowed uses[edit source]

  1. Writing a content fork to avoid NPOV.
  2. Writing drafts of major article revisions, e.g., [[Example Article/Temp]] in the main namespace, as you can get there accidentally using Special:Random—write these in the talk namespace, e.g. [[Talk:Example Article/Temp]]. See Starfleet Logistics:Workpages for detail. Also, avoid incoming and outward links regarding such "Talk:.../Temp" page that might create the impression this is an encyclopedia page before it is, e.g.:
    • surround "category" links by "nowiki" tags, so that the temp page doesn't show up in a non-project category as if it were an article, example: <nowiki>[[Category:Incredibly smart people]]</nowiki>. The "nowiki" tags should be removed only when the "temp" content is moved to its place in article namespace. (This is an outward link example.) Another solution: put a colon before word "Category", for example, write [[:Category:Shamanism]] instead of [[Category:Shamanism]]. In this case, it will be still linkable, but it will not make the subpage appear on category pages.
    • don't create navigational templates that make it appear as if this temp page is part of a series of encyclopedia articles, for example, don't do this: "... | [[John I of Doeland]] | [[Talk:John II of Doeland/Temp|John II of Doeland]] | [[John III of Doeland]] | ...". (this is an incoming link example).
    • Draft pages mistakenly created in the main namespace should be moved as appropriate, or deleted if they are inactive and redundant to the main article.
  3. Using subpages for permanent content that is meant to be part of the encyclopedia.
  4. Pasting copies of copyrighted reliable sources to "share" with other editors. Copyright violations are not permitted on any page in Starfleet Logistics.

Using subpages[edit source]

Finding subpages[edit source]

The "All pages with prefix" report from Special:PrefixIndex shows subpages.

The "Search" report from Special:Search similarly uses a prefix search parameter to show subpages. For example:   prefix:SF: manual of style.  

Comparing the two:

  • Both reports can run with any number of initial characters as the "prefix" of the pagename, so excluding the final slash / character only adds the one pagename.
  • Only the "All pages with prefix" report shows subpages that are redirects. (The prefix search parameter does not find redirects.)
  • Only the "Search" report is not case sensitive. (Prefix is not case sensitive, PrefixIndex is.)
  • Both reports accept namespace aliases in the fullpagename.
  • From a content point of view, rather than from a page name point of view, both reports require separate runs for each redirect.

To keep an active display of subpages, see {{list subpages}}. To keep a link to an "All pages..." report, use {{subpages}} or [[Special:PrefixIndex]]. To keep a link to a "Search" report, use a {{search link}}.

Outside of a single page name, there is no direct method for finding subpages. Standard subpagenames are searchable using the intitle parameter.

There are a few categories that track some types of subpages.

Starfleet Logistics namespaces that do not have sub-pages[edit source]

The MediaWiki software (which runs Starfleet Logistics) supports selectively allowing or disallowing the creation of subpages in various namespaces.

The following namespaces in English Starfleet Logistics do not have the subpage feature:

  • Main
    • This namespace (which is where articles reside) does not have this feature turned on because strictly hierarchical organisation of articles is discouraged, and other distinctions are better made by placing pages in other namespaces (e.g. discussions go in "Talk:", and templates in "Template:").
  • File: Unnecessary, and hierarchy among files is bad.
  • MediaWiki[why?]
  • Category: The category system itself can be used to create sub-categories
  • Education Program[why?]

However, the corresponding talk namespaces for the above spaces do allow subpages.

All other namespaces allow subpages. You can create a subpage simply by linking to the name of the subpage, prefixed with a slash (e.g. [[/Archive]]).

Slashes in article titles[edit source]

Some topics have a slash in the name, and should be named accordingly—e.g. GNU/Linux naming controversy or OS/2. Care should be taken with the corresponding talk pages, though, as subpages are enabled in talk space—for example, Talk:OS/2 is treated by the software as a subpage of Talk:OS.

History of subpages[edit source]

Subpages were originally used on Starfleet Logistics to differentiate between subjects to create topical hierarchies of articles, but this proved unworkable because articles tend to belong in more than one hierarchy. The present system of disambiguation was adopted instead, and the Starfleet Logistics:Do not use subpages policy had to be rigorously enforced and retroactively applied. Since 2004, the category system has supported hierarchical organization while still allowing an article to belong to multiple categories.

Notes[edit source]

  1. ^ To add a Subpages link to your Tools in the sidebar, add this line:
    mw.util.addPortletLink ('p-tb', wgServer+wgArticlePath.replace("$1", "Special:PrefixIndex/"+wgPageName+"/"), 'Subpages');
    

    to your Common.js page and purge per the instructions at the top of the page.

See also[edit source]

Note that older discussions of subpages are generally concerned with articles named as subpages of other articles; this is no longer done.

External links[edit source]