Xfce Wiki

Sub domains
 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
contribute:documentation:creating_new_pages [2026/09/16 00:04] – kevinbowencontribute:documentation:creating_new_pages [2026/09/16 01:33] (current) – kevinbowen
Line 1: Line 1:
 ~~NOTOC~~ ~~NOTOC~~
-====== Formatting guidelines for new documentation/wiki pages ======+====== Formatting Guidelines for New Pages ======
  
   * **[[#Use the NOTOC header|Use the NOTOC header]]**   * **[[#Use the NOTOC header|Use the NOTOC header]]**
Line 8: Line 8:
   * **[[#Creating back-links|Creating back-links]]**   * **[[#Creating back-links|Creating back-links]]**
  
-Most documentation contributions to docs.xfce.org and the wiki consist of small edits or modifications to specific sections of the documentation. 
  
-If a new page is needed, it is important to keep its layout and appearance consistant with the rest of the documentation.+If a new documentation, or wiki page is needed, it is important to keep its layout and appearance consistant with the rest of the documentation.
  
 Below are some guidelines to use when creating a new documentation page. Below are some guidelines to use when creating a new documentation page.
Line 20: Line 19:
 Use the control macro ''<nowiki>~~NOTOC~~</nowiki>'' at the very top of the page in the editing window. Use the control macro ''<nowiki>~~NOTOC~~</nowiki>'' at the very top of the page in the editing window.
 This is a internal Dokuwiki control macro that will disable the autogeneration of a list in the sidebar. If a document becomes long enough, it is recommended to manually create and maintain a table of contents within the body of the documentation page. See also [[:wiki:syntax#sectioning|Sectioning syntax]]. This is a internal Dokuwiki control macro that will disable the autogeneration of a list in the sidebar. If a document becomes long enough, it is recommended to manually create and maintain a table of contents within the body of the documentation page. See also [[:wiki:syntax#sectioning|Sectioning syntax]].
- 
-As a rule of thumb, if a page becomes longer than a screen and has multiple sections, it is recommended to manually create a table of contents. 
  
 ---- ----
  
 ===== Creating a Table of Contents ===== ===== Creating a Table of Contents =====
 +
 +As a general rule, if a page becomes longer than one visual screen, and has multiple sections, it is recommended to manually create a table of contents.
  
 Using the [[:start|Main Docs.xfce.org page]] as an example, we have a table of contents consisting of three main sections Using the [[:start|Main Docs.xfce.org page]] as an example, we have a table of contents consisting of three main sections
Line 35: Line 34:
 </code> </code>
  
-[[|Back to Top]]+Each link refers to a main header further down the page. 
 ---- ----
  
 ===== Using horizontal rules ===== ===== Using horizontal rules =====
  
-3. Use a horizontal rule for breaking up sections of a page. +Use a horizontal rule for breaking up sections of a page. 
-A horizontal rule is created by using ''<nowiki>----</nowiki>''(four dashes) in between two blank lines. Be sure to check your preview before saving to ensure that the divider properly renders.+A horizontal rule is created by using 
 +<code> 
 +---- 
 +</code> 
 +(four dashes) in between two blank lines. Be sure to preview your changes before saving to ensure that the divider properly renders.
  
 +[[|Back to Top]]
 ---- ----
  
 ===== Using Back to Top links ===== ===== Using Back to Top links =====
  
-3. If a section is long enough and the top of the page scrolls far beyond the top of the screen, insert the code ''<nowiki>[[|Back to Top]]</nowiki>'' followed by a horizontal rule to allow the reader to return back to the top of page and the table of contents. This is not a strict rule and would depend on how large a section. If there are a number of small sections on one screen, a "Back to Top" is not neccessarily needed for each section. This is a bit of a judgement call required on the part of the editor to strike a balance between a reader's useability of the page and cluttering the page with unneeded links.+'Back to Top' links are used on Xfce's documentation pages as a navigational aid for readers on documentation pages that are larger than a few sentences. 
 + 
 +If a section is long enough and the top of the page scrolls far beyond the top of the screen, insert the code ''<nowiki>[[|Back to Top]]</nowiki>'' followed by a horizontal rule to allow the reader to return back to the top of page and the table of contents.  
 + 
 +<code> 
 + 
 +[[|Back to Top]] 
 +---- 
 + 
 +</code> 
 + 
 +This is not a strict rule and would depend on how large a section. If there are a number of small sections on one screen, a "Back to Top" is not neccessarily needed for each section. This is a bit of a judgement call required on the part of the editor to strike a balance between a reader's useability of the page and cluttering the page with unneeded links. 
 + 
 +----
  
 ===== Creating back-links ===== ===== Creating back-links =====
  
-4.At the bottom of the page, if it makes sense, create one or two back-links to the main page. For example, on the [[:xfce:thunar:thunar-archive-plugin:bugs|Thunar-archive-plugin bugs]] page, there are two backlinks included at the bottom of the page. One returns the user to the subsection on the thunar archive plugin, and the second goes back to the main thunar page. This is coded in the editing window, as follows:+At the bottom of the page, if it makes sense, create one or two back-links to the main page. For example, on the [[:xfce:thunar:thunar-archive-plugin:bugs|Thunar-archive-plugin bugs]] page, there are two backlinks included at the bottom of the page. One returns the user to the subsection on the thunar archive plugin, and the second goes back to the main thunar page. This is coded in the editing window, as follows:
  
 <code> <code>