Help:Style: Difference between revisions

From Alpine Linux
m (moved heading)
(fixed sentence and heading levels to make it easier to read)
Line 1: Line 1:
To achieve a consistent look and feel across all pages of Alpine Linux wiki, editors are requested to follow the below style guidelines as much as possible. This page only deals with the common conventions to be followed, as there are specific pages like [[Help:Editing]] and [[Help:Cheatsheet]] for the technical aspects.  
To achieve a consistent look and feel across all pages of Alpine Linux wiki, editors are requested to follow the below style guidelines as much as possible. This page only deals with the common conventions to be followed, as there are specific pages like [[Help:Editing]] and [[Help:Cheatsheet]] for the technical aspects.  


To avoid content fragmentation and for easier maintenance of wiki, it is important to follow the guideline '''Do Not Repeat Yourself'''. At all times, place the content in the most appropriate page or section and add reference from other pages.
== Page layout ==


== Page layout and organization ==
For consistency across the wiki, article pages follow certain layout and organization guidelines. See [[How to write a HOWTO#Sample page layout|sample page layout]] for a complete example.


A wiki page needs the following elements:
A wiki page needs the following mandatory elements:


* [[#Page title|Page title]]
* [[#Page title|Page title]]
* [[#Magic words|Magic words]](optional)
* Table of contents (automatically generated)
* [[#Version and status tags|Status tags]](recommended)
* [[#"Introduction" section|Introduction section]]
* [[#"Introduction" section|Introduction section]]
* [[#Section headings|Additional sections]]
* [[#Section headings|Section headings]]
* [[#Category|Category]]
 
The following are optional elements:
 
* [[#Magic words|Magic words]]
* [[#Metadata|Metadata]]
* [[#"See also" section|See also section]]
* [[#"See also" section|See also section]]
* [[#"Category" section|Category section]]


== Page title ==
== Mandatory elements ==
 
=== Page title ===


* Page titles should use [https://en.wikipedia.org/wiki/Letter_case#Sentence_case sentence case].  
Page titles should use [https://en.wikipedia.org/wiki/Letter_case#Sentence_case sentence case]. Avoid including '''Alpine Linux''' in page titles, as it is mostly redundant in this wiki.
* Avoid including '''Alpine Linux''' as it is mostly redundant in this wiki.


== Magic words ==
=== "Introduction" section ===  


[https://www.mediawiki.org/wiki/Help:Magic_words Magic words] are optional. If used, they should go at the very beginning of articles. Commonly used magic word is {{ic|<nowiki>{{DISPLAYTITLE:title}}</nowiki>}}, to alter how an article title is displayed, like in [[dwm]] page.
Every page should begin with an introductory lead section – a concise summary of the article – which is never divided into sections. The remainder of the article is typically divided into sections.


== Version and status tags ==
=== Section headings ===


Editors are strongly encouraged to include version or status tags like [[:Template:Verified]], [[:Template:Obsolete]] or [[:Template:Accuracy]] at the page or section level, especially when writing new articles or updating existing ones. These  helps users to quickly see the relevance of the page.
Use standard headings like Prerequisite, Installation, Configuration and Troubleshooting to organize information as shown in [[How to write a HOWTO#Sample page layout|sample page]].


* Use [[:Template:Pill]] to provide visual clarity
Follow the formatting guidelines given in [[#Page title|Page title]] for section headings too. Start headings at level 2, as first-level heading is implicitly used for page title. Don't skip levels.
* Use [[:Template:Pill_clickable]] for linking to release notes or references


These templates can be used at page level or section level or even at a specific line of a wiki page, depending on their relevance.
=== Category ===


== "Introduction" section ==
Every article page should have at least one [[Help:Editing#categories|category]] from among the [[Special:Categories|categories list]]. They must be placed at the bottom of the page.


Every page should begin with an introductory lead section – a concise summary of the article – which is never divided into sections. The remainder of the article is typically divided into sections.
== Optional elements ==
 
=== Magic words ===
 
The optional [https://www.mediawiki.org/wiki/Help:Magic_words Magic words], if used, should be placed as the first entry in the wiki page. They can be used to alter how an article title, Table of Contents(TOC) are displayed.
 
=== Metadata ===
 
Metadata like version or status tags help users to quickly see the relevance of the page.
 
Status tags like [[:Template:Verified]], [[:Template:Obsolete]] or [[:Template:Accuracy]] can be added at the page or section level, especially when writing new articles or updating existing ones.  


== Section headings ==
Version information can be added using [[:Template:Pill]] to provide visual clarity or [[:Template:Pill_clickable]] for linking to release notes or references. These can be used at page level or section level or even at a specific line of a wiki page, depending on their relevance.


* Follow the guidelines given in [[#Page title|Page title]] for section headings too.
=== "See also" section ===
* Start headings at level 2, as first-level heading is used for page title.
* Don't skip levels.
* Use standard headings like Prerequisite,Installation and Configuration to organize information as shown in [[How to write a HOWTO#Sample page layout|sample page]].
* Currently numbered headings are not enabled in Alpine wiki. Since the current css doesn't clearly differentiate between heading levels like H3,H4,H5 etc..i.e beyond H2, do not create too many levels and instead use H2 level if needed for clarity.


== "See also" section ==
Use '''See also''' section for placing both internal wikilinks and external [[#Links|links]] that are relevant to the page.


Make [[Help:Editing#Links|links]] only where they are relevant and helpful in the context: Excessive use of hyperlinks can be distracting and may slow the reader down. Add links only that are worth pursuing.
== Content guidelines ==


Check links: Ensure the destination is the intended one and test them.
=== General principles ===


External links should not normally be used in the body of an article and instead use '''See also''' section for placing them in addition to relevant internal wikilinks. Add external links with discretion. Do not use wiki for self-promotion.
When adding or editing content, place it in the most appropriate page or section and add reference from other pages. New pages must be created sparingly, i.e., only if it is absolutely needed. Updating existing wiki pages benefits existing wikilinks.  


== "Category" section ==
Pay proper attention to name new pages as changing the name of pages in the wiki is not trivial. Adding or editing section headings must be done with care, as they can be linked within the page and from other wiki pages.


Every page should be assigned at least one [[Help:Editing#categories|category]] from among the [[Special:Categories|categories list]] by placing them at the bottom of the page.
Refer to existing wiki pages for standard tasks like [[installation]], [[Setting_up_disks_manually#Manual partitioning|partitioning]], [[Setting_up_disks_manually#Formatting_partitions|formatting]], [[Setting_up_a_new_user#Creating_a_new_user|user management]], [[Repositories#Managing_repositories|managing repositories]] etc. This avoids confusing users and prevents content fragmentation.  


== Code and commands ==
=== Code and commands ===


To ensure clarity, standardized visual style, and proper handling of characters, editors must use the available templates like [[:Template:Cmd]], [[:Template:Cat]] etc for all technical elements like code and commands. [[HTML Entities|HTML]] elements like <nowiki><Pre></nowiki> should be used sparingly. The Templates subsection of [[Help:Cheatsheet]] page lists commonly used [[Special:AllPages/Template|Templates]].
To ensure clarity, standardized visual style, and proper handling of characters, editors should make use of Alpine Linux wiki specific templates listed in [[Help:Cheatsheet]]. [[HTML Entities|HTML]] elements should be used sparingly.  


== Tables and lists  ==
=== Tables and lists  ===


[[Help:Editing#Tables|Tables]] are effective in presenting a summary or overview or when listing rows of information. Avoid using a table and instead use lists if there are only few rows as table markup often complicates page editing.  
[[Help:Editing#Tables|Tables]] are effective in presenting a summary or overview or when listing rows of information. Avoid using a table and instead use lists if there are only few rows as table markup often complicates page editing.  
Line 72: Line 80:
** the sequence of the items is critical;
** the sequence of the items is critical;


== Transclusion ==
=== Links ===
 
Use [[Help:Editing#Links|links]] only where they are relevant and helpful in the context: Excessive use of hyperlinks can be distracting and may slow the reader down.


Use [[Help:Editing#Transclusion|transclusion]] for content that may be required in multiple pages. To quickly identify such pages, title such pages with '''Include:''' in front of the regular title. For eg: [[Include:Setup-desktop]]. Add adequate notice to editors using the standard html comment syntax.
External links should not normally be used in the body of an article and instead place them in [[#"See also" section|"See also" section]] in addition to internal wikilinks. Exercise care when adding external links. Do not use the wiki for self-promotion.


Use Transclusion sparingly as they can easily break pages and viewing the same content in multiple page can be confusing for readers. Consider creating a regular page and link to it instead, if applicable.  
Check links and ensure that the destination is the intended one.


== User pages ==
=== Transcluded pages ===


User pages are subpages in the User namespace like [[Special:Mypage/|User:Username/]]. These pages are meant to keep personal notes, references or for drafting and the above instructions are not applicable for them.  
Use [[Help:Editing#Transclusion|transclusion]] for content needed in multiple pages. To quickly identify such pages, add '''Include:''' in front of the regular title (e.g., [[Include:Setup-desktop]]).


* Do not add category to User pages.
Use transclusion sparingly, as inappropriate placement can break pages or confuse readers. If possible, consider using a regular page and linking to it instead.
* Do not add [[Help:Editing#Redirect|redirect links]] to User pages from Main namespace.
* Note that user pages are not part of default wiki search.
* Do not use article-specific templates like [[:Template:Draft]], [[:Template:Obsolete]], or [[:Template:Todo]] etc on your user pages unless you are testing the templates itself.


== See also ==
== User pages ==


* [[How to write a HOWTO#Sample page layout|Sample page]]
User pages are subpages in the User namespace like [[Special:Mypage/|User:Username/]]. These pages are meant to keep personal notes, references or for drafting and the above instructions are not applicable for them. Do not add a category or [[Help:Editing#Redirect|redirect links]] to User pages from Main namespace. Note that user pages are not part of default search.
* [https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style Wikipedia Manual of Style]
* [https://wiki.archlinux.org/title/Help:Style Archwiki Help:Style]


[[Category:Wiki]]
[[Category:Wiki]]

Revision as of 18:02, 13 December 2025

To achieve a consistent look and feel across all pages of Alpine Linux wiki, editors are requested to follow the below style guidelines as much as possible. This page only deals with the common conventions to be followed, as there are specific pages like Help:Editing and Help:Cheatsheet for the technical aspects.

Page layout

For consistency across the wiki, article pages follow certain layout and organization guidelines. See sample page layout for a complete example.

A wiki page needs the following mandatory elements:

The following are optional elements:

Mandatory elements

Page title

Page titles should use sentence case. Avoid including Alpine Linux in page titles, as it is mostly redundant in this wiki.

"Introduction" section

Every page should begin with an introductory lead section – a concise summary of the article – which is never divided into sections. The remainder of the article is typically divided into sections.

Section headings

Use standard headings like Prerequisite, Installation, Configuration and Troubleshooting to organize information as shown in sample page.

Follow the formatting guidelines given in Page title for section headings too. Start headings at level 2, as first-level heading is implicitly used for page title. Don't skip levels.

Category

Every article page should have at least one category from among the categories list. They must be placed at the bottom of the page.

Optional elements

Magic words

The optional Magic words, if used, should be placed as the first entry in the wiki page. They can be used to alter how an article title, Table of Contents(TOC) are displayed.

Metadata

Metadata like version or status tags help users to quickly see the relevance of the page.

Status tags like Template:Verified, Template:Obsolete or Template:Accuracy can be added at the page or section level, especially when writing new articles or updating existing ones.

Version information can be added using Template:Pill to provide visual clarity or Template:Pill_clickable for linking to release notes or references. These can be used at page level or section level or even at a specific line of a wiki page, depending on their relevance.

"See also" section

Use See also section for placing both internal wikilinks and external links that are relevant to the page.

Content guidelines

General principles

When adding or editing content, place it in the most appropriate page or section and add reference from other pages. New pages must be created sparingly, i.e., only if it is absolutely needed. Updating existing wiki pages benefits existing wikilinks.

Pay proper attention to name new pages as changing the name of pages in the wiki is not trivial. Adding or editing section headings must be done with care, as they can be linked within the page and from other wiki pages.

Refer to existing wiki pages for standard tasks like installation, partitioning, formatting, user management, managing repositories etc. This avoids confusing users and prevents content fragmentation.

Code and commands

To ensure clarity, standardized visual style, and proper handling of characters, editors should make use of Alpine Linux wiki specific templates listed in Help:Cheatsheet. HTML elements should be used sparingly.

Tables and lists

Tables are effective in presenting a summary or overview or when listing rows of information. Avoid using a table and instead use lists if there are only few rows as table markup often complicates page editing.

Lists can be either bulleted or numbered.

  • Do not use lists if a passage is read easily as plain paragraphs.
  • Use numbers rather than bullets only if:
    • a need to refer to the elements by number may arise;
    • the sequence of the items is critical;

Links

Use links only where they are relevant and helpful in the context: Excessive use of hyperlinks can be distracting and may slow the reader down.

External links should not normally be used in the body of an article and instead place them in "See also" section in addition to internal wikilinks. Exercise care when adding external links. Do not use the wiki for self-promotion.

Check links and ensure that the destination is the intended one.

Transcluded pages

Use transclusion for content needed in multiple pages. To quickly identify such pages, add Include: in front of the regular title (e.g., Include:Setup-desktop).

Use transclusion sparingly, as inappropriate placement can break pages or confuse readers. If possible, consider using a regular page and linking to it instead.

User pages

User pages are subpages in the User namespace like User:Username/. These pages are meant to keep personal notes, references or for drafting and the above instructions are not applicable for them. Do not add a category or redirect links to User pages from Main namespace. Note that user pages are not part of default search.