Toolbox: Difference between revisions
(→Add an introductory screenshot and description: Working and cooler way.) |
(remove deprecated markup) |
||
Line 5: | Line 5: | ||
==Deciding where to create your page== | ==Deciding where to create your page== | ||
Many people choose to draft a page on their own Talk page, then move the result to the desired site. Sometimes there is a good reason for preferring to do it in the final location. If that is the case, consider using before your content <nowiki>{{Construction}}</nowiki> which will display | Many people choose to draft a page on their own Talk page, then move the result to the desired site. Sometimes there is a good reason for preferring to do it in the final location. If that is the case, consider using before your content <nowiki>{{Construction}}</nowiki> which will display | ||
{{Construction}} | |||
===Directory Structure=== | |||
Try to avoid creating a structure more than three levels deep. For most purposes, the following guide will suffice: | |||
Application | |||
Application/Troubleshooting | |||
Application/xxx-How-To | |||
Application/Manual | |||
Application/Manual/Introduction | |||
Application/Manual/Section_1 | |||
Application/Manual/Section_xxx | |||
==Do not add an i18n language bar== | ==Do not add an i18n language bar== | ||
Line 14: | Line 24: | ||
|} | |} | ||
New pages should not have this language bar. It related to the old style of translation and will not work with page translation extension. | New pages should not have this language bar. It related to the old style of translation and will not work with page translation extension. The new style language bar will be added by the software when the first translation is made. | ||
==Add an introductory screenshot and description== | ==Add an introductory screenshot and description== | ||
Whenever possible we begin an application's top-level page with this. The code to achieve it is | Whenever possible we begin an application's top-level page with this. The code to achieve it is | ||
<pre style="background: | <pre style="background:lemonchiffon"> | ||
{| | {| | ||
|[[Image:YourScreenshot.png|250px|thumb]] | |[[Image:YourScreenshot.png|250px|thumb]] | ||
|Your descriptive text | |Your descriptive text | ||
Line 50: | Line 60: | ||
===Add indents=== | ===Add indents=== | ||
:':' is used for an indent, and | :':' is used for an indent, and was used in multiples in some old pages. This is deprecated, and causes some problems, so the multiples will be removed as they are found. A single ':' indents by four characters. | ||
===Lists, numbered and bulleted=== | ===Lists, numbered and bulleted=== | ||
:<nowiki>*</nowiki> is the symbol to use for bulletted lists. ** gives a second level: | :<nowiki>*</nowiki> is the symbol to use for bulletted lists. ** gives a second level: | ||
<nowiki> | <nowiki> | ||
:* One star | |||
:* Next point | |||
:** Sub-point | |||
:* Third point</nowiki> | |||
:produces | :produces | ||
:* One star | |||
:* Next point | |||
:** Sub-point | |||
:* Third point | |||
:Numbered lists are produced in the same way, using '#'. | :Numbered lists are produced in the same way, using '#'. | ||
Line 71: | Line 81: | ||
<nowiki> | <nowiki> | ||
:# A single hash | |||
:# Second point | |||
:## A sub-point | |||
:# Third point</nowiki> | |||
:produces | :produces | ||
:# A single hash | |||
:# Second point | |||
:## A sub-point | |||
:# Third point | |||
:This is less useful than the bulletted list. | :This is less useful than the bulletted list. | ||
Line 122: | Line 132: | ||
===Use tables to precisely place multiple images=== | ===Use tables to precisely place multiple images=== | ||
<div style="white-space:pre;"> | <div style="white-space:pre;"> | ||
:{|style="width: | :{|style="width:95%; border:2px dotted #BCBCBC; background:lemonchiffon" align="center" | ||
|<nowiki>{| | |<nowiki>{|class=tablecenter | ||
|[[Image:Desktop-config-customized.png|230px|center]]||[[Image:Desktop-settings-rightclick.png|230px|center]] | |[[Image:Desktop-config-customized.png|230px|center]]||[[Image:Desktop-settings-rightclick.png|230px|center]] | ||
|- | |- | ||
Line 133: | Line 143: | ||
:displays | :displays | ||
:{| | :{|class=tablecenter | ||
|[[Image:Desktop-config-customized.png|230px|center]]||[[Image:Desktop-settings-rightclick.png|230px|center]] | |[[Image:Desktop-config-customized.png|230px|center]]||[[Image:Desktop-settings-rightclick.png|230px|center]] | ||
|- | |- | ||
Line 141: | Line 151: | ||
:Note that all the parameters for one image are contained within <nowiki>[[...]]</nowiki>, and cells are separated by '||'. To start a new line, insert '|-' | :Note that all the parameters for one image are contained within <nowiki>[[...]]</nowiki>, and cells are separated by '||'. To start a new line, insert '|-' on an otherwise-empty line, then '|' at the start of the next one. | ||
==Add Notes and Warnings== | ==Add Notes and Warnings== | ||
Where a note or warning is relevant within your text, use a table, like these: | Where a note or warning is relevant within your text, use a table, like these: | ||
{|style="width:80%; border:2px dotted #BCBCBC; background: | {|style="width:80%; border:2px dotted #BCBCBC; background:lemonchiffon" align="center" | ||
|<nowiki> | |<nowiki> | ||
:{| | |||
|[[Image:Im-status-message-edit.png]]||'''Note'''||Some important information | |[[Image:Im-status-message-edit.png]]||'''Note'''||Some important information | ||
|} | |} | ||
Line 154: | Line 164: | ||
|} | |} | ||
:{| | |||
|[[Image:Im-status-message-edit.png]]||'''Note'''||Some important information | |[[Image:Im-status-message-edit.png]]||'''Note'''||Some important information | ||
|} | |} | ||
{|style="width: | {|style="width:95%; border:2px dotted #BCBCBC; background:lemonchiffon" align="center" | ||
|<nowiki> | |<nowiki> | ||
:{| | |||
|[[Image:help-hint.png]]||'''Tip'''||Something useful to remember | |[[Image:help-hint.png]]||'''Tip'''||Something useful to remember | ||
|} | |} | ||
Line 166: | Line 176: | ||
|} | |} | ||
:{| | |||
|[[Image:help-hint.png]]||'''Tip'''||Something useful to remember | |[[Image:help-hint.png]]||'''Tip'''||Something useful to remember | ||
|} | |} | ||
{|style="width:95%; border:2px dotted #BCBCBC;background:lemonchiffon " align="center" | |||
{|style="width: | |<nowiki>:{| | ||
|<nowiki> | |||
|[[Image:dialog-warning.png|32px]]||'''Warning'''||This is dangerous | |[[Image:dialog-warning.png|32px]]||'''Warning'''||This is dangerous | ||
|} | |} | ||
Line 179: | Line 187: | ||
|} | |} | ||
:{| | |||
|[[Image:dialog-warning.png|32px]]||'''Warning'''||This is dangerous | |[[Image:dialog-warning.png|32px]]||'''Warning'''||This is dangerous | ||
|} | |} | ||
Line 194: | Line 202: | ||
{{warning|This is a very dangerous thing to do}} | {{warning|This is a very dangerous thing to do}} | ||
==KDE3 and KDE SC 4 versions of applications== | ==KDE3 and KDE SC 4 versions of applications== | ||
Line 218: | Line 224: | ||
{{Being_Edited}} | {{Being_Edited}} | ||
''Don't forget to remove it when you have finished!'' | |||
===Adding a new complex page=== | ===Adding a new complex page=== |
Revision as of 15:25, 28 August 2010
Template:I18n/Language Navigation Bar
This page offers examples of formatting code for common tasks
Deciding where to create your page
Many people choose to draft a page on their own Talk page, then move the result to the desired site. Sometimes there is a good reason for preferring to do it in the final location. If that is the case, consider using before your content {{Construction}} which will display
Directory Structure
Try to avoid creating a structure more than three levels deep. For most purposes, the following guide will suffice:
Application Application/Troubleshooting Application/xxx-How-To Application/Manual Application/Manual/Introduction Application/Manual/Section_1 Application/Manual/Section_xxx
Do not add an i18n language bar
{{Template:I18n/Language Navigation Bar|Toolbox}} |
New pages should not have this language bar. It related to the old style of translation and will not work with page translation extension. The new style language bar will be added by the software when the first translation is made.
Add an introductory screenshot and description
Whenever possible we begin an application's top-level page with this. The code to achieve it is
{| |[[Image:YourScreenshot.png|250px|thumb]] |Your descriptive text |}
Format your text
Use Headings
- Headings automatically form part of your Table of Contents, so need to be structured. Their place in the tree is governed by multiple '=' characters at each end of the heading. Avoid using a single one - that denotes a page heading, and the automatic page heading should be used. Your major headings will use '==text goes here==', the next level, '===more text===' and so on.
Use bold and italic
- Blips are used to specify bold and italic words.
- Use '''bold text''' to specify bold text and
- ''italic text'' to specify italic text.
- In order to ensure we get easy and accurate translations, please adhere to the typographical guidelines.
Add a code snippet
- We distinguish code that the user inputs from terminal output by the use of templates. {{Input|1=this piece of code is input by the user}} displays
this piece of code is input by the user
- Code output by a terminal is shown similarly, using {{Output|1=the user would read this in konsole}} which displays as
the user would read this in konsole
- Be aware that very long lines can be problematic. Wherever possible display the code in reasonably short lines.
Add indents
- ':' is used for an indent, and was used in multiples in some old pages. This is deprecated, and causes some problems, so the multiples will be removed as they are found. A single ':' indents by four characters.
Lists, numbered and bulleted
- * is the symbol to use for bulletted lists. ** gives a second level:
:* One star :* Next point :** Sub-point :* Third point
- produces
- One star
- Next point
- Sub-point
- Third point
- Numbered lists are produced in the same way, using '#'.
:# A single hash :# Second point :## A sub-point :# Third point
- produces
- A single hash
- Second point
- A sub-point
- Third point
- This is less useful than the bulletted list.
Add a link
There are two kinds of links to learn, internal ones, to another userbase page, and external URL links.
For an internal link the format [[PageLayout]], where you want to display the name of the page, does work, but it is not ideal, particularly for translation to docbook. It is better to use the form [[PageLayout|Page Layout]], as it avoids problems at the translator stage. You often need to include the link in a sentence, so in that case you would use
[[PageLayout|this page]]
which displays
External links are slightly different so
[http://techbase.kde.org/Schedules our road map]
displays
our road map, which would take you straight to the techbase page.
One last thing to note - when you preview your page, the links are live. This gives you two benefits. You can check (by hovering) that your links are set up as you expected, and you can use a red link to create a new page.
Illustrate your text
Add a single image, centered
[[Image:KMail-kde4.png|250px|center]]
- Note that you can change the position of the image, but the default is left. The size of the image depends on the circumstances, but for screenshots I recommend no less than 250px and no more than 500px.
- Where you need to show more detail, create a moderately sized image, clickable, so that the full-size can be seen. Simply add the parameter '|thumb' within the image parentheses.
- A caption can also be added as a parameter, but will only show if '|thumb' is present.
Use tables to precisely place multiple images
{|class=tablecenter |[[Image:Desktop-config-customized.png|230px|center]]||[[Image:Desktop-settings-rightclick.png|230px|center]] |- |[[Image:Desktop-theme-details-dialog.png|230px|center]]||[[Image:Plasma-multiple-themes.png|230px|center]] |}
- displays
- Note that all the parameters for one image are contained within [[...]], and cells are separated by '||'. To start a new line, insert '|-' on an otherwise-empty line, then '|' at the start of the next one.
Add Notes and Warnings
Where a note or warning is relevant within your text, use a table, like these:
:{| |[[Image:Im-status-message-edit.png]]||'''Note'''||Some important information |} |
:{| |[[Image:help-hint.png]]||'''Tip'''||Something useful to remember |} |
:{| |[[Image:dialog-warning.png|32px]]||'''Warning'''||This is dangerous |} |
Where a note or warning is important enough to need to stand out strongly there are two useful templates, Info and Warning. Use
{{info|This is another way to display your information}}
or
{{warning|This is a very dangerous thing to do}}
KDE3 and KDE SC 4 versions of applications
By default, KDE SC 4 is assumed. If the KDE SC 4 version is not yet ready for release it may be necessary to document the KDE3 version. In this case you should add an icon {{KDE3}} which displays . Should you be writing about a KDE3 version and KDE SC 4 version on the same page, use icons for both - {{KDE4}} which displays
Useful Templates
Community Applications
The final consideration concerns those applications which are not distributed as core KDE applications. These need to be indicated by an icon, placing {{Community-app}}
at the end of your sentence or line, just as you would to denote a footnote in general writing. You then need to add {{Community-app-footnote}} which will create a footnote, like this:
Support for this application can be found from the project's home page
Making major edits to Existing Pages
If a page is likely to be open for editing for some time there is a danger of conflicts - someone else may edit at the same time, and saving your edit will cancel out theirs, or vice versa. The way to avoid that is to make a temporary entry, directly under the language bar, using {{Being_Edited}} which will display
Don't forget to remove it when you have finished!
Adding a new complex page
If you need to be able to work on a page for quite some time, over several days, for instance, you may like to use the Construction template - {{Construction}}, which displays
Adding a List of Sub-Pages
== Subpages of {{FULLPAGENAME}} == {{Special:PrefixIndex/{{FULLPAGENAME}}/}}
is very useful when you want to list subpages with active links, such as