ERP EnterprisePLUS [E+] - User contributions [en]

File:LEADing Practice - Best Practice & Tips & Tricks .pdf

2020-03-03T10:02:44Z

Ufo:

== Licensing ==
{{[[LEADing Practice IP::LEADing Practice IP]] }}

Organizational Rule

2019-01-24T11:47:27Z

Ufo: Created page with "{{#lead-mw-content: MetaObjectDescriptions|getPageContent|{{FULLPAGENAME}} }} === Reference Content === *Enterprise_Standards:Strategy_Management_Reference_Content|Strategy..."

{{#lead-mw-content: MetaObjectDescriptions|getPageContent|{{FULLPAGENAME}} }}

=== Reference Content ===
*[[Enterprise_Standards:Strategy_Management_Reference_Content|Strategy Management Reference Content]]
*[[Enterprise_Standards:Growth%3A_Core_Differentiating_%26_Core_Competitive_Reference_Content|Growth: Core Differentiating & Core Competitive Reference Content]]
*[[Enterprise_Standards:Performance_Management_Reference_Content|Performance Management Reference Content]]
*[[Enterprise_Standards:Planning_Management_Reference_Content|Planning Management Reference Content]]
*[[Enterprise_Standards:Production_Management_Reference_Content|Production Management Reference Content]]
*[[Enterprise_Standards:Portfolio_Management_Reference_Content|Portfolio Management Reference Content]][[Category:Objects Inner]]

Help:Links

2019-01-11T08:16:30Z

Ufo:

There are five types of hypertext links in Knowledge Management system:

<ol><li>Internal links to other pages in the same Knowledge Management system (commonly called "Knowledge Management system links")</li>
<li>External links to pages at other websites</li>
<li>External links to internal pages in the same Knowledge Management system</li>
<li>Interlanguage links to other Knowledge Management systems registered as different language versions of the current Knowledge Management system</li></ol>

Please note that this list does not include category links and file links, which are used to place pages into categories and display images or other media files, respectively.

===Internal links===

{|
<table border="1" class="wikitable">
<tr style="
">
<th style="text-align: center;padding: 10px">Description
</th>
<th style="text-align: center;">You type
</th>
<th style="text-align: center;">You get
</th></tr>
<tr>
<td>Internal link
</td>
<td><pre>[[Main Page]]

</pre>
</td>
<td>
Main Page


</td></tr>
<tr>
<td>Piped link
</td>
<td><pre>[[Help:Editing pages|editing help]]

[[Help:Editing pages#Preview|previewing]]</pre>

</td>
<td>
[[Need_help]]
[[previewing]]

</td></tr>
<tr>

<td><pre>

[[User:John Doe|]]

</pre>
The pipe trick involves less typing for editors, but is potentially confusing to readers, as seen in these DynamicPageList examples.

</td>
<td>
[[Extensions]]
[[User:John Doe]]

</td></tr>

<tr>
<td>Redirect
</td>
<td><pre>#REDIRECT [[Main Page]]</pre>
Should be the first and only line on the page.

</td>
<td><img alt="Redirect arrow without text (cropped).svg" src="//upload.wikimedia.org/wikipedia/commons/thumb/7/7f/Redirect_arrow_without_text_%28cropped%29.svg/19px-Redirect_arrow_without_text_%28cropped%29.svg.png" width="19" height="17" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/7/7f/Redirect_arrow_without_text_%28cropped%29.svg/29px-Redirect_arrow_without_text_%28cropped%29.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/7/7f/Redirect_arrow_without_text_%28cropped%29.svg/38px-Redirect_arrow_without_text_%28cropped%29.svg.png 2x" data-file-width="19" data-file-height="17"> [[Main Page]]
</td></tr>

<tr>
<td>Setting an anchor for incoming links
</td>
<td><pre><div id="Unique anchor name 1">optional text</div>

optional text
</pre>
Rendered lock-level and inline, respectively.
Doing this would allow for <code>[[#Unique anchor name 1]]</code> on the same page or <code>[[Help:Links#Unique anchor name 1]]</code> on a different page.
Omit the "optional text" for an invisible anchor.

</td>
<td>
<div id="Unique_anchor_name_1">optional text</div>
optional text

</td></tr>
<tr>
<td>Setting an anchor in a section heading
</td>
<td><pre>==Section heading==</pre>
Note the placement.
This must be a "span" tag, not a "div".
(Such anchors allow sections to be retitled without breaking incoming links.)

</td>
<td><div style="color: #000000; background: none; overflow: hidden; page-break-after: avoid; font-size: 1.5em; font-family: Georgia,Times,serif; margin-top: 1em; margin-bottom: 0.25em; line-height: 1.3; padding: 0; border-bottom: 1px solid #AAAAAA;">Section heading</div>
</td></tr>
<tr>
<td>Link to an anchor at another page
</td>
<td><pre>[[Help:Images#Supported media types for images]]</pre>
</td>
<td>[[Help:Images]]#Supported media types for images
</td></tr>
<tr>
<td>Link to the current page's talk page
</td>
<td><pre>[[{{TALKPAGENAME}}|Discussion]]</pre>

</td>
<td>[[Help:links]] Discussion
</td></tr>

<tr>
<td>Visible link to a category page
</td>
<td><pre>[[:Category:Help]]</pre>

</td>
</tr>
<tr>
<td>Visible link to an image or media file
</td>
<td id="file-links"><pre>[[:File:Example.jpg]]

[[:File:Example.jpg|this example]]

[[Media:Example.jpg]]
</pre>
Without the leading colon on the "File:" examples, the images would actually be displayed.
See also [[Help:Images]]
The <code><code class="mw-highlight" dir="ltr">Media:</code></code> prefix is used to link directly to the uploaded file, rather than the file-information page.

</td>
<td>
[[File:Example.jpg]]
[[File:Example.jpg]]this example

</td></tr>
<tr>
<td>Link to a page specific to each reader (user page, etc.)
</td>
<td><pre>[[Special:MyPage]]

[[Special:MyTalk]]

[[Special:Preferences]]
</pre>
</td>
<td>
[[Special:MyPage]]
[[Special:MyTalk]]
[[Special:Preferences]]

</td></tr>

</table>
|}

===External links===

To create an external link, usually to a page at a different website, enclose the URL followed by space and the link text in single square brackets (see examples below). When you save or preview the page, you will see a link rendered slightly differently than an internalKnowledge Management system link. It may be a different color and/or be followed by an arrow icon to show that it may lead to another site.

<table class="wikitable">
<tr>
<th style="width:15%;text-align: center;padding: 10px">Description
</th>
<th style="width:45%;text-align: center;">You type
</th>
<th style="width:40%;text-align: center;">You get
</th></tr>
<tr>
<td>External link with specified link text
</td>
<td><pre>[https://enterpriseplus.tools E+]</pre>
</td>
<td>[[enterpriseplus.tools]]
</td></tr>
<tr>
<td>Numbered external link
</td>
<td><pre>[https://enterpriseplus.tools]</pre>
This is what happens if you omit the link text.
Multiple links of this type on the same page are numbered sequentially.

</td>
<td>[1]
</td></tr>
<tr>
<td>Bare external link
</td>
<td><pre>https://www.enterpriseplus.tools</pre>
URLs beginning with "<code>http://</code>" and "<code>https://</code>" are automatically linked, even when no brackets are used.

</td>
<td>https://enterpriseplus.tools
</td></tr>
<tr>
<td>Avoiding auto-linked URLs
</td>
<td><pre><nowiki>https://enterpriseplus.tools</nowiki></pre>
</td>
<td>https://enterpriseplus.tools
</td></tr>

<tr>
<td>External link to the current server
</td>
<td><pre>https://{{SERVERNAME}}/pagename</pre>
</td>
<td>[[https://enterpriseplus.tools/pagename]]
</td></tr>
<tr>
<td>External link to other host passing the pagename
</td>

<td>[[https://google.com/search?q=Links]]
</td></tr>
<tr>
<td>Mailto link
</td>
<td><pre>[mailto:info@example.com email me]</pre>
</td>
</tr>
<tr>
<td>Mailto named with subject line and body
</td>
<td><pre>[mailto:info@example.com?Subject=URL%20Encoded%20Subject&body=Body%20Text info]</pre>
</td>
</tr>

</table>

===External links to internal pages===

To add a link to a page on the sameKnowledge Management systemusing URL query parameters, you may need to use external link syntax.

<table border="1" class="wikitable">
<tr>
<th style="text-align: center;padding: 10px">Description
</th>
<th style="text-align: center;">You type
</th>
<th style="text-align: center;">You get
</th></tr>
<tr>
<td>External link to the current page's edit page
</td>
<td><pre>[https://www.enterpriseplus.tools/index.php?title=Help:Links&action=edit Edit this page]

[{{fullurl:{{FULLPAGENAME}}|action=edit}} Edit this page]
</pre>

</td>
<td>
[{{fullurl:{{FULLPAGENAME}}|action=edit}} Edit this page]
[{{fullurl:{{FULLPAGENAME}}|action=edit}} Edit this page]
</td></tr>
<tr>
<td>External link to the current page's edit page, and styled to look like an internal link
</td>
<td><pre>[{{fullurl:{{FULLPAGENAME}}|action=edit}} Edit this page]</pre>
The plainlinks class can be used in cases where you want an external link to look like an internal one, by suppressing the icon that normally appears after it.

</td>
<td>[{{fullurl:{{FULLPAGENAME}}|action=edit}} Edit this page]
</td></tr></table>

===Limits===

An internal Knowledge Management system link is limited by maximum page title size.

Normal and sysop users cannot permanently delete a Knowledge Management system page, but sysops can delete a page such that it could still be restored. This is a deliberate design feature, and is an important part of why Knowledge Management system's work. Every kind of editing operation can be reverted by any other user, and that includes resurrecting deleted content. It doesn't cause significant wasted space; and with nothing but a 'delete' label, the page is effectively deleted anyway.

Deleting a page is, on the other hand, a straightforward operation for anyone with sysop permissions: it allows to semi-permanently remove a page from the Knowledge Management system, until a sysop undeletes (restores) it with the same ease. Typically sysops might look for delete labels, and do a proper delete on these pages, after a period of time. If for some reason you need a page to be deleted more quickly than that, you will need to contact a sysop to request this.

Revision deletion offers a more granular feature of deletion for edits with peculiar problems.

===Before deleting===

Sysops should also be aware of the general advice given on When not to delete a page: in particular, there are many situations where a deletion is too drastic. For example, a redirect is often more appropriate.

Before deleting you could perform various checks:

*'''Use the "What links here" tool. This gives an indication as to how important a page is, and what subjects it relates to. Perhaps the page is still linked to prominently from many places. All incoming links will become red links if you proceed with the delete. Ideally all incoming links should be changed/removed, if there is genuinely no need for this page to exist. You could do this work prior to deleting, or ask others in the Knowledge Management system community to do it.
*'''Check the page history and the associated talk page. Who was proposing the deletion? Does anyone disagree? Has it been properly discussed? Did people have adequate time to raise objections? Did somebody vandalize a page, which then led to a deletion proposal?

The care taken over these things might depend on the size of the Knowledge Management system community, and how clear-cut the case for deletion is. Remember that only sysop users can undo a delete action, so to a normal user the information appears to be lost forever.

===Use the 'delete' action===

Sysops should see a 'delete' tab or action menu option at the top of every page. To find the action menu, look for a down arrow or triangle next to the "View History" tab. If you mouse over the triangle you should see "delete", "move", "protect" and "watch". Click the delete action to delete the page. When using browsers which support keyboard shortcuts, you can also use (Control-Alt-D). You will be asked to confirm, and to supply a "Reason for deletion". This is a short textual description of why the page is being deleted. Your action will appear on the recent changes display, and in the deletion log ([[Special:Log]]).

Remember only the administrator can delete uploaded photograph files.

===Undeleting===

To undelete a page you must navigate to the exact page name of the page.
You should then see a link to "View or restore n deleted edits". Tick the box next to the revision you wish to restore.

===Configuring deletion reasons===
The list of reasons in the dropdown box is maintained at [[Help:Deletereason-dropdown]].

===When not to delete a page===

Typically you would delete a page if the contents are entirely inappropriate and do not match the purposes of the Knowledge Management system. In other situations, you would take a less extreme course of action, for example:

*'''The page should have a different title. See [[Help:Moving a page]].
*'''The contents should have been placed on a different page -- Add the contents to the other page, and then supply a redirect. See Help:Redirects.
*'''The contents are already on a different page -- Delete the duplicate content and leave a redirect. That way, the page title, which made sense to somebody, will helpfully redirect to the information.
*'''The page is out-of-date -- Re-word sentences to be in the past tense, to make the page a historical record. Alternatively, label the information as out-of-date, with a warning notice.

An actual delete is generally necessary only if the title of the page is inappropriate. In other situations, a merge and redirect is more appropriate.

===Proposing changes===

Deciding on appropriate content/page titles can be a difficult aspect of Knowledge Management system organization, and one which can often provoke debates. If the merge or deletion you have in mind is one which might cause upset, you should propose the change first. Do this by leaving a note to give your reasons on the talk page. You might also establish a system for labeling the page with a delete/merge proposal template, to make everybody aware of your intentions.

===Unlinking a page===

The 'What links here' toolbox feature (bottom of left sidebar) will tell you which other Knowledge Management system pages link to the current page. Always use this feature to check before proceeding with deleting. These related pages will need to be edited for their links to reflect the change.

*'''[[Help:Starting a new page]]
*'''[[Help:Moving a page]]
*'''[[Help:Admin deleting and undeleting]]
*'''[[Help:Formating]]
*'''[[Help:Links]]
*'''[[Help:List]]
*'''[[Help:Images]]
*'''[[Help:Tables]]

Help:Tables

2019-01-11T08:14:02Z

Ufo:

Tables may be created in Knowledge Management systempages.
As a general rule, it is best to avoid using a table unless you need one.
Table markup often complicates page editing.


<h2>Knowledge Management systemtable markup summary</h2>
<table class="wikitable" style="width:60%">
<tr>
<td style="padding: 10px;"><big>{|</big>
</td>
<td style="padding: 5px;">table start, required
</td></tr>
<tr>
<td style="padding: 10px;"><big>|+</big>
</td>
<td style="padding: 5px;">table caption, optional; only between table start and table row
</td></tr>
<tr>
<td style="padding: 10px;"><big>|-</big>
</td>
<td style="padding: 5px;">table row, optional on first row—Knowledge Management systemengine assumes the first row
</td></tr>
<tr>
<td style="padding: 10px;"><big>!</big>
</td>
<td style="padding: 5px;">table header cell, optional. Consecutive table header cells may be added on same line separated by double marks (<code>!!</code>) or start on new lines, each with its own single mark (<code>!</code>).
</td></tr>
<tr>
<td style="padding: 10px;"><big>|</big>
</td>
<td style="padding: 5px;">table data cell, optional. Consecutive table data cells may be added on same line separated by double marks (<code>||</code>) or start on new lines, each with its own single mark (<code>|</code>).
</td></tr>
<tr>
<td style="padding: 10px;"><big>|}</big>
</td>
<td style="padding: 5px;">table end, required
</td></tr></table>
<ul><li>The above marks must start on a new line except the double <code>||</code> and <code>!!</code> for optionally adding consecutive cells to a line. However, blank spaces at the beginning of a line are ignored.</li>
<li>HTML attributes. Each mark, except table end, optionally accepts one or more HTML attributes. Attributes must be on the same line as the mark. Separate attributes from each other with a single space.
<ul><li>Cells and caption (<code>|</code> or <code>||</code>, <code>!</code> or <code>!!</code>, and <code>|+</code>) hold content. So separate any attributes from content with a single pipe (<code>|</code>). Cell content may follow on same line or on following lines.</li>
<li>Table and row marks (<code>{|</code> and <code>|-</code>) do not directly hold content. Do not add pipe (<code>|</code>) after their optional attributes. If you erroneously add a pipe after attributes for the table mark or row mark the parser will delete it and your final attribute if it was touching the erroneous pipe!</li></ul></li>
<li>Content may (a) follow its cell mark on the same line after any optional HTML attributes or (b) on lines below the cell mark. Content that uses Knowledge Management systemmarkup that itself needs to start on a new line, such as lists, headings, or nested tables, must be on its own new line.
<ul><li>Pipe character as content. To insert a pipe (<code>|</code>) character into a table, use the <nowiki><code>|</code></nowiki> escaping markup.</li></ul></li></ul>
<h2>Basics</h2>
The following table lacks borders and good spacing but shows the simplest Knowledge Management systemmarkup table structure.

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{|
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream
|}
</pre>
</td>
<td style="padding: 5px;">
<table>
<tr>
<td>Orange
</td>
<td>Apple
</td></tr>
<tr>
<td>Bread
</td>
<td>Pie
</td></tr>
<tr>
<td>Butter
</td>
<td>Ice cream
</td></tr></table>
</td></tr></table>
The cells in the same row can be listed on one line separated by <code>||</code> (two pipe symbols).
If the text in the cell should contain a line break, use <code> </code> instead.

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{|
|Orange||Apple||more
|-
|Bread||Pie||more
|-
|Butter||Ice cream||and more
|}
</pre>
</td>
<td style="padding: 5px;">
<table>
<tr>
<td>Orange</td>
<td>Apple</td>
<td>more
</td></tr>
<tr>
<td>Bread</td>
<td>Pie</td>
<td>more
</td></tr>
<tr>
<td>Butter</td>
<td>Ice cream</td>
<td>and more
</td></tr></table>
</td></tr></table>
Extra spaces within cells in the Knowledge Management systemmarkup, as in the Knowledge Management systemmarkup below, do not affect the actual table rendering.

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{|
| Orange || Apple || more
|-
| Bread || Pie || more
|-
| Butter || Ice cream || and more
|}
</pre>
</td>
<td style="padding: 5px;">
<table>
<tr>
<td>Orange</td>
<td>Apple</td>
<td>more
</td></tr>
<tr>
<td>Bread</td>
<td>Pie</td>
<td>more
</td></tr>
<tr>
<td>Butter</td>
<td>Ice cream</td>
<td>and more
</td></tr></table>
</td></tr></table>
You can have longer text or more complex Knowledge Management systemsyntax inside table cells, too:

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{|
|Lorem ipsum dolor sit amet,
consetetur sadipscing elitr,
sed diam nonumy eirmod tempor invidunt
ut labore et dolore magna aliquyam erat,
sed diam voluptua.

At vero eos et accusam et justo duo dolores
et ea rebum. Stet clita kasd gubergren,
no sea takimata sanctus est Lorem ipsum
dolor sit amet.
|
* Lorem ipsum dolor sit amet
* consetetur sadipscing elitr
* sed diam nonumy eirmod tempor invidunt
|}
</pre>
</td>
<td style="padding: 5px;">
<table>
<tr>
<td>Lorem ipsum dolor sit amet,
consetetur sadipscing elitr,
sed diam nonumy eirmod tempor invidunt
ut labore et dolore magna aliquyam erat,
sed diam voluptua.
At vero eos et accusam et justo duo dolores
et ea rebum. Stet clita kasd gubergren,
no sea takimata sanctus est Lorem ipsum
dolor sit amet.

</td>
<td>
<ul><li>Lorem ipsum dolor sit amet</li>
<li>consetetur sadipscing elitr</li>
<li>sed diam nonumy eirmod tempor invidunt</li></ul>
</td></tr></table>
</td></tr></table>
<h3>Table headers</h3>
Table headers can be created by using "<code>!</code>" (exclamation mark) instead of "<code>|</code>" (pipe symbol).
Headers usually show up bold and centered by default.

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{|
! style="text-align:left;"| Item
! Amount
! Cost
|-
|Orange
|10
|7.00
|-
|Bread
|4
|3.00
|-
|Butter
|1
|5.00
|-
!Total
|
|15.00
|}
</pre>
</td>
<td style="padding: 5px;">
<table>
<tr>
<th style="text-align:left;">Item
</th>
<th>Amount
</th>
<th>Cost
</th></tr>
<tr>
<td>Orange
</td>
<td>10
</td>
<td>7.00
</td></tr>
<tr>
<td>Bread
</td>
<td>4
</td>
<td>3.00
</td></tr>
<tr>
<td>Butter
</td>
<td>1
</td>
<td>5.00
</td></tr>
<tr>
<th>Total
</th>
<td>
</td>
<td>15.00
</td></tr></table>
</td></tr></table>
Note: When using attributes as in the heading 'Item' a vertical bar '|' is used for separation.
Not an exclamation character '!'.

<h3>Caption</h3>
A table caption can be added to the top of any table as follows.

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{|
|+Food complements
|-
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream
|}
</pre>
</td>
<td style="padding: 5px;">
<table>
<caption>Food complements
</caption>
<tr>
<td>Orange
</td>
<td>Apple
</td></tr>
<tr>
<td>Bread
</td>
<td>Pie
</td></tr>
<tr>
<td>Butter
</td>
<td>Ice cream
</td></tr></table>
</td></tr></table>
<h3>class="wikitable"</h3>
Basic styling (light gray background, borders, padding and align left) can be achieved by adding class="wikitable".

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{| class="wikitable"
|+Food complements
|-
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream
|}
</pre>
</td>
<td style="padding: 5px;">
<table class="wikitable">
<caption>Food complements
</caption>
<tr>
<td>Orange
</td>
<td>Apple
</td></tr>
<tr>
<td>Bread
</td>
<td>Pie
</td></tr>
<tr>
<td>Butter
</td>
<td>Ice cream
</td></tr></table>
</td></tr></table>
<h3>HTML colspan and rowspan</h3>
You can use HTML colspan and rowspan attributes on cells for advanced layout.

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{| class="wikitable"
!colspan="6"|Shopping List
|-
|rowspan="2"|Bread & Butter
|Pie
|Buns
|Danish
|colspan="2"|Croissant
|-
|Cheese
|colspan="2"|Ice cream
|Butter
|Yogurt
|}
</pre>
</td>
<td style="padding: 5px;">
<table class="wikitable">
<tr>
<th colspan="6">Shopping List
</th></tr>
<tr>
<td rowspan="2">Bread & Butter
</td>
<td>Pie
</td>
<td>Buns
</td>
<td>Danish
</td>
<td colspan="2">Croissant
</td></tr>
<tr>
<td>Cheese
</td>
<td colspan="2">Ice cream
</td>
<td>Butter
</td>
<td>Yogurt
</td></tr></table>
</td></tr></table>
 

<h2>HTML attributes</h2>
You can add HTML attributes to tables.
For the authoritative source on HTML attributes, see [https://www.w3.org/TR/html401/struct/tables.html the W3C's HTML Specification page on tables].

<h3>Attributes on tables</h3>
Placing attributes after the table start tag (<code>{|</code>) applies attributes to the entire table.

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{| class="wikitable" style="text-align: center; color: green;"
|Orange
|Apple
|12,333.00
|-
|Bread
|Pie
|500.00
|-
|Butter
|Ice cream
|1.00
|}
</pre>
</td>
<td style="padding: 5px;">
<table class="wikitable" style="text-align: center; color: green;">
<tr>
<td>Orange
</td>
<td>Apple
</td>
<td>12,333.00
</td></tr>
<tr>
<td>Bread
</td>
<td>Pie
</td>
<td>500.00
</td></tr>
<tr>
<td>Butter
</td>
<td>Ice cream
</td>
<td>1.00
</td></tr></table>
</td></tr></table>
<h3>Attributes on cells</h3>
You can put attributes on individual cells.
For example, numbers may look better aligned right.

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{| class="wikitable"
| Orange
| Apple
| style="text-align:right;" | 12,333.00
|-
| Bread
| Pie
| style="text-align:right;" | 500.00
|-
| Butter
| Ice cream
| style="text-align:right;" | 1.00
|}
</pre>
</td>
<td style="padding: 5px;">
<table class="wikitable" style="text-align:center">
<tr>
<td>Orange
</td>
<td>Apple
</td>
<td style="text-align:right;">12,333.00
</td></tr>
<tr>
<td>Bread
</td>
<td>Pie
</td>
<td style="text-align:right;">500.00
</td></tr>
<tr>
<td>Butter
</td>
<td>Ice cream
</td>
<td style="text-align:right;">1.00
</td></tr></table>
</td></tr></table>
You can also use cell attributes when you are listing multiple cells on a single line.
Note that the cells are separated by <code>||</code>, and within each cell the attribute(s) and value are separated by <code>|</code>.

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{| class="wikitable"
| Orange || Apple || style="text-align:right;" | 12,333.00
|-
| Bread || Pie || style="text-align:right;" | 500.00
|-
| Butter || Ice cream || style="text-align:right;" | 1.00
|}
</pre>
</td>
<td style="padding: 5px;">
<table class="wikitable">
<tr>
<td>Orange</td>
<td>Apple</td>
<td style="text-align:right;">12,333.00
</td></tr>
<tr>
<td>Bread</td>
<td>Pie</td>
<td style="text-align:right;">500.00
</td></tr>
<tr>
<td>Butter</td>
<td>Ice cream</td>
<td style="text-align:right;">1.00
</td></tr></table>
</td></tr></table>
<h3>Attributes on rows</h3>
You can put attributes on individual rows, too.

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{| class="wikitable"
| Orange
| Apple
| style="text-align:right;"| 12,333.00
|-
| Bread
| Pie
| style="text-align:right;"| 500.00
|- style="font-style: italic; color: green;"
| Butter
| Ice cream
| style="text-align:right;"| 1.00
|}
</pre>
</td>
<td style="padding: 5px;">
<table class="wikitable">
<tr>
<td>Orange
</td>
<td>Apple
</td>
<td style="text-align:right;">12,333.00
</td></tr>
<tr>
<td>Bread
</td>
<td>Pie
</td>
<td style="text-align:right;">500.00
</td></tr>
<tr style="font-style: italic; color: green;">
<td>Butter
</td>
<td>Ice cream
</td>
<td style="text-align:right;">1.00
</td></tr></table>
</td></tr></table>
<h3>Simple one-pixel table border</h3>
An example of a one-pixel table border:

<table style="width:100%">

<tr>
<th style="width:50%">You type
</th>
<th style="width:50%">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{| border="1" style="border-collapse:collapse"
| Orange
| Apple
|-
| Bread
| Pie
|}
</pre>
</td>
<td style="padding: 20px;">
<table border="1" style="border-collapse:collapse">
<tr>
<td>Orange
</td>
<td>Apple
</td></tr>
<tr>
<td>Bread
</td>
<td>Pie
</td></tr></table>
</td></tr></table>
<h3>Border width</h3>
If "border-width:" has only one number, it is for all four border sides:

<table style="width:100%">

<tr>
<th style="width:50%">You type
</th>
<th style="width:50%">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{|style="border-style: solid; border-width: 20px"
|
Hello
|}
</pre>
</td>
<td style="padding: 20px;">
<table style="border-style: solid; border-width: 20px">
<tr>
<td>
Hello

</td></tr></table>
</td></tr></table>
If "border-width:" has more than one number, the four numbers are for top, right, bottom, left (REMEMBER this order):

<table style="width:100%">

<tr>
<th style="width:50%">You type
</th>
<th style="width:50%">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{|style="border-style: solid; border-width: 10px 20px 100px 0"
|
Hello
|}
</pre>
</td>
<td style="padding: 20px;">
<table style="border-style: solid; border-width: 10px 20px 100px 0">
<tr>
<td>
Hello

</td></tr></table>
</td></tr></table>
<dl><dd>When there are fewer than 4 values, the value for left takes its default from the value for right, the value for bottom takes its default from the value for top, and the value for right takes its default from the value for top.</dd></dl>
Another method to define the widths of the four sides of a cell is to use "border-left", "border-right", "border-top" and "border-bottom":

<div style="width: 100%; overflow:auto;">
<table style="width:100%">

<tr>
<th style="width:50%">You type
</th>
<th style="width:50%">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{|style="border-left:solid 10px black;border-right:solid 20px black;border-top:solid 30px black;border-bottom:solid 40px black;" align="center"
|
Hello
|}
</pre>
</td>
<td style="padding: 20px;">
<table style="border-left:solid 10px black;border-right:solid 20px black;border-top:solid 30px black;border-bottom:solid 40px black;" align="center">
<tr>
<td>
Hello

</td></tr></table>
</td></tr></table>
</div>
<div role="note" class="note note-info" style="background-position:left 7px top 50%; padding-right: 0.5em; padding-left: 40px;">
The HTML attributes (such as "width=", "border=", "cellspacing=", "cellpadding=") do not need any length unit (the pixel unit is assumed). They are also invalid in HTML 5. 
"Cellpadding" is the Set the space between the cell wall and the cell content.

The CSS style properties (which override the HTML attributes) require an explicit length unit (if the value is not 0) such as "px" for the pixel.</div>
<h3>With HTML attributes and CSS styles</h3>
<p?CSS style attributes can be added with or without other HTML attributes.

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10"
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream
|}
</pre>
</td>
<td style="padding: 5px;">
<table class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10">
<tr>
<td>Orange
</td>
<td>Apple
</td></tr>
<tr>
<td>Bread
</td>
<td>Pie
</td></tr>
<tr>
<td>Butter
</td>
<td>Ice cream
</td></tr></table>
</td></tr></table>
<h3>Padding</h3>
<table style="width:100%;">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr valign="top">
<td style="padding:10px;">
<pre>{|class=wikitable
| style="padding:10px;" | style="padding:10px;"
|-
| style="padding:50px;" | style="padding:50px;" Specify the padding on '''EACH CELL'''
|-
| style="padding:100px;" | style="padding:100px;"
|}
</pre>
</td>
<td>
<table class="wikitable">
<tr>
<td style="padding:10px;">Example of style="padding:10px;"
</td></tr>
<tr>
<td style="padding:50px;">Example of style="padding:50px;" Specify the padding on EACH CELL
</td></tr>
<tr>
<td style="padding:100px;">example of style="padding:100px;"
</td></tr></table>
</td></tr></table>
<h4>Attributes</h4>
Attributes can be added to the caption and headers as follows.

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{| class="wikitable"
|+ style="caption-side:bottom; color:#e76700;"|''Food complements''
|-
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream
|}
</pre>
</td>
<td style="padding: 5px;">
<table class="wikitable">
<caption style="caption-side:bottom; color:#e76700;">Food complements
</caption>
<tr>
<td>Orange
</td>
<td>Apple
</td></tr>
<tr>
<td>Bread
</td>
<td>Pie
</td></tr>
<tr>
<td>Butter
</td>
<td>Ice cream
</td></tr></table>
</td></tr></table>
<h4>Column width</h4>
Column width can be added as follows.
You type:

<pre>{| style="color: black; background-color: #ffffcc; width: 85%;"
| colspan="2" | This column width is 85% of the screen width (and has a background color)
|-
| style="width: 30%; background-color: white;"|
'''This column is 30% counted from 85% of the screen width'''
| style="width: 70%; background-color: orange;"|
'''This column is 70% counted from 85% of the screen width (and has a background color)'''
|}
</pre>
You get:

<table style="color: black; background-color: #ffffcc; width: 85%;">
<tr>
<td colspan="2">This column width is 85% of the screen width (and has a background color)
</td></tr>
<tr>
<td style="width: 30%; background-color: white;">This column is 30% counted from 85% of the screen width
</td>
<td style="width: 70%; background-color: orange;">This column is 70% counted from 85% of the screen width (and has a background color)
</td></tr></table>
 

<h3>Accessibility of table header cells</h3>
Table header cells do not explicitly specify which table data cells they apply to (those on their right on the same row, or those below them on the same column).
When the table is rendered in a visual 2D environment, this is usually easy to infer.
However when tables are rendered on non-visual media, you can help the browser to determine which table header cell applies to the description of any selected cell (in order to repeat its content in some accessibility helper) using a scope="row" or scope="col" attribute on table header cells.
In most cases with simple tables, you'll use scope="col" on all header cells of the first row, and scope="row" on the first cell of the following rows:

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{| class="wikitable"
|-
! scope="col"| Item
! scope="col"| Quantity
! scope="col"| Price
|-
! scope="row"| Bread
| 0.3 kg
| $0.65
|-
! scope="row"| Butter
| 0.125 kg
| $1.25
|-
! scope="row" colspan="2"| Total
| $1.90
|}
</pre>
</td>
<td style="padding: 5px;">
<table class="wikitable">

<tr>
<th scope="col">Item
</th>
<th scope="col">Quantity
</th>
<th scope="col">Price
</th></tr>
<tr>
<th scope="row">Bread
</th>
<td>0.3 kg
</td>
<td>$0.65
</td></tr>
<tr>
<th scope="row">Butter
</th>
<td>0.125 kg
</td>
<td>$1.25
</td></tr>
<tr>
<th scope="row" colspan="2">Total
</th>
<td>$1.90
</td></tr></table>
</td></tr></table>
 

<h2>Alignment</h2>
<h3>Table alignment</h3>
Table alignment is achieved by using CSS.
The table alignment is controlled by margins.
A fixed margin on one side will make the table to be aligned to that side, if on the opposite side the margin is defined as auto.
To have a table center aligned, you should set both margins to auto
For example, a right-aligned table:

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{| class="wikitable" style="margin-left: auto; margin-right: 0px;"
| Orange
| Apple
|-
| Bread
| Pie
|-
| Butter
| Ice cream
|}
</pre>
</td>
<td style="padding: 5px;">
<table class="wikitable" style="margin-left: auto; margin-right: 0px;">
<tr>
<td>Orange
</td>
<td>Apple
</td></tr>
<tr>
<td>Bread
</td>
<td>Pie
</td></tr>
<tr>
<td>Butter
</td>
<td>Ice cream
</td></tr></table>
</td></tr></table>
And a center-aligned table:

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{| class="wikitable" style="margin: auto;"
| Orange
| Apple
|-
| Bread
| Pie
|-
| Butter
| Ice cream
|}
</pre>
</td>
<td style="padding: 5px;">
<table class="wikitable" style="margin: auto;">
<tr>
<td>Orange
</td>
<td>Apple
</td></tr>
<tr>
<td>Bread
</td>
<td>Pie
</td></tr>
<tr>
<td>Butter
</td>
<td>Ice cream
</td></tr></table>
</td></tr></table>
<h3>Table floating around text</h3>
If you align a table to the right or the left side of the page, the text that comes after the table starts at the end of it, leaving an empty space around the table.
You can make the text to be wrapped around the table by making the table to float around the text instead of just aligning it.
This can be achieved using the <code>float</code> CSS attribute, which can specify where the table floats to the right side or to the left.
When using float, margins doesn't control table alignment and can be used to specify the margin between the table and the surrounding text.

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{| class="wikitable" style="float:right; margin-left: 10px;"
| Orange
| Apple
|-
| Bread
| Pie
|-
| Butter
| Ice cream
|}

Lorem ipsum dolor sit amet, consectetuer adipiscing
elit, sed diam nonummy nibh euismod tincidunt ut
laoreet dolore magna aliquam erat volutpat. Ut wisi
enim ad minim veniam, quis nostrud exerci tation
ullamcorper suscipit lobortis nisl ut aliquip ex ea
commodo consequat. Duis autem vel eum iriure dolor
in hendrerit in vulputate velit esse molestie consequat,
vel illum dolore eu feugiat nulla facilisis at vero
eros et accumsan et iusto odio dignissim qui blandit
praesent luptatum zzril delenit augue duis dolore te
feugait nulla facilisi.
</pre>
</td>
<td style="padding: 5px;">
<table class="wikitable" style="float:right; margin-left: 10px;">
<tr>
<td>Orange
</td>
<td>Apple
</td></tr>
<tr>
<td>Bread
</td>
<td>Pie
</td></tr>
<tr>
<td>Butter
</td>
<td>Ice cream
</td></tr></table>
Lorem ipsum dolor sit amet, consectetuer adipiscing
elit, sed diam nonummy nibh euismod tincidunt ut
laoreet dolore magna aliquam erat volutpat. Ut wisi
enim ad minim veniam, quis nostrud exerci tation
ullamcorper suscipit lobortis nisl ut aliquip ex ea
commodo consequat. Duis autem vel eum iriure dolor
in hendrerit in vulputate velit esse molestie consequat,
vel illum dolore eu feugiat nulla facilisis at vero
eros et accumsan et iusto odio dignissim qui blandit
praesent luptatum zzril delenit augue duis dolore te
feugait nulla facilisi.

</td></tr></table>
<h3>Cell contents alignment</h3>
The alignment of cell contents can be controlled with 2 different CSS properties: <code>text-align</code> and <code>vertical-align</code>.
<code>text-align</code> can be specified at the table, row or individual cells, while <code>vertical-align</code> only can be specified at individual rows or cells.

<table style="width:100%">
<tr>
<th style="width: 50%;">You type
</th>
<th style="width: 50%;">You get
</th></tr>
<tr>
<td style="padding: 5px;">
<pre>{| class="wikitable"
|- style="vertical-align:top;"
| style="height:100px; width:100px; text-align:left;" | A
| style="height:100px; width:100px; text-align:center;" | B
| style="height:100px; width:100px; text-align:right;" | C
|- style="vertical-align:middle;"
| style="height:100px; width:100px; text-align:left;" | D
| style="height:100px; width:100px; text-align:center;" | E
| style="height:100px; width:100px; text-align:right;" | F
|- style="vertical-align:bottom;"
| style="height:100px; width:100px; text-align:left;" | G
| style="height:100px; width:100px; text-align:center;" | H
| style="height:100px; width:100px; text-align:right;" | I
|}
</pre>
</td>
<td style="padding: 5px;">
<table class="wikitable">

<tr style="vertical-align:top;">
<td style="height:100px; width:100px; text-align:left;">A
</td>
<td style="height:100px; width:100px; text-align:center;">B
</td>
<td style="height:100px; width:100px; text-align:right;">C
</td></tr>
<tr style="vertical-align:middle;">
<td style="height:100px; width:100px; text-align:left;">D
</td>
<td style="height:100px; width:100px; text-align:center;">E
</td>
<td style="height:100px; width:100px; text-align:right;">F
</td></tr>
<tr style="vertical-align:bottom;">
<td style="height:100px; width:100px; text-align:left;">G
</td>
<td style="height:100px; width:100px; text-align:center;">H
</td>
<td style="height:100px; width:100px; text-align:right;">I
</td></tr></table>
</td></tr></table>
<h2>Caveats</h2>
<h3>Negative numbers</h3>
If you start a cell on a new line with a negative number with a minus sign (or a parameter that evaluates to a negative number), your table can get broken, because the characters <code>|-</code> will be parsed as the Knowledge Management systemmarkup for table row, not table cell.
To avoid this, insert a space before the value (<code>| -6</code>) or use in-line cell markup (<code>|| -6</code>).

<h3>CSS vs attributes</h3>
Table borders specified through CSS rather than the border attribute will render incorrectly in a small subset of text browsers.

<h3>Common attributes for columns, column groups and row groups</h3>
The Knowledge Management system syntax for tables currently offers no support for specifying common attributes for columns (with the HTML element <code><col /></code>), column groups (HTML element <code><colgroup></colgroup></code>) and row groups (HTML elements <code><thead></thead></code>, <code><tbody></tbody></code> and <code><tfoot></tfoot></code>).
Those standard HTML elements are not accepted even in their HTML or XHTML syntax.
All the rows and cells (header or data) of the table are rendered within a single implicit row group (HTML element <code><tbody></tbody></code>) without any attributes or styles.


<h2>Notes</h2>
<div class="mw-references-wrap"><ol class="references">
<li id="cite_note-1"><Jump up ↑ Tables can be created using either HTML table elements directly, or usingKnowledge Management system code formatting to define the table.
HTML table elements and their use are well described on various web pages and will not be discussed here.
The benefit ofKnowledge Management system code is that the table is constructed of character symbols which tend to make it easier to perceive the table structure in the article editing view compared to HTML table elements.
</li>
<li id="cite_note-2">Jump up ↑ [https://www.w3schools.com/tags/att_table_cellpadding.asp HTML table cellpadding Attribute]
</li>
</ol></div>




Normal and sysop users cannot permanently delete a Knowledge Management system page, but sysops can delete a page such that it could still be restored. This is a deliberate design feature, and is an important part of why Knowledge Management system's work. Every kind of editing operation can be reverted by any other user, and that includes resurrecting deleted content. It doesn't cause significant wasted space; and with nothing but a 'delete' label, the page is effectively deleted anyway.

Deleting a page is, on the other hand, a straightforward operation for anyone with sysop permissions: it allows to semi-permanently remove a page from the Knowledge Management system, until a sysop undeletes (restores) it with the same ease. Typically sysops might look for delete labels, and do a proper delete on these pages, after a period of time. If for some reason you need a page to be deleted more quickly than that, you will need to contact a sysop to request this.

Revision deletion offers a more granular feature of deletion for edits with peculiar problems.

===Before deleting===

Sysops should also be aware of the general advice given on When not to delete a page: in particular, there are many situations where a deletion is too drastic. For example, a redirect is often more appropriate.

Before deleting you could perform various checks:

*'''Use the "What links here" tool. This gives an indication as to how important a page is, and what subjects it relates to. Perhaps the page is still linked to prominently from many places. All incoming links will become red links if you proceed with the delete. Ideally all incoming links should be changed/removed, if there is genuinely no need for this page to exist. You could do this work prior to deleting, or ask others in the Knowledge Management system community to do it.
*'''Check the page history and the associated talk page. Who was proposing the deletion? Does anyone disagree? Has it been properly discussed? Did people have adequate time to raise objections? Did somebody vandalize a page, which then led to a deletion proposal?

The care taken over these things might depend on the size of the Knowledge Management system community, and how clear-cut the case for deletion is. Remember that only sysop users can undo a delete action, so to a normal user the information appears to be lost forever.

===Use the 'delete' action===

Sysops should see a 'delete' tab or action menu option at the top of every page. To find the action menu, look for a down arrow or triangle next to the "View History" tab. If you mouse over the triangle you should see "delete", "move", "protect" and "watch". Click the delete action to delete the page. When using browsers which support keyboard shortcuts, you can also use (Control-Alt-D). You will be asked to confirm, and to supply a "Reason for deletion". This is a short textual description of why the page is being deleted. Your action will appear on the recent changes display, and in the deletion log ([[Special:Log]]).

Remember only the administrator can delete uploaded photograph files.

===Undeleting===

To undelete a page you must navigate to the exact page name of the page.
You should then see a link to "View or restore n deleted edits". Tick the box next to the revision you wish to restore.

===Configuring deletion reasons===
The list of reasons in the dropdown box is maintained at [[Help:Deletereason-dropdown]].

===When not to delete a page===

Typically you would delete a page if the contents are entirely inappropriate and do not match the purposes of the Knowledge Management system. In other situations, you would take a less extreme course of action, for example:

*'''The page should have a different title. See [[Help:Moving a page]].
*'''The contents should have been placed on a different page -- Add the contents to the other page, and then supply a redirect. See Help:Redirects.
*'''The contents are already on a different page -- Delete the duplicate content and leave a redirect. That way, the page title, which made sense to somebody, will helpfully redirect to the information.
*'''The page is out-of-date -- Re-word sentences to be in the past tense, to make the page a historical record. Alternatively, label the information as out-of-date, with a warning notice.

An actual delete is generally necessary only if the title of the page is inappropriate. In other situations, a merge and redirect is more appropriate.

===Proposing changes===

Deciding on appropriate content/page titles can be a difficult aspect of Knowledge Management system organization, and one which can often provoke debates. If the merge or deletion you have in mind is one which might cause upset, you should propose the change first. Do this by leaving a note to give your reasons on the talk page. You might also establish a system for labeling the page with a delete/merge proposal template, to make everybody aware of your intentions.

===Unlinking a page===

The 'What links here' toolbox feature (bottom of left sidebar) will tell you which other Knowledge Management system pages link to the current page. Always use this feature to check before proceeding with deleting. These related pages will need to be edited for their links to reflect the change.

*'''[[Help:Starting a new page]]
*'''[[Help:Moving a page]]
*'''[[Help:Admin deleting and undeleting]]
*'''[[Help:Formating]]
*'''[[Help:Links]]
*'''[[Help:List]]
*'''[[Help:Images]]
*'''[[Help:Tables]]

Help:Images

2019-01-11T08:13:06Z

Ufo:

This page explains the image syntax when editing theKnowledge Management system. You or another user must usually upload an image before you can use it on a page.

Images that are stored on aKnowledge Management systemserver are usually rendered by using the File: namespace prefix (but the legacy Image: namespace prefix is still supported as a synonym) as the target of aKnowledge Management systemlink. The alternate Media: namespace prefix is also usable to reference the original media file content (for rendering or downloading it separately, out of anyKnowledge Management systempage).

===Supported media types for images===

The following file formats are supported by default:

<ul><li>.jpg or .jpeg : bitmap image compressed in the standard JPEG format (this lossy format is most suitable for photographs).</li>
<li>.png : bitmap image in the Portable Network Graphics format (specified by the W3 Consortium).</li>
<li>.gif : bitmap image in the legacy Graphics Interchange Format.</li></ul>

Other formats used onKnowledge Management systemmedia, and commonly enabled elsewhere (these may require extra set-up beyond what is enabled by default):

<ul><li>.svg : scalable image in the Scalable Vector Graphics format (specified by the W3 Consortium). </li>
<li>.tiff : Tagged image format. Often used for high-resolution archival photographs. Often used with </li>
<li>.ogg, .oga, .ogv : Ogg multimedia (audio or video). Not an image format, but treated similarly. Often used with </li>
<li>.pdf : multipaged documents in the Portable Document Format (initially specified by Adobe). Often used in conjunction with </li>
<li>.djvu : multipaged bitmap documents in the DejaVu format (most often, scans of books).
<dl><dd>Only a single page of a .pdf or .djvu file is shown at one time.</dd></dl></li></ul>

Only a single page of a .pdf or .djvu file is shown at one time.

Other media types may be supported, but it may not be possible to display them inline.

===Rendering a single image===

Syntax

The full syntax for displaying an image is:

<pre>[[File:filename.extension|options|caption]]
</pre>

where options can be zero or more of the following, separated by pipes (|):

<ul><li>Format option: one of border and/or frameless, frame, thumb (or thumbnail);
<dl><dd>Controls how the rendered image is formatted and embedded in the rest of the page.</dd></dl></li>
<li>Resizing option: one of
<ul><li>{width}px — Resizes the image to fit within the given maximum width in pixels, without restricting its height;</li>
<li>x{height}px — Resizes the image to fit within the given maximum height in pixels, without restricting its width;</li>
<li>{width}x{height}px — Resizes the image to fit within the given width and height in pixels;</li>
<li>upright — Resizes an image to fit within reasonable dimensions, according to user preferences (suitable for images whose height is larger than width).</li></ul>
<dl><dd>Note that the image will always retain its aspect ratio, and can only be reduced (not increased) in size unless it's in a scalable media type (bitmap images cannot be scaled up).</dd>
<dd>The default maximum size depends on the format and the internal image dimensions (according to its media type).</dd></dl></li>
<li>Horizontal alignment option: one of left, right, center, none;
<dl><dd>Controls the horizontal alignment (and inline/block or floating styles) of the image within a text (no default value).</dd></dl></li>
<li>Vertical alignment option: one of baseline, sub, super, top, text-top, middle, bottom, text-bottom;
<dl><dd>Controls the vertical alignment of a non-floating inline image with the text before or after the image, and in the same block (the default vertical alignment is middle).</dd></dl></li>
<li>Link option: one of
<ul><li>link={target} — Allows to change the target (to an arbitrary page title, or URL) of the generated link, activable on the rendered image surface; e.g. <code>[[File:Example.jpg|20px|link=http://www.wikipedia.org]]</code> renders as <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/20px-Example.jpg" width="20" height="13" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/30px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg 2x" data-file-width="400" data-file-height="267"> (external link), or <code>[[File:Example.jpg|20px|link=Knowledge Management system]]</code> renders as <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/20px-Example.jpg" width="20" height="13" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/30px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg 2x" data-file-width="400" data-file-height="267"> (internal link).</li>
<li>link= (with an empty value) — Displays an image without any activable link; e.g. <code>[[File:Example.jpg|20px|link=]]</code> renders as <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/20px-Example.jpg" width="20" height="13" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/30px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg 2x" data-file-width="400" data-file-height="267">.
<ul><li>! for MW 1.24 and lower: If you set <code>|link=|</code> (empty), then no <code>title</code> will be rendered. </li></ul></li></ul></li>
<li>Other specific options:
<ul><li>alt={alternative text} — Defines the alternative text (maps to the HTML attribute <code>alt="..."</code> of the generated <code><img /></code> element) of an image that will be rendered if either the referenced image cannot be downloaded and embedded, or if the support media must use the alternative description text (e.g. when using a Braille reader or with accessibility options set by the user in its browser).</li>
<li>page={number} — Renders the specified page number (currently only applicable when showing a .djvu or .pdf file).</li>
<li>class={html class} — (Knowledge Management system1.20+) Defines classes (maps to the HTML attribute <code>class="..."</code> of the generated <code><img /></code> element).</li>
<li>lang={language code} — (Knowledge Management system1.22+) For SVG files containing <switch> statements varying on a systemLanguage attribute, selects what language to render the file in. The default is always English, even on non-EnglishKnowledge Management systems.</li></ul></li></ul>

If a parameter does not match any of the other possibilities, it is assumed to be the caption text. Caption text shows below the image in thumb and frame formats, or as tooltip text in any other format. Caption text displayed in the thumb and frame formats may containKnowledge Management system links and other formatting.Knowledge Management systemextensions can add additional options.

If 'alt' is not specified and a caption is provided, the alternative text will be created automatically from the caption, stripped of formatting, except when in thumb or frame mode since the caption is already readable by screen readers in that case.

Format

The following table shows the effect of all available formats.

<table class="wikitable plainlinks">

<tr>
<th style="text-align:center;padding:10px">Description
</th>
<th style="text-align:center">You type
</th>
<th style="text-align:center">You get
</th></tr>
<tr>
<td>no format specified Rendered as a floating block: no Rendered inline: yes Rendered caption: no
</td>
<td>
<pre>... text text text
[[File:example.jpg|caption]]
text text text ...
</pre>
</td>
<td>... text text text
<img alt="caption" src="//upload.wikimedia.org/wikipedia/mediawiki/a/a9/Example.jpg" width="400" height="267" data-file-width="400" data-file-height="267">
text text text ...

</td></tr>
<tr>
<td>border results in a very small gray border Rendered as a floating block: no Rendered inline: yes Rendered caption: no
</td>
<td>
<pre>... text text text
[[File:example.jpg|border|caption]]
text text text ...
</pre>
</td>
<td>... text text text
<img alt="caption" src="//upload.wikimedia.org/wikipedia/mediawiki/a/a9/Example.jpg" width="400" height="267" class="thumbborder" data-file-width="400" data-file-height="267">
text text text ...

</td></tr>
<tr>
<td>frameless, like thumbnail, respect user preferences for image width, but without border and no right float Rendered as a floating block: no Rendered inline: yes Rendered caption: no
</td>
<td>
<pre>... text text text
[[File:example.jpg|frameless|caption]]
text text text ...
</pre>
</td>
<td>... text text text
<img alt="caption" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/220px-Example.jpg" width="220" height="147" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/330px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/a/a9/Example.jpg 2x" data-file-width="400" data-file-height="267">
text text text ...

</td></tr>
<tr>
<td>frameless and border Rendered as a floating block: no Rendered inline: yes Rendered caption: no
</td>
<td>
<pre>... text text text
[[File:example.jpg|frameless|border|caption]]
text text text ...
</pre>
</td>
<td>... text text text
<img alt="caption" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/220px-Example.jpg" width="220" height="147" class="thumbborder" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/330px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/a/a9/Example.jpg 2x" data-file-width="400" data-file-height="267">
text text text ...

</td></tr>
<tr>
<td>frame Rendered as a floating block: yes Rendered inline: no Rendered caption: yes
</td>
<td>
<pre>... text text text
[[File:example.jpg|frame|caption]]
text text text ...
</pre>
</td>
<td>... text text text
<div class="thumb tright"><div class="thumbinner" style="width:402px;"><img alt="" src="//upload.wikimedia.org/wikipedia/mediawiki/a/a9/Example.jpg" width="400" height="267" class="thumbimage" data-file-width="400" data-file-height="267"> <div class="thumbcaption">caption</div></div></div>
text text text ...

</td></tr>
<tr>
<td>thumb or thumbnail Rendered as a floating block: yes Rendered inline: no Rendered caption: yes
</td>
<td>
<pre>... text text text
[[File:example.jpg|thumb|caption]]
text text text ...
</pre>
</td>
<td>... text text text
<div class="thumb tright"><div class="thumbinner" style="width:222px;"></div><img alt="" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/220px-Example.jpg" width="220" height="147" class="thumbimage" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/330px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/a/a9/Example.jpg 2x" data-file-width="400" data-file-height="267"> <div class="thumbcaption"><div class="magnify"></div>caption</div></div></div>
text text text ...

</td></tr></table>

When the height of an image in thumbnail is bigger than its width (i.e. in portrait orientation rather than landscape) and you find it too large, you may try the option upright=N, where N is the image's aspect ratio (its width divided by its height, defaulting to 0.75). The alternative is to specify the desired maximum height (in pixels) explicitly.

Note that by writing thumb={filename}, you can use a different image for the thumbnail.

Size and frame

Among different formats, the effect of the size parameter may be different, as shown below.

<ul><li>For how it appears when its size is not specified, see Format section above.</li>
<li>When the format is not specified, or only <code>border</code>ed, the size can be both reduced and enlarged to any specified size.</li>
<li>In the examples below, the original size of the image is 400 × 267 pixels.</li>
<li>An image with <code>frame</code> always ignores the size specification, the original image will be reduced if it exceeds the maximum size defined in user preferences.</li>
<li>The size of an image with <code>thumb</code> can be reduced, but can not be enlarged beyond the original size of the image.</li></ul>

<table class="wikitable">

<tr>
<th style="text-align:center;padding: 10px">Format</th>
<th style="text-align:center">Reduced</th>
<th style="text-align:center">Enlarged
</th></tr>
<tr>
<th>(not specified)
</th>
<td>
<pre>[[File:Example.jpg|50px]]
</pre>
<img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/50px-Example.jpg" width="50" height="33" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/75px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg 2x" data-file-width="400" data-file-height="267">

</td>
<td>
<pre>[[File:Example.jpg|200px]]
</pre>
<img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg" width="200" height="134" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/300px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/a/a9/Example.jpg 2x" data-file-width="400" data-file-height="267">
 

</td></tr>
<tr>
<th>border
</th>
<td>
<pre>[[File:Example.jpg|border|50px]]
</pre>
<img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/50px-Example.jpg" width="50" height="33" class="thumbborder" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/75px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg 2x" data-file-width="400" data-file-height="267">

</td>
<td>
<pre>[[File:Example.jpg|border|200px]]
</pre>
<img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg" width="200" height="134" class="thumbborder" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/300px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/a/a9/Example.jpg 2x" data-file-width="400" data-file-height="267">
 

</td></tr>
<tr>
<th>frame
</th>
<td>
<pre>[[File:Example.jpg|frame|50px]]
</pre>
<div class="thumb tright"><div class="thumbinner" style="width:402px;"><img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/a/a9/Example.jpg" width="400" height="267" class="thumbimage" data-file-width="400" data-file-height="267"> <div class="thumbcaption"></div></div></div>
</td>
<td>
<pre>[[File:Example.jpg|frame|200px]]
</pre>
<div class="thumb tright"><div class="thumbinner" style="width:402px;"><img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/a/a9/Example.jpg" width="400" height="267" class="thumbimage" data-file-width="400" data-file-height="267"> <div class="thumbcaption"></div></div></div>
 

</td></tr>
<tr>
<th>thumb
</th>
<td>
<pre>[[File:Example.jpg|thumb|50px]]
</pre>
<div class="thumb tright"><div class="thumbinner" style="width:52px;"><img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/50px-Example.jpg" width="50" height="33" class="thumbimage" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/75px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <div class="thumbcaption"><div class="magnify"></div></div></div></div>
</td>
<td>
<pre>[[File:Example.jpg|thumb|200px]]
</pre>
<div class="thumb tright"><div class="thumbinner" style="width:202px;"><img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg" width="200" height="134" class="thumbimage" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/300px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/a/a9/Example.jpg 2x" data-file-width="400" data-file-height="267"> <div class="thumbcaption"><div class="magnify"></div></div></div></div>
 

</td></tr>
<tr>
<th>frameless
</th>
<td>
<pre>[[File:Example.jpg|frameless|50px]]
</pre>
<img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/50px-Example.jpg" width="50" height="33" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/75px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg 2x" data-file-width="400" data-file-height="267">

</td>
<td>
<pre>[[File:Example.jpg|frameless|200px]]
</pre>
<img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg" width="200" height="134" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/300px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/a/a9/Example.jpg 2x" data-file-width="400" data-file-height="267">

</td></tr></table>

Horizontal alignment

Note that when using the frame or thumb[nail] formats, the default horizontal alignment will be right.

<table class="wikitable">

<tr>
<th style="text-align:center;padding:10px">Description
</th>
<th style="text-align:center">You type
</th>
<th style="text-align:center">You get
</th></tr>
<tr>
<td>no horizontal alignment specified, or default alignment Rendered as a floating block: no Rendered inline: yes
</td>
<td>
<pre>... text text text
[[File:example.jpg|100px|caption]]
text text text ...
</pre>
</td>
<td>... text text text
<img alt="caption" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg" width="100" height="67" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/150px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg 2x" data-file-width="400" data-file-height="267">
text text text ...

</td></tr>
<tr>
<td>specify horizontal alignment as: none Rendered as a floating block: no Rendered inline: no
</td>
<td>
<pre>... text text text
[[File:example.jpg|none|100px|caption]]
text text text ...
</pre>
</td>
<td>... text text text
<div class="floatnone"><img alt="caption" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg" width="100" height="67" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/150px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg 2x" data-file-width="400" data-file-height="267"></div>
text text text ...

</td></tr>
<tr>
<td>specify horizontal alignment as: center Rendered as a floating block: no Rendered inline: no
</td>
<td>
<pre>... text text text
[[File:example.jpg|center|100px|caption]]
text text text ...
</pre>
</td>
<td>... text text text
<div class="center"><div class="floatnone"><img alt="caption" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg" width="100" height="67" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/150px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg 2x" data-file-width="400" data-file-height="267"></div></div>
text text text ...

</td></tr>
<tr>
<td>specify horizontal alignment as: left Rendered as a floating block: yes Rendered inline: no
</td>
<td>
<pre>... text text text
[[File:example.jpg|left|100px|caption]]
text text text ...
</pre>
</td>
<td>... text text text
<div class="floatleft"><img alt="caption" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg" width="100" height="67" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/150px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg 2x" data-file-width="400" data-file-height="267"></div>
text text text ...

</td></tr>
<tr>
<td>specify horizontal alignment as: right Rendered as a floating block: yes Rendered inline: no
</td>
<td>
<pre>... text text text
[[File:example.jpg|right|100px|caption]]
text text text ...
</pre>
</td>
<td>... text text text
<div class="floatright"><img alt="caption" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg" width="100" height="67" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/150px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg 2x" data-file-width="400" data-file-height="267"></div>
text text text ...

</td></tr></table>

Vertical alignment

The vertical alignment options take effect only if the image is rendered as an inline element and is not floating. They alter the way the inlined image will be vertically aligned with the text present in the same block before and/or after this image on the same rendered row.

Note that the rendered line of text where inline images are inserted (and the lines of text rendered after the current one) may be moved down (this will increase the line-height conditionally by additional line spacing, just as it may occur with spans of text with variable font sizes, or with superscripts and subscripts) to allow the image height to be fully displayed with this alignment constraint.

<div class="mw-collapsible mw-made-collapsible mw-collapsed"><div class="mw-collapsible-toggle toccolours mw-collapsible-toggle-collapsed" style="padding:10px;background-color:antiquewhite;float:none;text-align:center" tabindex="0">Toggle source code view</div>
<div class="mw-collapsible-content" style="display: none;">
<div class="mw-highlight mw-content-ltr" dir="ltr"><pre><p style="border:1px solid #AAA;padding:0;font-size:150%;line-height:2">
<span style="background:#FFF;color:#000;text-decoration:overline"><u><del>text</del>
'''top:''' [[File:Example.jpg|20px|top]] [[File:Example.jpg|40px|top]] [[File:Example.jpg|100px|top]]
<del>text</del></u></span></p>

<p style="border:1px solid #AAA;padding:0;font-size:150%;line-height:2">
<span style="background:#FFF;color:#000;text-decoration:overline"><u><del>text</del>
'''text-top:''' [[File:Example.jpg|20px|text-top]] [[File:Example.jpg|40px|text-top]] [[File:Example.jpg|100px|text-top]]
<del>text</del></u></span></p>

<p style="border:1px solid #AAA;padding:0;font-size:150%;line-height:2">
<span style="background:#FFF;color:#000;text-decoration:overline"><u><del>text</del>
<sup>super:</sup> [[File:Example.jpg|20px|super]] [[File:Example.jpg|40px|super]] [[File:Example.jpg|100px|super]]
<del>text</del></u></span></p>

<p style="border:1px solid #AAA;padding:0;font-size:150%;line-height:2">
<span style="background:#FFF;color:#000;text-decoration:overline"><u><del>text</del>
'''baseline:''' [[File:Example.jpg|20px|baseline]] [[File:Example.jpg|40px|baseline]] [[File:Example.jpg|100px|baseline]]
<del>text</del></u></span></p>

<p style="border:1px solid #AAA;padding:0;font-size:150%;line-height:2">
<span style="background:#FFF;color:#000;text-decoration:overline"><u><del>text</del>
<sub>'''sub:'''</sub> [[File:Example.jpg|20px|sub]] [[File:Example.jpg|40px|sub]] [[File:Example.jpg|100px|sub]]
<del>text</del></u></span></p>

<p style="border:1px solid #AAA;padding:0;font-size:150%;line-height:2">
<span style="background:#FFF;color:#000;text-decoration:overline"><u><del>text</del>
'''default:''' [[File:Example.jpg|20px]][[File:Example.jpg|40px]] [[File:Example.jpg|100px]]
<del>text</del></u></span></p>

<p style="border:1px solid #AAA;padding:0;font-size:150%;line-height:2">
<span style="background:#FFF;color:#000;text-decoration:overline"><u><del>text</del>
'''middle:''' [[File:Example.jpg|20px|middle]] [[File:Example.jpg|40px|middle]] [[File:Example.jpg|100px|middle]]
<del>text</del></u></span></p>

<p style="border:1px solid #AAA;padding:0;font-size:150%;line-height:2">
<span style="background:#FFF;color:#000;text-decoration:overline"><u><del>text</del>
'''text-bottom:''' [[File:Example.jpg|20px|text-bottom]] [[File:Example.jpg|40px|text-bottom]] [[File:Example.jpg|100px|text-bottom]]
<del>text</del></u></span></p>

<p style="border:1px solid #AAA;padding:0;font-size:150%;line-height:2">
<span style="background:#FFF;color:#000;text-decoration:overline"><u><del>text</del>
'''bottom:'' [[File:Example.jpg|20px|bottom]] [[File:Example.jpg|40px|bottom]] [[File:Example.jpg|100px|bottom]]
<del>text</del></u></span></p>
</pre></div></div></div>

To show the alignment result more clearly, the text spans are overlined and underlined, the font-size is increased to 200%, and the paragraph block is outlined with a thin border; additionally images of different sizes are aligned:


<del>text</del>
top: <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/20px-Example.jpg" width="20" height="13" style="vertical-align: top" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/30px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg" width="40" height="27" style="vertical-align: top" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/60px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/80px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg" width="100" height="67" style="vertical-align: top" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/150px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg 2x" data-file-width="400" data-file-height="267">
<del>text</del>

<del>text</del>
text-top: <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/20px-Example.jpg" width="20" height="13" style="vertical-align: text-top" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/30px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg" width="40" height="27" style="vertical-align: text-top" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/60px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/80px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg" width="100" height="67" style="vertical-align: text-top" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/150px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg 2x" data-file-width="400" data-file-height="267">
<del>text</del>


<del>text</del>
super: <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/20px-Example.jpg" width="20" height="13" style="vertical-align: super" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/30px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg" width="40" height="27" style="vertical-align: super" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/60px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/80px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg" width="100" height="67" style="vertical-align: super" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/150px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg 2x" data-file-width="400" data-file-height="267">
<del>text</del>


<del>text</del>
baseline: <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/20px-Example.jpg" width="20" height="13" style="vertical-align: baseline" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/30px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg" width="40" height="27" style="vertical-align: baseline" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/60px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/80px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg" width="100" height="67" style="vertical-align: baseline" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/150px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg 2x" data-file-width="400" data-file-height="267">
<del>text</del>

<del>text</del>
sub: <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/20px-Example.jpg" width="20" height="13" style="vertical-align: sub" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/30px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg" width="40" height="27" style="vertical-align: sub" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/60px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/80px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg" width="100" height="67" style="vertical-align: sub" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/150px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg 2x" data-file-width="400" data-file-height="267">
<del>text</del>

<del>text</del>
default: <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/20px-Example.jpg" width="20" height="13" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/30px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg" width="40" height="27" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/60px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/80px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg" width="100" height="67" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/150px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg 2x" data-file-width="400" data-file-height="267">
<del>text</del>

<del>text</del>
middle: <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/20px-Example.jpg" width="20" height="13" style="vertical-align: middle" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/30px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg" width="40" height="27" style="vertical-align: middle" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/60px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/80px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg" width="100" height="67" style="vertical-align: middle" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/150px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg 2x" data-file-width="400" data-file-height="267">
<del>text</del>

<del>text</del>
text-bottom: <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/20px-Example.jpg" width="20" height="13" style="vertical-align: text-bottom" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/30px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg" width="40" height="27" style="vertical-align: text-bottom" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/60px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/80px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg" width="100" height="67" style="vertical-align: text-bottom" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/150px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg 2x" data-file-width="400" data-file-height="267">
<del>text</del>

<del>text</del>
bottom: <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/20px-Example.jpg" width="20" height="13" style="vertical-align: bottom" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/30px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/40px-Example.jpg" width="40" height="27" style="vertical-align: bottom" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/60px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/80px-Example.jpg 2x" data-file-width="400" data-file-height="267"> <img alt="Example.jpg" src="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/100px-Example.jpg" width="100" height="67" style="vertical-align: bottom" srcset="//upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/150px-Example.jpg 1.5x, //upload.wikimedia.org/wikipedia/mediawiki/thumb/a/a9/Example.jpg/200px-Example.jpg 2x" data-file-width="400" data-file-height="267">
<del>text</del>

Notes:

<ol><li>The "middle" vertical alignment position of the image (which is also the default) usually refers to the middle between the x-height and the baseline of the text (on which the vertical middle of the image will be aligned, and on which usually the text may be overstroke), but not to the middle of the line-height of the font-height that refers to the space between the "text-top" and "text-bottom" positions ; the font-height excludes:
<ul><li>the additional line separation spacing normally divided equally into two line-margins (here 0.5em, according to line-height set to 200%) above and below the font-height).</li>
<li>the additional line spacing which may be added by superscripts and subscripts.</li></ul></li>
<li>However, if the image height causes its top or bottom position to go above or below the normal full line-height of text, the middle position will be adjusted after the increasing the top and/or bottom line-margins so that the image can fit and align properly, and all images (including those with smaller heights) will be vertically centered on the adjusted middle position (for computing the effective line-height, the text of each rendered row with the larger font-height will be considered).</li>
<li>The "text-top" and "text-bottom" alignment positions also excludes the extra line spacing added by superscripts and subscripts, but not the additional line-spacing defined by the line-height.</li>
<li>The "top" and "bottom" alignment positions take into account all these extra line spacings (including superscripts and subscripts, if they are present in a rendered line span). When the image alignment constrains the image to grow above or below the normal line-spacing, and the image is not absolutely positioned, the image will cause the "top" and "bottom" positions to be adjusted (just like superscripts and subscripts), so the effective line-height between rendered lines of text will be higher.</li>
<li>The "underline", "overline" and "overstrike" text-decoration positions should be somewhere within these two limits and may depend on the type and height of fonts used (the superscript and subscript styles may be taken into account in some browsers, but usually these styles are ignored and the position of these decorations may not be adjusted); so these decorations normally don't affect the vertical position of images, relatively to the text.</li></ol>

Stopping the text flow

On occasion it is desirable to stop text (or other inline non-floating images) from flowing around a floating image. Depending on the web browser's screen resolution and such, text flow on the right side of an image may cause a section header (for instance, == My Header ==) to appear to the right of the image, instead of below it, as a user may expect. The text flow can be stopped by placing (or if you prefer, <div style="clear: both"></div>) before the text that should start below the floating image. (This may also be done without an empty line by wrapping the section with the floating images with <div style="overflow: hidden">…</div>, which clears all floats inside the div element.)

All images rendered as blocks (including non-floating centered images, left- or right-floating images, as well as framed or thumbnailed floating images) are implicitly breaking the surrounding lines of text (terminating the current block of text before the image, and creating a new paragraph for the text after them). They will then stack vertically along their left or right alignment margin (or along the center line between these margins for centered images).

Altering the default link target

The following table shows how to alter the link target (whose default is the image description page) or how to remove it. Changing the link does not alter the format described in the previous sections.

<table class="wikitable plainlinks">

<tr>
<th style="text-align:center;padding:10px">Description
</th>
<th style="text-align:center">You type
</th>
<th style="text-align:center">You get
</th></tr>
<tr>
<td>internal link
</td>
<td>
<pre>... text text text
[[File:example.jpg|link=Main Page|caption]]
text text text ...
</pre>
</td>
<td>... text text text
<img alt="caption" src="//upload.wikimedia.org/wikipedia/mediawiki/a/a9/Example.jpg" width="400" height="267" data-file-width="400" data-file-height="267">
text text text ...

</td></tr>
<tr>
<td>external link
</td>
<td>
<pre>... text text text
[[File:example.jpg||caption]]
text text text ...
</pre>
</td>
<td>... text text text
<img alt="caption" src="//upload.wikimedia.org/wikipedia/mediawiki/a/a9/Example.jpg" width="400" height="267" data-file-width="400" data-file-height="267">
text text text ...

</td></tr>
<tr>
<td>no link (external or file page)
</td>
<td>
<pre>... text text text
[[File:example.jpg|link=|caption]]
text text text ...
</pre>
</td>
<td>... text text text
<img alt="caption" src="//upload.wikimedia.org/wikipedia/mediawiki/a/a9/Example.jpg" title="caption" width="400" height="267" data-file-width="400" data-file-height="267">
text text text ...

</td></tr></table>

Warning:


The licencing requirements on yourKnowledge Management system may not allow you to remove all links to the description page that displays the required authors attributions, the copyrights statements, the applicable licencing terms, or a more complete description of the rendered image (including its history of modifications).
If you change or remove the target link of an image, you will then have to provide somewhere else on your page an explicit link to this description page, or to display the copyright and author statement and a link to the applicable licence, if they are different from the elements applicable to the embedding page itself.
YourKnowledge Management system policy may restrict the use of the alternate link parameter, or may even enforce a prohibition of alternate link parameters for embedded media files (in which case, the link parameter will be ignored), or may only accept them after validation by authorized users or administrators.

Normal and sysop users cannot permanently delete a Knowledge Management system page, but sysops can delete a page such that it could still be restored. This is a deliberate design feature, and is an important part of why Knowledge Management system's work. Every kind of editing operation can be reverted by any other user, and that includes resurrecting deleted content. It doesn't cause significant wasted space; and with nothing but a 'delete' label, the page is effectively deleted anyway.

Deleting a page is, on the other hand, a straightforward operation for anyone with sysop permissions: it allows to semi-permanently remove a page from the Knowledge Management system, until a sysop undeletes (restores) it with the same ease. Typically sysops might look for delete labels, and do a proper delete on these pages, after a period of time. If for some reason you need a page to be deleted more quickly than that, you will need to contact a sysop to request this.

Revision deletion offers a more granular feature of deletion for edits with peculiar problems.

===Before deleting===

Sysops should also be aware of the general advice given on When not to delete a page: in particular, there are many situations where a deletion is too drastic. For example, a redirect is often more appropriate.

Before deleting you could perform various checks:

*'''Use the "What links here" tool. This gives an indication as to how important a page is, and what subjects it relates to. Perhaps the page is still linked to prominently from many places. All incoming links will become red links if you proceed with the delete. Ideally all incoming links should be changed/removed, if there is genuinely no need for this page to exist. You could do this work prior to deleting, or ask others in the Knowledge Management system community to do it.
*'''Check the page history and the associated talk page. Who was proposing the deletion? Does anyone disagree? Has it been properly discussed? Did people have adequate time to raise objections? Did somebody vandalize a page, which then led to a deletion proposal?

The care taken over these things might depend on the size of the Knowledge Management system community, and how clear-cut the case for deletion is. Remember that only sysop users can undo a delete action, so to a normal user the information appears to be lost forever.

===Use the 'delete' action===

Sysops should see a 'delete' tab or action menu option at the top of every page. To find the action menu, look for a down arrow or triangle next to the "View History" tab. If you mouse over the triangle you should see "delete", "move", "protect" and "watch". Click the delete action to delete the page. When using browsers which support keyboard shortcuts, you can also use (Control-Alt-D). You will be asked to confirm, and to supply a "Reason for deletion". This is a short textual description of why the page is being deleted. Your action will appear on the recent changes display, and in the deletion log ([[Special:Log]]).

Remember only the administrator can delete uploaded photograph files.

===Undeleting===

To undelete a page you must navigate to the exact page name of the page.
You should then see a link to "View or restore n deleted edits". Tick the box next to the revision you wish to restore.

===Configuring deletion reasons===
The list of reasons in the dropdown box is maintained at [[Help:Deletereason-dropdown]].

===When not to delete a page===

Typically you would delete a page if the contents are entirely inappropriate and do not match the purposes of the Knowledge Management system. In other situations, you would take a less extreme course of action, for example:

*'''The page should have a different title. See [[Help:Moving a page]].
*'''The contents should have been placed on a different page -- Add the contents to the other page, and then supply a redirect. See Help:Redirects.
*'''The contents are already on a different page -- Delete the duplicate content and leave a redirect. That way, the page title, which made sense to somebody, will helpfully redirect to the information.
*'''The page is out-of-date -- Re-word sentences to be in the past tense, to make the page a historical record. Alternatively, label the information as out-of-date, with a warning notice.

An actual delete is generally necessary only if the title of the page is inappropriate. In other situations, a merge and redirect is more appropriate.

===Proposing changes===

Deciding on appropriate content/page titles can be a difficult aspect of Knowledge Management system organization, and one which can often provoke debates. If the merge or deletion you have in mind is one which might cause upset, you should propose the change first. Do this by leaving a note to give your reasons on the talk page. You might also establish a system for labeling the page with a delete/merge proposal template, to make everybody aware of your intentions.

===Unlinking a page===

The 'What links here' toolbox feature (bottom of left sidebar) will tell you which other Knowledge Management system pages link to the current page. Always use this feature to check before proceeding with deleting. These related pages will need to be edited for their links to reflect the change.

*'''[[Help:Starting a new page]]
*'''[[Help:Moving a page]]
*'''[[Help:Admin deleting and undeleting]]
*'''[[Help:Formating]]
*'''[[Help:Links]]
*'''[[Help:List]]
*'''[[Help:Images]]
*'''[[Help:Tables]]

Help:List

2019-01-11T08:12:36Z

Ufo:

This page deals with creating lists in Knowledge Management system

===List basics===

Knowledge Management system offers three types of lists: ordered lists, unordered lists, and definition lists. In the following sections, ordered lists are used for examples. Unordered lists would give corresponding results.

<table class="wikitable">
<tr>
<th style="text-align:center;padding:10px">Knowledge Management system text</th>
<th style="text-align:center">Rendering
</th></tr>
<tr>
<td><pre>* Lists are easy to do:
** start every line
* with a star
** more stars mean
*** deeper levels</pre>
</td>
<td>
<ul><li>Lists are easy to do:
<ul><li>start every line</li></ul></li>
<li>with a star
<ul><li>more stars mean
<ul><li>deeper levels</li></ul></li></ul></li></ul>
</td></tr>
<tr>
<td><pre>* A newline
* in a list
marks the end of the list.
Of course
* you can
* start again.</pre>
</td>
<td>
<ul><li>A newline</li>
<li>in a list</li></ul>
marks the end of the list.
Of course

<ul><li>you can</li>
<li>start again.</li></ul>
</td></tr>
<tr>
<td><pre># Numbered lists are good
## very organized
## easy to follow</pre>
</td>
<td>
<ol><li>Numbered lists are good
<ol><li>very organized</li>
<li>easy to follow</li></ol></li></ol>
</td></tr>
<tr>
<td><pre>* You can also
** break lines
** like this</pre>
</td>
<td>
<ul><li>You can also
<ul><li>break lines</li>
<li>like this</li></ul></li></ul>
</td></tr>
<tr>
<td><pre>; Definition lists
; item : definition
; semicolon plus term
: colon plus definition</pre>
</td>
<td>
<dl><dt>Definition lists</dt>
<dt>item </dt>
<dd>definition</dd>
<dt>semicolon plus term</dt>
<dd>colon plus definition</dd></dl>
</td></tr>
<tr>
<td><pre>; Mixed definition lists
; item 1 : definition
:; sub-item 1 plus term
:: two colons plus definition
:; sub-item 2 : colon plus definition
; item 2
: back to the main list</pre>
</td>
<td>
<dl><dt>Mixed definition lists</dt>
<dt>item 1 </dt>
<dd>definition
<dl><dt>sub-item 1 plus term</dt>
<dd>two colons plus definition</dd>
<dt>sub-item 2 </dt>
<dd>colon plus definition</dd></dl></dd></dl>
<dl><dt>item 2</dt>
<dd>back to the main list</dd></dl>
</td></tr>
<tr>
<td><pre>* Or create mixed lists
*# and nest them
*#* like this
*#*; definitions
*#*: work:
*#*; apple
*#*; banana
*#*: fruits</pre>
</td>
<td>
<ul><li>Or create mixed lists
<ol><li>and nest them
<ul><li>like this
<dl><dt>definitions</dt>
<dd>work:</dd>
<dt>apple</dt>
<dt>banana</dt>
<dd>fruits</dd></dl></li></ul></li></ol></li></ul>
</td></tr></table>

===Paragraphs in lists===

For simplicity, list items in Knowledge Management system markup cannot be longer than a paragraph. A following blank line will end the list and reset the counter on ordered lists. Separating unordered list items usually has no noticeable effects.

Paragraphs can be forced in lists by using HTML tags. Two line break symbols, , will create the desired effect. So will enclosing all but the first paragraph with ....

For a list with items of more than one paragraph long, adding a blank line between items may be necessary to avoid confusion.

===Continuing a list item after a sub-item===

In HTML, a list item may contain several sublists, not necessarily adjacent; thus there may be parts of the list item not only before the first sublist, but also between sublists, and after the last one; however, in Knowledge Management system-syntax, sublists follow the same rules as sections of a page: the only possible part of the list item not in sublists is before the first sublist.

In the case of an unnumbered first-level list in Knowledge Management system text code this limitation can be overcome by splitting the list into multiple lists; indented text between the partial lists may visually serve as part of a list item after a sublist; however, this may give, depending on CSS, a blank line before and after each list, in which case, for uniformity, every first-level list item could be made a separate list.

Numbered lists illustrate that what should look like one list may, for the software, consist of multiple lists; unnumbered lists give a corresponding result, except that the problem of restarting with 1 is not applicable.

<table style="border:1px;border-spacing:1px;background-color:black;" class="sortable jquery-tablesorter" cellpadding="5">

<tr style="background-color:white;">
<td>
<pre><ol>
<li>list item A1
<ol>
<li>list item B1</li>
<li>list item B2</li>
</ol>continuing list item A1
</li>
<li>list item A2</li>
</ol></pre>
</td>
<td><ol>
<li>list item A1
<ol>
<li>list item B1</li>
<li>list item B2</li>
</ol>continuing list item A1
</li>
<li>list item A2</li>
</ol>
</td></tr>
<tr style="background-color:#E0E0E0;font-weight:bold;text-align:center;">
<td colspan="2">vs.
</td></tr>
<tr style="background-color:white;">
<td><pre>#list item A1
##list item B1
##list item B2
#:continuing list item A1
#list item A2</pre>
</td>
<td>
<ol><li>list item A1
<ol><li>list item B1</li>
<li>list item B2</li></ol>
<dl><dd>continuing list item A1</dd></dl></li>
<li>list item A2</li></ol>
</td></tr></table>

One level deeper, with a sublist item continuing after a sub-sublist, one gets even more blank lines; however, the continuation of the first-level list is not affected:

<pre>#list item A1
##list item B1
###list item C1
##:continuing list item B1
##list item B2
#list item A2</pre>

gives

<ol><li>list item A1
<ol><li>list item B1
<ol><li>list item C1</li></ol>
<dl><dd>continuing list item B1</dd></dl></li>
<li>list item B2</li></ol></li>
<li>list item A2</li></ol>

===Changing the list type===

The list type (which type of marker appears before the list item) can be changed in CSS by setting the list-style-type property:

<table class="wikitable">
<tr>
<th style="text-align: center;padding: 10px">Knowledge Management system text</th>
<th style="text-align: center">Rendering
</th></tr>
<tr>
<td>
<pre><ol style="list-style-type:lower-roman">
<li>About the author</li>
<li>Foreword to the first edition</li>
<li>Foreword to the second edition</li>
</ol></pre>
</td>
<td><ol style="list-style-type:lower-roman">
<li>About the author</li>
<li>Foreword to the first edition</li>
<li>Foreword to the second edition</li>
</ol>
</td></tr>
<tr>
<td>
<pre><ol style="list-style-type:lower-alpha">
<li>About the author</li>
<li>Foreword to the first edition</li>
<li>Foreword to the second edition</li>
</ol></pre>
</td>
<td><ol style="list-style-type:lower-alpha">
<li>About the author</li>
<li>Foreword to the first edition</li>
<li>Foreword to the second edition</li>
</ol>
</td></tr></table>

===Extra indentation of lists===

In a numbered list in a large font, some browsers do not show more than two digits, unless extra indentation is applied (if there are multiple columns: for each column). This can be done with CSS:

ol { margin-left: 2cm}

or alternatively, like below.

<table class="wikitable">
<tr>
<th style="text-align: center;padding: 10px">Knowledge Management system text</th>
<th style="text-align: center">Rendering
</th>
<th style="width: 40%;text-align: center">Comments
</th></tr>
<tr>
<td>
<pre>:#abc
:#def
:#ghi
</pre>
</td>
<td>
<dl><dd><ol><li>abc</li>
<li>def</li>
<li>ghi</li></ol></dd></dl>
</td>
<td>A list of one or more lines starting with a colon creates a [http://www.w3.org/TR/html4/struct/lists.html#edef-DL definition list] without definition terms, and with the items as definition descriptions, hence indented. However, if the colons are in front of the codes "*" or "#" of an unordered or ordered list, the list is treated as one definition description, so the whole list is indented.
</td></tr>
<tr>
<td>
<pre><ul>
<ol>
<li>abc</li>
<li>def</li>
<li>ghi</li>
</ol>
</ul>
</pre>
</td>
<td>
<ul>
<ol>
<li>abc</li>
<li>def</li>
<li>ghi</li>
</ol>
</ul>
</td>
<td>Knowledge Management system translates an unordered list (ul) without any list items (li) into a div with a <code>style="margin-left: 2em"</code>, causing indentation of the contents. This is the most versatile method, as it allows starting with a number other than 1, see below.
</td></tr>
<tr>
<td>
<pre><ul>
#abc
#def
#ghi
</ul>
</pre>
</td>
<td>
<ul>
<ol><li>abc</li>
<li>def</li>
<li>ghi</li></ol>
</ul>
</td>
<td>Like above, with the content of the "unordered list without any list items", which itself is an ordered list, expressed with # codes. The HTML produced, and hence the rendering, is the same. This is the recommended method when starting the list at 1.
</td></tr></table>

to demonstrate that all three methods show all digits of 3-digit numbers

Specifying a starting value

<table style="width:100%">
<tr>
<td style="width: 50%">
<pre><ol start="9">
<li>Amsterdam</li>
<li>Rotterdam</li>
<li>The Hague</li>
</ol>
</pre>
</td>
<td>
<ol start="9">
<li>Amsterdam</li>
<li>Rotterdam</li>
<li>The Hague</li>
</ol>
</td></tr></table>

Or:

<table style="width:100%">
<tr>
<td style="width: 50%">
<pre><ol>
<li value="9">Amsterdam</li>
<li value="8">Rotterdam</li>
<li value="7">The Hague</li>
</ol>
</pre>
</td>
<td>
<ol>
<li value="9">Amsterdam</li>
<li value="8">Rotterdam</li>
<li value="7">The Hague</li>
</ol>
</td></tr></table>

===Comparison with a table===

Apart from providing automatic numbering, the numbered list also aligns the contents of the items, comparable with using table syntax:

<pre>{|
|-
| align=right | 9.|| Amsterdam
|-
| align=right | 10.|| Rotterdam
|-
| align=right | 11.|| The Hague
|}
</pre>

gives

<table>

<tr>
<td align="right">9.</td>
<td>Amsterdam
</td></tr>
<tr>
<td align="right">10.</td>
<td>Rotterdam
</td></tr>
<tr>
<td align="right">11.</td>
<td>The Hague
</td></tr></table>

This non-automatic numbering has the advantage that if a text refers to the numbers, insertion or deletion of an item does not disturb the correspondence.

===Multi-column bulleted list===

<pre><div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
* apple
* carpet
* geography
* mountain
* nowhere
* postage
* ragged
* toast
</div>
</pre>

gives:

<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
<ul><li>apple</li>
<li>carpet</li>
<li>geography</li>
<li>mountain</li>
<li>nowhere</li>
<li>postage</li>
<li>ragged</li>
<li>toast</li></ul>
</div>
<pre><div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
* apple
* carpet
* geography
* mountain
* nowhere
* postage
* ragged
* toast
</div>
</pre>

gives:

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
<ul><li>apple</li>
<li>carpet</li>
<li>geography</li>
<li>mountain</li>
<li>nowhere</li>
<li>postage</li>
<li>ragged</li>
<li>toast</li></ul>
</div>

===Multi-column numbered list===

<pre><div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
#apple
#carpet
#geography
#mountain
#nowhere
#postage
#ragged
#toast
</div>
</pre>

gives:

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
<ol><li>apple</li>
<li>carpet</li>
<li>geography</li>
<li>mountain</li>
<li>nowhere</li>
<li>postage</li>
<li>ragged</li>
<li>toast</li></ol>
</div>

Below a starting value is specified, with HTML-syntax (for the first column either Knowledge Management-syntax or HTML-syntax can be used).

In combination with the extra indentation explained in the previous section:

<pre>{| valign="top"
|-
|<ul><ol start="125"><li>a<li>bb<li>ccc</ol></ul>
|<ul><ol start="128"><li>ddd<li>ee<li>f</ol></ul>
|}
</pre>

gives:

<table>

<tr>
<td><ul><ol start="125"><li>a</li><li>bb</li><li>ccc</li></ol></ul>
</td>
<td><ul><ol start="128"><li>ddd</li><li>ee</li><li>f</li></ol></ul>
</td></tr></table>

<pre>{{Multi-column numbered list|lst=lower-alpha|125|a<li>bb<li>ccc|3|<li>ddd<li>ee|2|<li>f}}

gives:

<table>

<tr>
<td valign="top"><ul><ol start="125" style="list-style-type:lower-roman"><li>a</li><li>bb</li><li>ccc</li></ol></ul>
</td>
<td valign="top"><ul><ol start="128" style="list-style-type:lower-roman"><li>ddd</li><li>ee</li></ol></ul>
</td>
<td valign="top"><ul><ol start="130" style="list-style-type:lower-roman"><li>f</li></ol></ul>
</td></tr></table>

<pre>{{Multi-column numbered list|lst=disc||a<li>bb<li>ccc||<li>ddd<li>ee||<li>f}}</pre>

gives:

<table>

<tr>
<td valign="top"><ul><ol start="1" style="list-style-type:disc"><li>a</li><li>bb</li><li>ccc</li></ol></ul>
</td>
<td valign="top"><ul><ol start="2" style="list-style-type:disc"><li>ddd</li><li>ee</li></ol></ul>
</td>
<td valign="top"><ul><ol start="3" style="list-style-type:disc"><li>f</li></ol></ul>
</td></tr></table>

===Streamlined style or horizontal style===

It is also possible to present short lists using very basic formatting, such as:

<pre>''Title of list:'' example 1, example 2, example 3</pre>

Title of list: example 1, example 2, example 3

This style requires less space on the page, and is preferred if there are only a few entries in the list, it can be read easily, and a direct edit point is not required. The list items should start with a lowercase letter unless they are proper nouns.

===Tables===

A one-column table is very similar to a list, but it allows sorting. If the Knowledge Management system text itself is already sorted with the same sortkey, this advantage does not apply. A multiple-column table allows sorting on any column.

===Changing unordered lists to ordered ones===

With the CSS

<pre>ul { list-style: decimal }
</pre>

unordered lists are changed to ordered ones. This applies (as far as the CSS selector does not restrict this) to all ul-lists in the HTML source code:

<ul><li>those produced with *</li>
<li>those with <ul> in the Knowledge Management system text</li>
<li>those produced by the system</li></ul>

Since each special page, like other pages, has a class based on the pagename, one can separately specify for each type whether the lists should be ordered, see User contributions and What links here.

However, it does not seem possible to make all page history lists ordered (unless one makes all lists ordered), because the class name is based on the page for which the history is viewed.

Normal and sysop users cannot permanently delete a Knowledge Management system page, but sysops can delete a page such that it could still be restored. This is a deliberate design feature, and is an important part of why Knowledge Management system's work. Every kind of editing operation can be reverted by any other user, and that includes resurrecting deleted content. It doesn't cause significant wasted space; and with nothing but a 'delete' label, the page is effectively deleted anyway.

Deleting a page is, on the other hand, a straightforward operation for anyone with sysop permissions: it allows to semi-permanently remove a page from the Knowledge Management system, until a sysop undeletes (restores) it with the same ease. Typically sysops might look for delete labels, and do a proper delete on these pages, after a period of time. If for some reason you need a page to be deleted more quickly than that, you will need to contact a sysop to request this.

Revision deletion offers a more granular feature of deletion for edits with peculiar problems.

===Before deleting===

Sysops should also be aware of the general advice given on When not to delete a page: in particular, there are many situations where a deletion is too drastic. For example, a redirect is often more appropriate.

Before deleting you could perform various checks:

*'''Use the "What links here" tool. This gives an indication as to how important a page is, and what subjects it relates to. Perhaps the page is still linked to prominently from many places. All incoming links will become red links if you proceed with the delete. Ideally all incoming links should be changed/removed, if there is genuinely no need for this page to exist. You could do this work prior to deleting, or ask others in the Knowledge Management system community to do it.
*'''Check the page history and the associated talk page. Who was proposing the deletion? Does anyone disagree? Has it been properly discussed? Did people have adequate time to raise objections? Did somebody vandalize a page, which then led to a deletion proposal?

The care taken over these things might depend on the size of the Knowledge Management system community, and how clear-cut the case for deletion is. Remember that only sysop users can undo a delete action, so to a normal user the information appears to be lost forever.

===Use the 'delete' action===

Sysops should see a 'delete' tab or action menu option at the top of every page. To find the action menu, look for a down arrow or triangle next to the "View History" tab. If you mouse over the triangle you should see "delete", "move", "protect" and "watch". Click the delete action to delete the page. When using browsers which support keyboard shortcuts, you can also use (Control-Alt-D). You will be asked to confirm, and to supply a "Reason for deletion". This is a short textual description of why the page is being deleted. Your action will appear on the recent changes display, and in the deletion log ([[Special:Log]]).

Remember only the administrator can delete uploaded photograph files.

===Undeleting===

To undelete a page you must navigate to the exact page name of the page.
You should then see a link to "View or restore n deleted edits". Tick the box next to the revision you wish to restore.

===Configuring deletion reasons===
The list of reasons in the dropdown box is maintained at [[Help:Deletereason-dropdown]].

===When not to delete a page===

Typically you would delete a page if the contents are entirely inappropriate and do not match the purposes of the Knowledge Management system. In other situations, you would take a less extreme course of action, for example:

*'''The page should have a different title. See [[Help:Moving a page]].
*'''The contents should have been placed on a different page -- Add the contents to the other page, and then supply a redirect. See Help:Redirects.
*'''The contents are already on a different page -- Delete the duplicate content and leave a redirect. That way, the page title, which made sense to somebody, will helpfully redirect to the information.
*'''The page is out-of-date -- Re-word sentences to be in the past tense, to make the page a historical record. Alternatively, label the information as out-of-date, with a warning notice.

An actual delete is generally necessary only if the title of the page is inappropriate. In other situations, a merge and redirect is more appropriate.

===Proposing changes===

Deciding on appropriate content/page titles can be a difficult aspect of Knowledge Management system organization, and one which can often provoke debates. If the merge or deletion you have in mind is one which might cause upset, you should propose the change first. Do this by leaving a note to give your reasons on the talk page. You might also establish a system for labeling the page with a delete/merge proposal template, to make everybody aware of your intentions.

===Unlinking a page===

The 'What links here' toolbox feature (bottom of left sidebar) will tell you which other Knowledge Management system pages link to the current page. Always use this feature to check before proceeding with deleting. These related pages will need to be edited for their links to reflect the change.

*'''[[Help:Starting a new page]]
*'''[[Help:Moving a page]]
*'''[[Help:Admin deleting and undeleting]]
*'''[[Help:Formating]]
*'''[[Help:Links]]
*'''[[Help:List]]
*'''[[Help:Images]]
*'''[[Help:Tables]]

Help:Formating

2019-01-11T08:12:14Z

Ufo:

====You can format your text by using Knowledge Management system markup. This consists of normal characters like asterisks, apostrophes or equal signs which have a special function in the Knowledge Management system, sometimes depending on their position. For example, to format a word in italic, you include it in two pairs of apostrophes like ''this''====

==Text formatting markup==

<table class="wikitable">
<tr style="padding:10px">
<th style="text-align:center;padding:10px">Description
</th>
<th width="40%" style="text-align:center">You type
</th>
<th width="40%" style="text-align:center">You get
</th></tr>
<tr>
<th colspan="3" style="background: #ABE;text-align:center;padding:10px">Character (inline) formatting – applies anywhere
</th></tr>
<tr>
<td>Italic text
</td>
<td><pre>''italic''
</pre>
</td>

<td>
italic

</td></tr>
<tr>
<td>Bold text
</td>
<td><pre>'''bold'''
</pre>
</td>
<td>
bold

</td></tr>
<tr>
<td>Bold and italic
</td>
<td><pre>'''''bold & italic'''''
</pre>
</td>
<td>
bold & italic

</td></tr>
<tr>
<td>Escape Knowledge Management system markup
</td>
<td><pre><nowiki>no ''markup''</nowiki>
</pre>
</td>
<td>
no ''markup''

</td></tr>
<tr>
<th colspan="3" style="background: #ABE;text-align: center;padding:10px">Section formatting – only at the beginning of the line
</th></tr>
<tr>
<td>Section Headings of different levels
</td>
<td><pre>== Level 2 ==

=== Level 3 ===

==== Level 4 ====

===== Level 5 =====

====== Level 6 ======
</pre>
<hr>
<div role="note" class="note note-info" style="background-position:left 7px top 50%; padding-right: 0.5em; padding-left: 40px;">
<ul><li>Skip Level 1, it is page name level.</li>
<li>Do not put any text on the same line after the ending equal signs.</li>
<li>An article with 4 or more headings automatically creates a table of contents (unless setting the magic word__NOTOC__).</li></ul></div>
</td>
<td>
<h2>Level 2</h2>
<h3>Level 3</h3>
<h4>Level 4</h4>
<h5>Level 5</h5>
<h6>Level 6</h6>
</td></tr>
<tr>
<td>Horizontal rule
</td>
<td><pre>Text before
----
Text after
</pre>
</td>
<td>
Text before

<hr>
Text after

</td></tr>
<tr>
<td>Bullet list
</td>
<td>
<pre>* Start each line
* with an [[Wikipedia:asterisk|asterisk]] (*).
** More asterisks give deeper
*** and deeper levels.
* Line breaks don't break levels.
*** But jumping levels creates empty space.
Any other start ends the list.

* combine bullet list
** with definition
::- definition
** creates empty space

* combine bullet list
** with definition
*:- definition
** without empty spaces

*bullet list
:- definition
:* sublist that doesn't create empty
:* spaces after definition
</pre>
</td>
<td>
<ul><li>Start each line</li>
<li>with an asterisk (*).
<ul><li>More asterisks give deeper
<ul><li>and deeper levels.</li></ul></li></ul></li>
<li>Line breaks don't break levels.
<ul><li><ul><li>But jumping levels creates empty space.</li></ul></li></ul></li></ul>
Any other start ends the list.

<ul><li>combine bullet list
<ul><li>with definition</li></ul></li></ul>
<dl><dd><dl><dd>- definition</dd></dl></dd></dl>
<ul><li><ul><li>creates empty space</li></ul></li></ul>
<ul><li>combine bullet list
<ul><li>with definition</li></ul>
<dl><dd>- definition</dd></dl>
<ul><li>without empty spaces</li></ul></li></ul>
<ul><li>bullet list</li></ul>
<dl><dd>- definition
<ul><li>sublist that doesn't create empty</li>
<li>spaces after definition</li></ul></dd></dl>
</td></tr>
<tr>
<td>Numbered list
</td>
<td>
<pre># Start each line
# with a [[Wikipedia:Number_sign|number sign]] (#).
## More number signs give deeper
### and deeper
### levels.
# Line breaks don't break levels.
### But jumping levels creates empty space.
# Blank lines

# end the list and start another.
Any other start also
ends the list.
</pre>
</td>
<td>
<ol><li>Start each line</li>
<li>with a number sign (#).
<ol><li>More number signs give deeper
<ol><li>and deeper</li>
<li>levels.</li></ol></li></ol></li>
<li>Line breaks don't break levels.
<ol><li><ol><li>But jumping levels creates empty space.</li></ol></li></ol></li>
<li>Blank lines</li></ol>
<ol><li>end the list and start another.</li></ol>
Any other start also
ends the list.

</td></tr>
<tr>
<td>Definition list
</td>
<td><pre>;item 1
: definition 1
;item 2
: definition 2-1
: definition 2-2
</pre>
</td>
<td>
<dl><dt>item 1</dt>
<dd>definition 1</dd>
<dt>item 2</dt>
<dd>definition 2-1</dd>
<dd>definition 2-2</dd></dl>
</td></tr>
<tr>
<td>Indent text
</td>
<td><pre>: Single indent
:: Double indent
::::: Multiple indent
</pre>
<hr>
<div role="note" class="note note-info" style="background-position:left 7px top 50%; padding-right: 0.5em; padding-left: 40px;">This workaround may harm accessibility.</div>
</td>
<td>
<dl><dd>Single indent
<dl><dd>Double indent
<dl><dd><dl><dd><dl><dd>Multiple indent</dd></dl></dd></dl></dd></dl></dd></dl></dd></dl>
</td></tr>
<tr>
<td>Mixture of different types of list
</td>
<td>
<pre># one
# two
#* two point one
#* two point two
# three
#; three item one
#: three def one
# four
#: four def one
#: this looks like a continuation
#: and is often used
#: instead of <nowiki> </nowiki>
# five
## five sub 1
### five sub 1 sub 1
## five sub 2
</pre>
<hr>
<div role="note" class="note note-info" style="background-position:left 7px top 50%; padding-right: 0.5em; padding-left: 40px;">The usage of <code>#:</code> and <code>*:</code> for breaking a line within an item may also harm accessibility.</div>
</td>
<td>
<ol><li>one</li>
<li>two
<ul><li>two point one</li>
<li>two point two</li></ul></li>
<li>three
<dl><dt>three item one</dt>
<dd>three def one</dd></dl></li>
<li>four
<dl><dd>four def one</dd>
<dd>this looks like a continuation</dd>
<dd>and is often used</dd>
<dd>instead of </dd></dl></li>
<li>five
<ol><li>five sub 1
<ol><li>five sub 1 sub 1</li></ol></li>
<li>five sub 2</li></ol></li></ol>
</td></tr>
<tr>
<td>Preformatted text
</td>
<td><pre> Start each line with a space.
Text is '''preformatted''' and
''markups'' '''''can''''' be done.
</pre>
<hr>
<div role="note" class="note note-info" style="background-position:left 7px top 50%; padding-right: 0.5em; padding-left: 40px;">This way of preformatting only applies to section formatting. Character formatting markups are still effective.</div>
</td>
<td>
<pre>Start each line with a space.
Text is preformatted and
markups can be done.
</pre>
</td></tr>
<tr>
<td>Preformatted text blocks
</td>
<td><pre> <nowiki>Start with a space in the first column,
(before the <nowiki>).

Then your block format will be
maintained.

This is good for copying in code blocks:

def function():
"""documentation string"""

if True:
print True
else:
print False</nowiki>
</pre>
</td>
<td>
<pre>Start with a space in the first column,
(before the <nowiki>).

Then your block format will be
maintained.

This is good for copying in code blocks:

def function():
"""documentation string"""

if True:
print True
else:
print False
</pre>
</td></tr></table>

=== Paragraphs ===

Knowledge Management system ignores single line breaks. To start a new paragraph, leave an empty line. You can force a line break within a paragraph with the HTML tag.

===HTML tags===

Some HTML tags are allowed in Knowledge Management system, for example 'code', 'div', and 'span'. These apply anywhere you insert them.

<table class="wikitable">
<tr>
<th style="text-align:center;padding:10px">Description
</th>
<th width="40%" style="text-align:center">You type
</th>
<th width="40%" style="text-align:center">You get
</th></tr>
<tr>
<td>Inserted (Displays as underline in most browsers)
</td>
<td><pre><ins>Inserted</ins>

or

Underline
</pre>
</td>
<td>
<ins>Inserted</ins>
or
Underline

</td></tr>
<tr>
<td>Deleted (Displays as strikethrough in most browsers)
</td>
<td><pre><s>Struck out</s>

or

<del>Deleted</del>

</pre>
</td>
<td>
<s>Struck out</s>
or
<del>Deleted</del>

</td></tr>
<tr>
<td>Fixed width text
</td>
<td><pre><code>Source code</code>

or

<code>Fixed width text</code>
</pre>
</td>
<td>
<code>Source code</code>
or
<code>Fixed width text</code>

</td></tr>
<tr>
<td>Blockquotes
</td>
<td><pre>Text before
<blockquote>Blockquote</blockquote>
Text after
</pre>
</td>
<td>
Text before

<blockquote>Blockquote</blockquote>
Text after

</td></tr>
<tr>
<td>Quotes
</td>
<td><pre><q>This is a quotation</q></pre>
<div role="note" class="note note-info" style="background-position:left 7px top 50%; padding-right: 0.5em; padding-left: 40px;">The q element must not be used in place of quotation marks that do not represent quotes; for example, it is inappropriate to use the q element for marking up sarcastic statements.[1]</div>
</td>
<td><q>This is a quotation</q>
</td></tr>
<tr>
<td>Comment
</td>
<td><pre>
Comments are visible only
in the edit zone.</pre>
</td>
<td>
Comments are visible only
in the edit zone.

</td></tr>
<tr>
<td>Completely preformatted text
</td>
<td><pre><pre>Text is '''preformatted''' and
''markups'' '''''cannot''''' be done</pre></pre>
<hr>
<div role="note" class="note note-info" style="background-position:left 7px top 50%; padding-right: 0.5em; padding-left: 40px;">For marking up of preformatted text, check the "Preformatted text" entry at the end of the previous table.</div>
</td>
<td>
<pre>Text is '''preformatted''' and
''markups'' '''''cannot''''' be done</pre>
</td></tr>
<tr>
<td>Customized preformatted text
</td>
<td><pre><pre style="color: red">Text is '''preformatted'''
with a style and
''markups'' '''''cannot''''' be done
</pre></pre>
<hr>
<div role="note" class="note note-info" style="background-position:left 7px top 50%; padding-right: 0.5em; padding-left: 40px;">A CSS style can be named within the <code>style</code> attribute.</div>
</td>
<td>
<pre style="color: red">Text is '''preformatted'''
with a style and
''markups'' '''''cannot''''' be done</pre>
</td></tr></table>

===Inserting symbols===

Symbols and other special characters not available on your keyboard can be inserted in a multitude of ways. Many Operating Systems and browsers allow you to insert special characters through a menu option or Operating System panel. Additionally, you can use the Knowledge Management system Editor or VisualEditor to insert them into the edit screen.

As a last resort, you can use a special sequence of characters. Those sequences are called HTML entities. For example, the following sequence (entity) → when inserted will be shown as right arrow HTML symbol → and — when inserted will be shown as an em dash HTML symbol —.
<hr>
<div role="note" class="note note-info" style="background-position:left 7px top 50%; padding-right: 0.5em; padding-left: 40px;">Hover over any character to find out the symbol that it produces. Some symbols not available in the current font will appear as empty squares.</div>

<table class="wikitable" align="center" width="100%">
<tr>
<th colspan="32" style="text-align:center;padding:10px">HTML symbol entities
</th></tr>
<tr align="center">
<td>Á
</td>
<td>á
</td>
<td>Â
</td>
<td>â
</td>
<td>´
</td>
<td>Æ
</td>
<td>æ
</td>
<td>À
</td>
<td>à
</td>
<td>ℵ
</td>
<td>Α
</td>
<td>α
</td>
<td>&
</td>
<td>∧
</td>
<td>∠
</td>
<td>Å
</td>
<td>å
</td>
<td>≈
</td>
<td>Ã
</td>
<td>ã
</td>
<td>Ä
</td>
<td>ä
</td>
<td>„
</td>
<td>Β
</td>
<td>β
</td>
<td>¦
</td>
<td>•
</td>
<td>∩
</td>
<td>Ç
</td>
<td>ç
</td>
<td>¸
</td>
<td>¢
</td></tr>
<tr align="center">
<td>Χ
</td>
<td>χ
</td>
<td>ˆ
</td>
<td>♣
</td>
<td>≅
</td>
<td>©
</td>
<td>↵
</td>
<td>∪
</td>
<td>¤
</td>
<td>†
</td>
<td>‡
</td>
<td>↓
</td>
<td>⇓
</td>
<td>°
</td>
<td>Δ
</td>
<td>δ
</td>
<td>♦
</td>
<td>÷
</td>
<td>É
</td>
<td>é
</td>
<td>Ê
</td>
<td>ê
</td>
<td>È
</td>
<td>è
</td>
<td>∅
</td>
<td>&emsp;
</td>
<td>&ensp;
</td>
<td>Ε
</td>
<td>ε
</td>
<td>≡
</td>
<td>Η
</td>
<td>η
</td></tr>
<tr align="center">
<td>Ð
</td>
<td>ð
</td>
<td>Ë
</td>
<td>ë
</td>
<td>€
</td>
<td>∃
</td>
<td>ƒ
</td>
<td>∀
</td>
<td>½
</td>
<td>¼
</td>
<td>¾
</td>
<td>⁄
</td>
<td>Γ
</td>
<td>γ
</td>
<td>≥
</td>
<td>>
</td>
<td>↔
</td>
<td>⇔
</td>
<td>♥
</td>
<td>…
</td>
<td>Í
</td>
<td>í
</td>
<td>Î
</td>
<td>î
</td>
<td>¡
</td>
<td>Ì
</td>
<td>ì
</td>
<td>ℑ
</td>
<td>∞
</td>
<td>∫
</td>
<td>Ι
</td>
<td>ι
</td></tr>
<tr align="center">
<td>¿
</td>
<td>∈
</td>
<td>Ï
</td>
<td>ï
</td>
<td>Κ
</td>
<td>κ
</td>
<td>Λ
</td>
<td>λ
</td>
<td>〈
</td>
<td>«
</td>
<td>←
</td>
<td>⇐
</td>
<td>⌈
</td>
<td>“
</td>
<td>≤
</td>
<td>⌊
</td>
<td>∗
</td>
<td>◊
</td>
<td>&lrm;
</td>
<td>‹
</td>
<td>‘
</td>
<td><
</td>
<td>¯
</td>
<td>—
</td>
<td>µ
</td>
<td>·
</td>
<td>−
</td>
<td>Μ
</td>
<td>μ
</td>
<td>∇
</td>
<td> 
</td>
<td>–
</td></tr>
<tr align="center">
<td>≠
</td>
<td>∋
</td>
<td>¬
</td>
<td>∉
</td>
<td>⊄
</td>
<td>Ñ
</td>
<td>ñ
</td>
<td>Ν
</td>
<td>ν
</td>
<td>Ó
</td>
<td>ó
</td>
<td>Ô
</td>
<td>ô
</td>
<td>Œ
</td>
<td>œ
</td>
<td>Ò
</td>
<td>ò
</td>
<td>‾
</td>
<td>Ω
</td>
<td>ω
</td>
<td>Ο
</td>
<td>ο
</td>
<td>⊕
</td>
<td>∨
</td>
<td>ª
</td>
<td>º
</td>
<td>Ø
</td>
<td>ø
</td>
<td>Õ
</td>
<td>õ
</td>
<td>⊗
</td>
<td>Ö
</td></tr>
<tr align="center">
<td>ö
</td>
<td>¶
</td>
<td>∂
</td>
<td>‰
</td>
<td>⊥
</td>
<td>Φ
</td>
<td>φ
</td>
<td>Π
</td>
<td>π
</td>
<td>ϖ
</td>
<td>±
</td>
<td>£
</td>
<td>′
</td>
<td>″
</td>
<td>∏
</td>
<td>∝
</td>
<td>Ψ
</td>
<td>ψ
</td>
<td>"
</td>
<td>√
</td>
<td>〉
</td>
<td>»
</td>
<td>→
</td>
<td>⇒
</td>
<td>⌉
</td>
<td>”
</td>
<td>ℜ
</td>
<td>®
</td>
<td>⌋
</td>
<td>Ρ
</td>
<td>ρ
</td>
<td>&rlm;
</td></tr>
<tr align="center">
<td>›
</td>
<td>’
</td>
<td>‚
</td>
<td>Š
</td>
<td>š
</td>
<td>⋅
</td>
<td>§
</td>
<td>
</td>
<td>Σ
</td>
<td>σ
</td>
<td>ς
</td>
<td>∼
</td>
<td>♠
</td>
<td>⊂
</td>
<td>⊆
</td>
<td>∑
</td>
<td>⊃
</td>
<td>¹
</td>
<td>²
</td>
<td>³
</td>
<td>⊇
</td>
<td>ß
</td>
<td>Τ
</td>
<td>τ
</td>
<td>∴
</td>
<td>Θ
</td>
<td>θ
</td>
<td>ϑ
</td>
<td> 
</td>
<td>Þ
</td>
<td>þ
</td>
<td>˜
</td></tr>
<tr align="center">
<td>×
</td>
<td>™
</td>
<td>Ú
</td>
<td>ú
</td>
<td>↑
</td>
<td>⇑
</td>
<td>Û
</td>
<td>û
</td>
<td>Ù
</td>
<td>ù
</td>
<td>¨
</td>
<td>ϒ
</td>
<td>Υ
</td>
<td>υ
</td>
<td>Ü
</td>
<td>ü
</td>
<td>℘
</td>
<td>Ξ
</td>
<td>ξ
</td>
<td>Ý
</td>
<td>ý
</td>
<td>¥
</td>
<td>ÿ
</td>
<td>Ÿ
</td>
<td>Ζ
</td>
<td>ζ
</td>
<td>&zwj;
</td>
<td>&zwnj;
</td></tr></table>

<table class="wikitable">
<tr>
<th style="text-align:center;padding:10px">Description
</th>
<th width="40%" style="text-align:center;">You type
</th>
<th width="40%" style="text-align:center;">You get
</th></tr>
<tr>
<td>Copyright symbol
</td>
<td class="mw-code">&copy;
</td>
<td>
<dl><dd><dl><dd><dl><dd>©</dd></dl></dd></dl></dd></dl>
</td></tr>
<tr>
<td>Greek delta letter symbol
</td>
<td class="mw-code">&delta;
</td>
<td>
<dl><dd><dl><dd><dl><dd>δ</dd></dl></dd></dl></dd></dl>
</td></tr>
<tr>
<td>Euro currency symbol
</td>
<td class="mw-code">&euro;
</td>
<td>
<dl><dd><dl><dd><dl><dd>€</dd></dl></dd></dl></dd></dl>
</td></tr></table>

See the list of all HTML entities on the Wikipedia article List of HTML entities. Additionally, Knowledge Management system supports two non-standard entity reference sequences: &רלמ; and &رلم; which are both considered equivalent to &rlm; which is a right-to-left mark. (Used when combining right to left languages with left to right languages in the same page.)

===HTML tags and symbol entities displayed themselves (with and without interpreting them)===

<dl><dd><code>&amp;euro;</code>  → &euro;</dd></dl>
<dl><dd><code>Typo to be corrected</code>  → Typo to be corrected</dd></dl>
<dl><dd><code>&lt;span style="color: red; text-decoration: line-through;">Typo to be corrected</code>  → Typo to be corrected</dd></dl>

==Nowiki for HTML==

<nowiki /> can prohibit (HTML) tags:

<ul><li><<nowiki />pre>  → <pre></li></ul>
But not & symbol escapes:

<ul><li>&<nowiki />amp;  → &</li></ul>
To print & symbol escapes as text, use "<code>&amp;</code>" to replace the "&" character (eg. type "<code>&amp;nbsp;</code>", which results in "<code>&nbsp;</code>").


Normal and sysop users cannot permanently delete a Knowledge Management system page, but sysops can delete a page such that it could still be restored. This is a deliberate design feature, and is an important part of why Knowledge Management system's work. Every kind of editing operation can be reverted by any other user, and that includes resurrecting deleted content. It doesn't cause significant wasted space; and with nothing but a 'delete' label, the page is effectively deleted anyway.

Deleting a page is, on the other hand, a straightforward operation for anyone with sysop permissions: it allows to semi-permanently remove a page from the Knowledge Management system, until a sysop undeletes (restores) it with the same ease. Typically sysops might look for delete labels, and do a proper delete on these pages, after a period of time. If for some reason you need a page to be deleted more quickly than that, you will need to contact a sysop to request this.

Revision deletion offers a more granular feature of deletion for edits with peculiar problems.

===Before deleting===

Sysops should also be aware of the general advice given on When not to delete a page: in particular, there are many situations where a deletion is too drastic. For example, a redirect is often more appropriate.

Before deleting you could perform various checks:

*'''Use the "What links here" tool. This gives an indication as to how important a page is, and what subjects it relates to. Perhaps the page is still linked to prominently from many places. All incoming links will become red links if you proceed with the delete. Ideally all incoming links should be changed/removed, if there is genuinely no need for this page to exist. You could do this work prior to deleting, or ask others in the Knowledge Management system community to do it.
*'''Check the page history and the associated talk page. Who was proposing the deletion? Does anyone disagree? Has it been properly discussed? Did people have adequate time to raise objections? Did somebody vandalize a page, which then led to a deletion proposal?

The care taken over these things might depend on the size of the Knowledge Management system community, and how clear-cut the case for deletion is. Remember that only sysop users can undo a delete action, so to a normal user the information appears to be lost forever.

===Use the 'delete' action===

Sysops should see a 'delete' tab or action menu option at the top of every page. To find the action menu, look for a down arrow or triangle next to the "View History" tab. If you mouse over the triangle you should see "delete", "move", "protect" and "watch". Click the delete action to delete the page. When using browsers which support keyboard shortcuts, you can also use (Control-Alt-D). You will be asked to confirm, and to supply a "Reason for deletion". This is a short textual description of why the page is being deleted. Your action will appear on the recent changes display, and in the deletion log ([[Special:Log]]).

Remember only the administrator can delete uploaded photograph files.

===Undeleting===

To undelete a page you must navigate to the exact page name of the page.
You should then see a link to "View or restore n deleted edits". Tick the box next to the revision you wish to restore.

===Configuring deletion reasons===
The list of reasons in the dropdown box is maintained at [[Help:Deletereason-dropdown]].

===When not to delete a page===

Typically you would delete a page if the contents are entirely inappropriate and do not match the purposes of the Knowledge Management system. In other situations, you would take a less extreme course of action, for example:

*'''The page should have a different title. See [[Help:Moving a page]].
*'''The contents should have been placed on a different page -- Add the contents to the other page, and then supply a redirect. See Help:Redirects.
*'''The contents are already on a different page -- Delete the duplicate content and leave a redirect. That way, the page title, which made sense to somebody, will helpfully redirect to the information.
*'''The page is out-of-date -- Re-word sentences to be in the past tense, to make the page a historical record. Alternatively, label the information as out-of-date, with a warning notice.

An actual delete is generally necessary only if the title of the page is inappropriate. In other situations, a merge and redirect is more appropriate.

===Proposing changes===

Deciding on appropriate content/page titles can be a difficult aspect of Knowledge Management system organization, and one which can often provoke debates. If the merge or deletion you have in mind is one which might cause upset, you should propose the change first. Do this by leaving a note to give your reasons on the talk page. You might also establish a system for labeling the page with a delete/merge proposal template, to make everybody aware of your intentions.

===Unlinking a page===

The 'What links here' toolbox feature (bottom of left sidebar) will tell you which other Knowledge Management system pages link to the current page. Always use this feature to check before proceeding with deleting. These related pages will need to be edited for their links to reflect the change.

*'''[[Help:Starting a new page]]
*'''[[Help:Moving a page]]
*'''[[Help:Admin deleting and undeleting]]
*'''[[Help:Formating]]
*'''[[Help:Links]]
*'''[[Help:List]]
*'''[[Help:Images]]
*'''[[Help:Tables]]

Help:Admin deleting and undeleting

2019-01-11T08:11:13Z

Ufo: Created page with "Normal and admin users cannot permanently delete a Knowledge Management system page, but admins can delete a page such that it could still be restored. This is a deliberate de..."

Normal and admin users cannot permanently delete a Knowledge Management system page, but admins can delete a page such that it could still be restored. This is a deliberate design feature, and is an important part of why Knowledge Management system's work. Every kind of editing operation can be reverted by any other user, and that includes resurrecting deleted content. It doesn't cause significant wasted space; and with nothing but a 'delete' label, the page is effectively deleted anyway.

Deleting a page is, on the other hand, a straightforward operation for anyone with admin permissions: it allows to semi-permanently remove a page from the Knowledge Management system, until a admin undeletes (restores) it with the same ease. Typically admins might look for delete labels, and do a proper delete on these pages, after a period of time. If for some reason you need a page to be deleted more quickly than that, you will need to contact a admin to request this.

Revision deletion offers a more granular feature of deletion for edits with peculiar problems.

===Before deleting===

Admins should also be aware of the general advice given on When not to delete a page: in particular, there are many situations where a deletion is too drastic. For example, a redirect is often more appropriate.

Before deleting you could perform various checks:

*'''Use the "What links here" tool. This gives an indication as to how important a page is, and what subjects it relates to. Perhaps the page is still linked to prominently from many places. All incoming links will become red links if you proceed with the delete. Ideally all incoming links should be changed/removed, if there is genuinely no need for this page to exist. You could do this work prior to deleting, or ask others in the Knowledge Management system community to do it.
*'''Check the page history and the associated talk page. Who was proposing the deletion? Does anyone disagree? Has it been properly discussed? Did people have adequate time to raise objections? Did somebody vandalize a page, which then led to a deletion proposal?

The care taken over these things might depend on the size of the Knowledge Management system community, and how clear-cut the case for deletion is. Remember that only admin users can undo a delete action, so to a normal user the information appears to be lost forever.

===Use the 'delete' action===

Admins should see a 'delete' tab or action menu option at the top of every page. To find the action menu, look for a down arrow or triangle next to the "View History" tab. If you mouse over the triangle you should see "delete", "move", "protect" and "watch". Click the delete action to delete the page. When using browsers which support keyboard shortcuts, you can also use (Control-Alt-D). You will be asked to confirm, and to supply a "Reason for deletion". This is a short textual description of why the page is being deleted. Your action will appear on the recent changes display, and in the deletion log ([[Special:Log]]).

Remember only the administrator can delete uploaded photograph files.

===Undeleting===

To undelete a page you must navigate to the exact page name of the page.
You should then see a link to "View or restore n deleted edits". Tick the box next to the revision you wish to restore.

===Configuring deletion reasons===
The list of reasons in the dropdown box is maintained at [[Help:Deletereason-dropdown]].

===When not to delete a page===

Typically you would delete a page if the contents are entirely inappropriate and do not match the purposes of the Knowledge Management system. In other situations, you would take a less extreme course of action, for example:

*'''The page should have a different title. See [[Help:Moving a page]].
*'''The contents should have been placed on a different page -- Add the contents to the other page, and then supply a redirect. See Help:Redirects.
*'''The contents are already on a different page -- Delete the duplicate content and leave a redirect. That way, the page title, which made sense to somebody, will helpfully redirect to the information.
*'''The page is out-of-date -- Re-word sentences to be in the past tense, to make the page a historical record. Alternatively, label the information as out-of-date, with a warning notice.

An actual delete is generally necessary only if the title of the page is inappropriate. In other situations, a merge and redirect is more appropriate.

===Proposing changes===

Deciding on appropriate content/page titles can be a difficult aspect of Knowledge Management system organization, and one which can often provoke debates. If the merge or deletion you have in mind is one which might cause upset, you should propose the change first. Do this by leaving a note to give your reasons on the talk page. You might also establish a system for labeling the page with a delete/merge proposal template, to make everybody aware of your intentions.

===Unlinking a page===

The 'What links here' toolbox feature (bottom of left sidebar) will tell you which other Knowledge Management system pages link to the current page. Always use this feature to check before proceeding with deleting. These related pages will need to be edited for their links to reflect the change.

*'''[[Help:Starting a new page]]
*'''[[Help:Moving a page]]
*'''[[Help:Admin deleting and undeleting]]
*'''[[Help:Formating]]
*'''[[Help:Links]]
*'''[[Help:List]]
*'''[[Help:Images]]
*'''[[Help:Tables]]

Help:Moving a page

2019-01-11T08:09:39Z

Ufo:

Moving (renaming) a page means giving it another name. This is done by using the "move" tab at the top. The tab is not visible if you are not logged in. Then simply enter the new name and click "Move page". Normally you would want to leave the "Move associated talk page" option ticked.

If you move page "A" to a new title "B", this operation will do the following:

*'''Renames the title of page "A" as "B"
*'''Renames all the editing history of page "A" as of page "B" as well
*'''Creates a new page "A", whose content is a redirect to page "B"

The second point is important. By using the "Move" feature, you also move the editing history, which is desirable in most situations. The editing history allows people to see how the contents of the page were built up, and who contributed what. If you move contents around by copying and pasting (not using the move feature), you do not achieve this (see also Help:Tracking changes).

When the move operation leaves behind a redirect (see Help:Redirects), it should not result in any broken links except the possibility of double redirects – that is, pages redirecting to "A" which becomes a redirect itself. You might want to hunt down pages or other redirects which link in to the redirect, and change their text to link directly to the new title. The "What links here" feature, which can be used through the link in the Tools (at bottom of the sidebar on the left) is useful when doing this.

===Proposing a move===

Deciding on a page title can be a difficult aspect of Knowledge Management system organization, and one which can often provoke debates. If the move you have in mind is one which might cause upset or could be considered controversial, you should propose the move first. Do this by leaving a note giving your reasons on the talk page. You might also establish a system for labeling the page itself, with a move proposal template, to make everybody aware of your intentions.

===Undo a move===

As with almost all Knowledge Management system editing, a move operation can be reversed (by any user). To reverse a move operation, simply move the page back, e.g. move page "B" back to "A".

The page title "B" will still be left behind, as a redirect from "B" to "A". Any user can remove the redirect and propose that the page be deleted. However the final deletion will require sysop privileges

===Moving a page without creating a redirect===

Users with the suppressredirect user right can optionally move a page without creating a redirect. This is particularly useful when undoing a move.

When the right is enabled, one additional check box will appear when one needs to move a page (see picture at right).

===Mass renaming / moving===

Knowledge Management system does not offer a special page with which to perform a batch operation for page moves. There may be alternatives, depending on your situation

===Moving subpages===

Users with the move-subpages user right can optionally move subpages of a page, preserving its "tree" structure. If you specify the root page you want to move in the title (by visiting Special:MovePage/Some_page), the special page displays the subpages of that root page.

*'''[[Help:Starting a new page]]
*'''[[Help:Moving a page]]
*'''[[Help:Admin deleting and undeleting]]
*'''[[Help:Formating]]
*'''[[Help:Links]]
*'''[[Help:List]]
*'''[[Help:Images]]
*'''[[Help:Tables]]

Help:Starting a new page

2019-01-11T08:09:18Z

Ufo:

There are several ways to start a new page.

These can vary based on the type of page started, as well as the Knowledge Management system and namespace.

=== Using Knowledge Management system links ===

Knowledge Management system makes it easy to link pages using standard syntax
If you (or anyone else) create a link to an article that doesn't exist yet, the link will be colored red, like this.

Notes:
*'''This sample displays that underline style unconditionally. The underline displayed below the text of actual links will normally be hidden by default and made visible only when the link is hovered by the mouse or selected by keyboard navigation, if the Knowledge Management system (or the user's preferences) uses the default Knowledge Management system styles.
*'''The actual color of links is also dependent on the default Knowledge Management system styles, and the design of Knowledge Management system pages may still override these default colors.

Clicking a red link will take you to the edit page for the new article.

Simply type your text, click save and the new page will be created.

Once the page has been created, the link will change from red to blue (purple for pages you've visited) indicating that the article now exists.

Usually this is the best way to create a new page, because it means that right from the start, the page will be linked from at least one other place on the Knowledge Management system (and typically you will want to mesh it into other related pages later).

If you are creating a new page without creating any link to it, you may need to ask yourself: Does this page really fit in with the topics already covered in the Knowledge Management system?

Also, how are you expecting visitors to find this page?

Normally there is no reason to create a page without first creating a red link to it.

=== From the search box ===

If you search for a page that doesn't exist (using the search box and "Go" button on the left of the page) then you will be provided with a link to create the new page.

=== Using the URL ===

You can use the Knowledge Management system's URL for creating a new page.

The URL to an article of the Knowledge Management system is usually something like this:

*'''http://www.enterpriseplus.tools/index.php?title=ARTICLE

If you replace ARTICLE with the name of the page you wish to create, you will be taken to a blank page which indicates that no article of that name exists yet.

Clicking the "Edit" page tab at the top of the page will take you to the edit page for that article, where you can create the new page by typing your text, and clicking submit.

=== Create redirects to your new page ===

Don't forget to set up redirects when you create a page.

If you think another person may search for the page you've created by using a different name or spelling, please create the proper redirect(s).

=== Protecting your new page ===

Normally a new Knowledge Management system page can be edited by other people (that is one of the main ideas of a Knowledge Management system!).

However, an Administrator could protect the page, if desired, to prevent normal users from editing it.

*'''[[Help:Starting a new page]]
*'''[[Help:Moving a page]]
*'''[[Help:Admin deleting and undeleting]]
*'''[[Help:Formating]]
*'''[[Help:Links]]
*'''[[Help:List]]
*'''[[Help:Images]]
*'''[[Help:Tables]]

Need help

2019-01-11T08:08:48Z

Ufo:

= Need help? =

== It's very easy to edit the contents within the Knowledge Management system ==

#Click the "Edit" page tab at the top right of the page.
#Make changes to the text.
#Click the "Save page" button.

=== Editing rules, editing conventions, and formatting===

The number one rule of editing is to be bold. Go ahead - make changes. Other people can correct any mistakes you make, so have confidence, and give it a try! There are all kinds of editing conventions, rules, and philosophies for the editing of + pages, but the be bold rule is the most important of these!

An edit can contribute whole new paragraphs or pages of information, or it can be as simple as fixing a typo or a spelling mistake. In general, try to add or edit text so that it is clear and concise. Most importantly, make sure you are always aiming to do something which improves the contents of the Knowledge Management system.

When you need to use some type of formatting, such as for new headings or bolding of text, you do this using Knowledge Management system markup syntax.

See Help:Formatting for some of the common types of formatting used.

=== Edit summary ===

Before you save a change, you can enter a short note (must be shorter than 500 characters) in the "Summary (?):" box describing your changes. Don't worry too much about this, or spend too much time thinking about it: just put in a short description of what you just changed. For example, you might say "fixed typo" or "added more information about sunflowers".

This summary gets stored alongside your edit, and allows people to track changes in the Knowledge Management system more effectively.

===Preview===

It's a good idea to use the "Show preview" button to see what your change will look like, before you save it. This is also related to tracking changes because every time you save, this is displayed to others as a separate change. This isn't something to worry about too much, but it's good to get into the habit of eliminating mistakes in your own work, by using a preview before saving, rather than saving, then having to do another edit just to make one or more minor corrections.

===Show changes===

Another option is the "Show changes" button which allows you to see the differences between the current version and the edited version.

===Protected pages===

Pages that are protected cannot be edited by anyone except users of a specific group. Protected pages will instead display "View source" instead of edit. In that case, to edit a protected page, contact a user who has permission to edit the page.

===Other types of editing===

With Knowledge Management system edits you can start a new page, move (or rename) a page, or even delete a page:

*'''[[Help:Starting a new page]]
*'''[[Help:Moving a page]]
*'''[[Help:Admin deleting and undeleting]]
*'''[[Help:Formating]]
*'''[[Help:Links]]
*'''[[Help:List]]
*'''[[Help:Images]]
*'''[[Help:Tables]]

Remember you should always aim to improve the overall contents of the Knowledge Management system with your edits.

Help:Sysop deleting and undeleting

2019-01-11T08:08:25Z

Ufo:

Normal and sysop users cannot permanently delete a Knowledge Management system page, but sysops can delete a page such that it could still be restored. This is a deliberate design feature, and is an important part of why Knowledge Management system's work. Every kind of editing operation can be reverted by any other user, and that includes resurrecting deleted content. It doesn't cause significant wasted space; and with nothing but a 'delete' label, the page is effectively deleted anyway.

Deleting a page is, on the other hand, a straightforward operation for anyone with sysop permissions: it allows to semi-permanently remove a page from the Knowledge Management system, until a sysop undeletes (restores) it with the same ease. Typically sysops might look for delete labels, and do a proper delete on these pages, after a period of time. If for some reason you need a page to be deleted more quickly than that, you will need to contact a sysop to request this.

Revision deletion offers a more granular feature of deletion for edits with peculiar problems.

===Before deleting===

Sysops should also be aware of the general advice given on When not to delete a page: in particular, there are many situations where a deletion is too drastic. For example, a redirect is often more appropriate.

Before deleting you could perform various checks:

*'''Use the "What links here" tool. This gives an indication as to how important a page is, and what subjects it relates to. Perhaps the page is still linked to prominently from many places. All incoming links will become red links if you proceed with the delete. Ideally all incoming links should be changed/removed, if there is genuinely no need for this page to exist. You could do this work prior to deleting, or ask others in the Knowledge Management system community to do it.
*'''Check the page history and the associated talk page. Who was proposing the deletion? Does anyone disagree? Has it been properly discussed? Did people have adequate time to raise objections? Did somebody vandalize a page, which then led to a deletion proposal?

The care taken over these things might depend on the size of the Knowledge Management system community, and how clear-cut the case for deletion is. Remember that only sysop users can undo a delete action, so to a normal user the information appears to be lost forever.

===Use the 'delete' action===

Sysops should see a 'delete' tab or action menu option at the top of every page. To find the action menu, look for a down arrow or triangle next to the "View History" tab. If you mouse over the triangle you should see "delete", "move", "protect" and "watch". Click the delete action to delete the page. When using browsers which support keyboard shortcuts, you can also use (Control-Alt-D). You will be asked to confirm, and to supply a "Reason for deletion". This is a short textual description of why the page is being deleted. Your action will appear on the recent changes display, and in the deletion log ([[Special:Log]]).

Remember only the administrator can delete uploaded photograph files.

===Undeleting===

To undelete a page you must navigate to the exact page name of the page.
You should then see a link to "View or restore n deleted edits". Tick the box next to the revision you wish to restore.

===Configuring deletion reasons===
The list of reasons in the dropdown box is maintained at [[Help:Deletereason-dropdown]].

===When not to delete a page===

Typically you would delete a page if the contents are entirely inappropriate and do not match the purposes of the Knowledge Management system. In other situations, you would take a less extreme course of action, for example:

*'''The page should have a different title. See [[Help:Moving a page]].
*'''The contents should have been placed on a different page -- Add the contents to the other page, and then supply a redirect. See Help:Redirects.
*'''The contents are already on a different page -- Delete the duplicate content and leave a redirect. That way, the page title, which made sense to somebody, will helpfully redirect to the information.
*'''The page is out-of-date -- Re-word sentences to be in the past tense, to make the page a historical record. Alternatively, label the information as out-of-date, with a warning notice.

An actual delete is generally necessary only if the title of the page is inappropriate. In other situations, a merge and redirect is more appropriate.

===Proposing changes===

Deciding on appropriate content/page titles can be a difficult aspect of Knowledge Management system organization, and one which can often provoke debates. If the merge or deletion you have in mind is one which might cause upset, you should propose the change first. Do this by leaving a note to give your reasons on the talk page. You might also establish a system for labeling the page with a delete/merge proposal template, to make everybody aware of your intentions.

===Unlinking a page===

The 'What links here' toolbox feature (bottom of left sidebar) will tell you which other Knowledge Management system pages link to the current page. Always use this feature to check before proceeding with deleting. These related pages will need to be edited for their links to reflect the change.

*'''[[Help:Starting a new page]]
*'''[[Help:Moving a page]]
*'''[[Help:Admin deleting and undeleting]]
*'''[[Help:Formating]]
*'''[[Help:Links]]
*'''[[Help:List]]
*'''[[Help:Images]]
*'''[[Help:Tables]]

Help:Moving a page

2019-01-11T08:07:16Z

Ufo:

Moving (renaming) a page means giving it another name. This is done by using the "move" tab at the top. The tab is not visible if you are not logged in. Then simply enter the new name and click "Move page". Normally you would want to leave the "Move associated talk page" option ticked.

If you move page "A" to a new title "B", this operation will do the following:

*'''Renames the title of page "A" as "B"
*'''Renames all the editing history of page "A" as of page "B" as well
*'''Creates a new page "A", whose content is a redirect to page "B"

The second point is important. By using the "Move" feature, you also move the editing history, which is desirable in most situations. The editing history allows people to see how the contents of the page were built up, and who contributed what. If you move contents around by copying and pasting (not using the move feature), you do not achieve this (see also Help:Tracking changes).

When the move operation leaves behind a redirect (see Help:Redirects), it should not result in any broken links except the possibility of double redirects – that is, pages redirecting to "A" which becomes a redirect itself. You might want to hunt down pages or other redirects which link in to the redirect, and change their text to link directly to the new title. The "What links here" feature, which can be used through the link in the Tools (at bottom of the sidebar on the left) is useful when doing this.

===Proposing a move===

Deciding on a page title can be a difficult aspect of Knowledge Management system organization, and one which can often provoke debates. If the move you have in mind is one which might cause upset or could be considered controversial, you should propose the move first. Do this by leaving a note giving your reasons on the talk page. You might also establish a system for labeling the page itself, with a move proposal template, to make everybody aware of your intentions.

===Undo a move===

As with almost all Knowledge Management system editing, a move operation can be reversed (by any user). To reverse a move operation, simply move the page back, e.g. move page "B" back to "A".

The page title "B" will still be left behind, as a redirect from "B" to "A". Any user can remove the redirect and propose that the page be deleted. However the final deletion will require sysop privileges

===Moving a page without creating a redirect===

Users with the suppressredirect user right can optionally move a page without creating a redirect. This is particularly useful when undoing a move.

When the right is enabled, one additional check box will appear when one needs to move a page (see picture at right).

===Mass renaming / moving===

Knowledge Management system does not offer a special page with which to perform a batch operation for page moves. There may be alternatives, depending on your situation

===Moving subpages===

Users with the move-subpages user right can optionally move subpages of a page, preserving its "tree" structure. If you specify the root page you want to move in the title (by visiting Special:MovePage/Some_page), the special page displays the subpages of that root page.

*'''[[Help:Starting a new page]]
*'''[[Help:Moving a page]]
*'''[[Help:Sysop deleting and undeleting]]
*'''[[Help:Formating]]
*'''[[Help:Links]]
*'''[[Help:List]]
*'''[[Help:Images]]
*'''[[Help:Tables]]

Help:Starting a new page

2019-01-11T08:06:39Z

Ufo:

There are several ways to start a new page.

These can vary based on the type of page started, as well as the Knowledge Management system and namespace.

=== Using Knowledge Management system links ===

Knowledge Management system makes it easy to link pages using standard syntax
If you (or anyone else) create a link to an article that doesn't exist yet, the link will be colored red, like this.

Notes:
*'''This sample displays that underline style unconditionally. The underline displayed below the text of actual links will normally be hidden by default and made visible only when the link is hovered by the mouse or selected by keyboard navigation, if the Knowledge Management system (or the user's preferences) uses the default Knowledge Management system styles.
*'''The actual color of links is also dependent on the default Knowledge Management system styles, and the design of Knowledge Management system pages may still override these default colors.

Clicking a red link will take you to the edit page for the new article.

Simply type your text, click save and the new page will be created.

Once the page has been created, the link will change from red to blue (purple for pages you've visited) indicating that the article now exists.

Usually this is the best way to create a new page, because it means that right from the start, the page will be linked from at least one other place on the Knowledge Management system (and typically you will want to mesh it into other related pages later).

If you are creating a new page without creating any link to it, you may need to ask yourself: Does this page really fit in with the topics already covered in the Knowledge Management system?

Also, how are you expecting visitors to find this page?

Normally there is no reason to create a page without first creating a red link to it.

=== From the search box ===

If you search for a page that doesn't exist (using the search box and "Go" button on the left of the page) then you will be provided with a link to create the new page.

=== Using the URL ===

You can use the Knowledge Management system's URL for creating a new page.

The URL to an article of the Knowledge Management system is usually something like this:

*'''http://www.enterpriseplus.tools/index.php?title=ARTICLE

If you replace ARTICLE with the name of the page you wish to create, you will be taken to a blank page which indicates that no article of that name exists yet.

Clicking the "Edit" page tab at the top of the page will take you to the edit page for that article, where you can create the new page by typing your text, and clicking submit.

=== Create redirects to your new page ===

Don't forget to set up redirects when you create a page.

If you think another person may search for the page you've created by using a different name or spelling, please create the proper redirect(s).

=== Protecting your new page ===

Normally a new Knowledge Management system page can be edited by other people (that is one of the main ideas of a Knowledge Management system!).

However, an Administrator could protect the page, if desired, to prevent normal users from editing it.

*'''[[Help:Starting a new page]]
*'''[[Help:Moving a page]]
*'''[[Help:Sysop deleting and undeleting]]
*'''[[Help:Formating]]
*'''[[Help:Links]]
*'''[[Help:List]]
*'''[[Help:Images]]
*'''[[Help:Tables]]

Need help

2018-08-30T06:22:46Z

Ufo:

= Need help? =

== It's very easy to edit the contents within the Knowledge Management system ==

#Click the "Edit" page tab at the top right of the page.
#Make changes to the text.
#Click the "Save page" button.

=== Editing rules, editing conventions, and formatting===

The number one rule of editing is to be bold. Go ahead - make changes. Other people can correct any mistakes you make, so have confidence, and give it a try! There are all kinds of editing conventions, rules, and philosophies for the editing of + pages, but the be bold rule is the most important of these!

An edit can contribute whole new paragraphs or pages of information, or it can be as simple as fixing a typo or a spelling mistake. In general, try to add or edit text so that it is clear and concise. Most importantly, make sure you are always aiming to do something which improves the contents of the Knowledge Management system.

When you need to use some type of formatting, such as for new headings or bolding of text, you do this using wiki markup syntax.

See Help:Formatting for some of the common types of formatting used.

=== Edit summary ===

Before you save a change, you can enter a short note (must be shorter than 500 characters) in the "Summary (?):" box describing your changes. Don't worry too much about this, or spend too much time thinking about it: just put in a short description of what you just changed. For example, you might say "fixed typo" or "added more information about sunflowers".

This summary gets stored alongside your edit, and allows people to track changes in the Knowledge Management system more effectively.

===Preview===

It's a good idea to use the "Show preview" button to see what your change will look like, before you save it. This is also related to tracking changes because every time you save, this is displayed to others as a separate change. This isn't something to worry about too much, but it's good to get into the habit of eliminating mistakes in your own work, by using a preview before saving, rather than saving, then having to do another edit just to make one or more minor corrections.

===Show changes===

Another option is the "Show changes" button which allows you to see the differences between the current version and the edited version.

===Protected pages===

Pages that are protected cannot be edited by anyone except users of a specific group. Protected pages will instead display "View source" instead of edit. In that case, to edit a protected page, contact a user who has permission to edit the page.

===Other types of editing===

With Knowledge Management system edits you can start a new page, move (or rename) a page, or even delete a page:

*'''[[Help:Starting a new page]]
*'''[[Help:Moving a page]]
*'''[[Help:Sysop deleting and undeleting]]

Remember you should always aim to improve the overall contents of the Knowledge Management system with your edits.

{{DisplayCategory: Help}}

Need help

2018-08-30T06:19:32Z

Ufo:

= Need help? =

== It's very easy to edit the contents within the Knowledge Management system ==

#Click the "Edit" page tab at the top right of the page.
#Make changes to the text.
#Click the "Save page" button.

=== Editing rules, editing conventions, and formatting===

The number one rule of editing is to be bold. Go ahead - make changes. Other people can correct any mistakes you make, so have confidence, and give it a try! There are all kinds of editing conventions, rules, and philosophies for the editing of + pages, but the be bold rule is the most important of these!

An edit can contribute whole new paragraphs or pages of information, or it can be as simple as fixing a typo or a spelling mistake. In general, try to add or edit text so that it is clear and concise. Most importantly, make sure you are always aiming to do something which improves the contents of the Knowledge Management system.

When you need to use some type of formatting, such as for new headings or bolding of text, you do this using wiki markup syntax.

See Help:Formatting for some of the common types of formatting used.

=== Edit summary ===

Before you save a change, you can enter a short note (must be shorter than 500 characters) in the "Summary (?):" box describing your changes. Don't worry too much about this, or spend too much time thinking about it: just put in a short description of what you just changed. For example, you might say "fixed typo" or "added more information about sunflowers".

This summary gets stored alongside your edit, and allows people to track changes in the Knowledge Management system more effectively.

===Preview===

It's a good idea to use the "Show preview" button to see what your change will look like, before you save it. This is also related to tracking changes because every time you save, this is displayed to others as a separate change. This isn't something to worry about too much, but it's good to get into the habit of eliminating mistakes in your own work, by using a preview before saving, rather than saving, then having to do another edit just to make one or more minor corrections.

===Show changes===

Another option is the "Show changes" button which allows you to see the differences between the current version and the edited version.

===Protected pages===

Pages that are protected cannot be edited by anyone except users of a specific group. Protected pages will instead display "View source" instead of edit. In that case, to edit a protected page, contact a user who has permission to edit the page.

===Other types of editing===

With Knowledge Management system edits you can start a new page, move (or rename) a page, or even delete a page:

*'''[[Help:Starting a new page]]
*'''[[Help:Moving a page]]
*'''[[Help:Sysop deleting and undeleting]]

Remember you should always aim to improve the overall contents of the Knowledge Management system with your edits.

Need help

2018-08-30T06:18:23Z

Ufo:

= Need help? =

== It's very easy to edit the contents within the Knowledge Management system ==

#Click the "Edit" page tab at the top right of the page. 
#Make changes to the text. 
#Click the "Save page" button. 

=== Editing rules, editing conventions, and formatting===

The number one rule of editing is to be bold. Go ahead - make changes. Other people can correct any mistakes you make, so have confidence, and give it a try! There are all kinds of editing conventions, rules, and philosophies for the editing of + pages, but the be bold rule is the most important of these!

An edit can contribute whole new paragraphs or pages of information, or it can be as simple as fixing a typo or a spelling mistake. In general, try to add or edit text so that it is clear and concise. Most importantly, make sure you are always aiming to do something which improves the contents of the Knowledge Management system.

When you need to use some type of formatting, such as for new headings or bolding of text, you do this using wiki markup syntax.

See Help:Formatting for some of the common types of formatting used.

=== Edit summary ===

Before you save a change, you can enter a short note (must be shorter than 500 characters) in the "Summary (?):" box describing your changes. Don't worry too much about this, or spend too much time thinking about it: just put in a short description of what you just changed. For example, you might say "fixed typo" or "added more information about sunflowers".

This summary gets stored alongside your edit, and allows people to track changes in the Knowledge Management system more effectively.

===Preview===

It's a good idea to use the "Show preview" button to see what your change will look like, before you save it. This is also related to tracking changes because every time you save, this is displayed to others as a separate change. This isn't something to worry about too much, but it's good to get into the habit of eliminating mistakes in your own work, by using a preview before saving, rather than saving, then having to do another edit just to make one or more minor corrections.

===Show changes===

Another option is the "Show changes" button which allows you to see the differences between the current version and the edited version.

===Protected pages===

Pages that are protected cannot be edited by anyone except users of a specific group. Protected pages will instead display "View source" instead of edit. In that case, to edit a protected page, contact a user who has permission to edit the page.

===Other types of editing===

With Knowledge Management system edits you can start a new page, move (or rename) a page, or even delete a page:

*'''[[Help:Starting a new page]]
*'''[[Help:Moving a page]]
*'''[[Help:Sysop deleting and undeleting]]

Remember you should always aim to improve the overall contents of the E+ with your edits.

User:Ufo

2018-07-24T10:20:13Z

Ufo: Created page with "My personal profile page."

My personal profile page.

Strategy (Strategic Objective)

2018-07-05T12:32:43Z

Terms of use

2018-05-15T12:51:04Z

Ufo:

== '''General Information''' ==

This Web site contains proprietary notices and copyright information, the terms of which must be observed and followed. Please see our Copyright section for related information.

LEADing Practice grants you a non-exclusive, non-transferable, limited permission to access and display the Web pages within this site as a customer or potential customer of LEADing Practice provided you comply with these Terms of Use, and all copyright, trademark, and other proprietary notices remain intact. The use authorized under this agreement is non-commercial in nature (e.g., you may not sell the content you access on or through this Web site). All other use of this site is prohibited.

Except for the limited permission in the preceding paragraph, LEADing Practice does not grant you any express or implied rights or licenses under any patents, trademarks, copyrights, or other proprietary or intellectual property rights. You may not mirror any of the content from this site on another Web site or in any other media. Any standards, software and other materials that are made available for downloading, access, or other use from this site with their own license terms will be governed by such terms, conditions, and notices. Your failure to comply with such terms or any of the terms on this site will result in automatic termination of any rights granted to you, without prior notice, and you must immediately destroy all copies of downloaded materials in your possession, custody or control.

=== '''Website content and Copyright''' ===

LEADing Practice does not grant any licenses to any copyrights, patents or any other intellectual property rights. This Website is the property of LEADing Practice and is protected by Laws of Denmark, U.S. and international copyright law and conventions. LEADing Practice grants to User the right to access and use the Website, so long as such use is for internal information purposes, and User does not alter, copy, disseminate, redistribute or republish any content or feature of this Website. User acknowledges that access to and use of this Website is subject to these TERMS OF USE and any expanded access or use must be approved in writing by LEADing Practice.

=== '''Enterprise Standards example content and Copyright on Website''' ===

On the webpage you are granted access to example content of Enterprise Standards, Industry Standards and Leading Practice. YOU AGREE NOT TO REPRODUCE, MODIFY, COPY, AGGREGATE, DISTRIBUTE, TRANSMIT, DISPLAY, PUBLISH, LICENSE, TRANSFER OR CREATE DERIVATIVE WORKS OR SELL ANY INFORMATION YOU AGAIN ACCESS TO THROUGH LEADING PRACTICE. PLEASE REVIEW OUR ENTIRE INTELLECTUAL PROPERTY (IP) NOTICE BEFORE PROCEEDING. IF YOU DO NOT AGREE WITH THESE TERMS, YOU MUST EXIT THIS WEBSITE IMMEDIATELY.

=== '''Disclaimer of Warranties''' ===

LEADing Practice does not make any warranties, express or implied, including, without limitation, those of merchantability and fitness for a particular purpose, with respect to this Website. Although LEADing Practice takes reasonable steps to screen this Website for infection by viruses, worms, Trojan horses or other code manifesting contaminating or destructive properties, LEADing Practice cannot guarantee that it will be free of infection or that it will be available at any particular time or location.

=== '''Accuracy of Information''' ===

The LEADing Practice assumes no responsibility regarding the accuracy of the information that is provided by LEADing Practice and use of such information is at the recipient’s own risk. LEADing Practice provides no assurances that any reported problems may be resolved with the use of any information that LEADing Practice provides. By furnishing information, LEADing Practice does not grant any licenses to any copyrights, patents or any other intellectual property rights.

While the information contained on this Website has been obtained from sources believed to be reliable, LEADing Practice disclaims all warranties as to the accuracy, completeness or adequacy of such information. User assumes sole responsibility for the use it makes of this Website to achieve his/her intended results.

=== '''Third Party Links''' ===

This Website may contain links to other third party websites, which are provided as additional resources for the convenience of Users. LEADing Practice does not endorse, sponsor or accept any responsibility for these third party websites, User agrees to direct any concerns relating to these third party websites to the relevant website administrator.

LEADing Practice makes no representations whatsoever about any other web site, which you may access through this one. When you access a third-party web site, even one that may contain the LEADing Practice logo, please understand that it is independent from LEADing Practice and that LEADing Practice has no control over the content on that web site.

In addition, a link to a third-party web site does not mean that LEADing Practice endorses or accepts any responsibility for the content, or the use, of such web site. It is up to you to take precautions to ensure that whatever you select for your use is free of such items as viruses, worms, trojan horses and other items of a destructive nature.

=== '''Third Party Rights''' ===

The terms hereunder regarding Disclaimer of Warranty, Limitation of Liability and Indemnification are for the benefit of LEADing Practice , and its licensors, employees and agents, each of whom shall have the right to assert and enforce those terms against a User. LEADing Practice links to independent, third-party information considered relevant and valuable to our audience. The views and opinions expressed there do not necessarily reflect the views of LEADing Practice, its members or its sponsors.

=== '''Limitation of Liability''' ===

In no event will LEADing Practice be liable to any party for any direct, indirect, special or other consequential damages for any use of this website, newsletter or email services or on any other hyper linked website, including, without limitation, any lost profits, business interruption, loss of programs or otherwise, even if we are expressly advised of the possibility of such damages. All information is provided by the LEADing Practice on an “as is” basis only. LEADing Practice provides no representations and warranties express or implied, including the implied warranties of fitness for particular purpose, merchantability and non-infringement.

=== '''Privacy Statement''' ===

User’s right to privacy is of vital importance to LEADing Practice. When you register to use our Website, LEADing Practice will ask you to provide your name, organization, email address, and other related information. LEADing Practice will use this information to provide you with a more personalized online experience and, where applicable, to process orders, as well as to keep track of what topics are of interest to our Users. LEADing Practice will not share this information with any third party.

LEADing Practice does not want to receive confidential or proprietary information from you through our website. Please note that any information or material sent to LEADing Practice will be deemed NOT to be confidential. By sending LEADing Practice any information or material, you grant LEADing Practice an unrestricted, irrevocable license to use, reproduce, display, perform, modify, transmit and distribute those materials or information, and you also agree that LEADing Practice is free to use any ideas, concepts, know-how or techniques that you send us for any purpose. However, we will not release your name or otherwise publicize the fact that you submitted materials or other information to us unless: (a) we obtain your permission to use your name; or (b) we first notify you that the materials or other information you submit to a particular part of this site will be published or otherwise used with your name on it; or (c) we are required to do so by law. To learn how we maintain your privacy, please review our Privacy statement.

=== '''Restriction on Use''' ===

User will not (i) violate the security of the Site nor attempt to gain unauthorized access to the Site, data, materials, information, computer systems or networks connected to any server associated with the Site, through hacking, password timing or any other means; (ii) take nor attempt any action that, in the sole discretion of LEADing Practice, imposes or may impose an unreasonable or disproportionately large burden on the Site or its infrastructure; (iii) use nor attempt to use any “scraper,” “robot,” “bot,” “spider,” “data mining,” “computer code,” or any other automated device, program, tool, algorithm, process or methodology to access, acquire, copy, or monitor any portion of the Site, any data or content found on or accessed through the Site without the prior written consent of LEADing Practice; (iv) forge headers or otherwise manipulate identifiers in order to disguise the origin of any other content.

== '''Overview''' ==

The following are the terms of an agreement between you and LEADing Practice. By accessing, or using this Web site, you acknowledge that you have read, understand, and agree to be bound by these terms and to comply with all applicable laws and regulations, including export and re-export control laws and regulations. If you do not agree to these terms, please do not use this Web site.

LEADing Practice may, without notice to you, at any time, revise these Terms of Use and any other information contained in this Web site. LEADing Practice may also make improvements or changes in the standards, software, services, or programs described in this site at any time without notice.

=== '''Changes or Updates to the Web site''' ===

LEADing Practice reserves the right to change, update or discontinue any aspect of this Website at any time without notice. Your continued use of the Website after any such change constitutes your agreement to these TERMS OF USE, as modified. LEADing Practice may at any time revise these terms by updating this posting. By using this web site, you agree to be bound by any such revisions and should therefore periodically visit this page to determine the then current terms to which you are bound.

=== '''Termination''' ===

In accessing and using this Website, User agrees to comply with all applicable laws and agrees not to take any action that would compromise the security or viability of this Website. LEADing Practice may terminate User’s access to this Website at any time for any reason. The terms hereunder regarding Disclaimer of Warranty, Accuracy of Information, Indemnification, and Third Party Rights shall survive termination.

=== '''Indemnification''' ===

User agrees to indemnify, defend and hold harmless LEADing Practice, its affiliates, licensors, and their respective officers, directors, employees and agents from and against all losses, expenses, damages and costs, including reasonable attorneys’ fees, arising out of User’s use/misuse of this Website.

=== '''General Provisions''' ===

Any provision in any written communication received by LEADing Practice in connection with this Website, which is inconsistent with, or adds to, these TERMS OF USE is void. If any term hereunder is determined by a court of competent jurisdiction to be invalid, all remaining terms will remain in full force and effect.

=== '''Governing Law''' ===

These TERMS OF USE and the resolution of any dispute arising hereunder shall all be governed and construed in accordance with the laws of Denmark, without regard to its conflicts of law principles. User consents to the jurisdiction of the laws of Denmark.

Terms of use

2018-05-15T12:48:23Z

Ufo:

= TESTING MARKUP CONVERSION =
The following are the terms of an agreement between you and LEADing Practice. By accessing, or using this Web site, you acknowledge that you have read, understand, and agree to be bound by these terms and to comply with all applicable laws and regulations, including export and re-export control laws and regulations. If you do not agree to these terms, please do not use this Web site. LEADing Practice may, without notice to you, at any time, revise these Terms of Use and any other information contained in this Web site. LEADing Practice may also make improvements or changes in the standards, software, services, or programs described in this site at any time without notice. '''''Important note:''''' Unauthorized use, disclosure, appropriation, reproduction or misuse of “'''LEADing Practice Material'''” (LPM) and/or “'''LEADing Practice Service'''” (LPS) in any form whatsoever, whether in absence of contract or outside the use permitted by contract, may result in invoicing issued to You and/or to the relevant person(s) based on the applicable LEADING Practice Standard Fees at the time of such unauthorized use or misuse, in addition to any other such fees, rights and remedies as may be available to LEADING Practice. You fully acknowledge and agree that such Invoicing as per this Policy and any such additional remedy shall be deemed by You to be appropriate and reasonable in the circumstances. You also acknowledge and agree that You have read and understood the [http://leadingpractice.com/terms-of-use/ Terms of Use], [http://leadingpractice.com/privacy-policy/ Privacy Policy] and [http://leadingpractice.com/copyright-policy/ Copyright Policy].

== '''General Information''' ==

This Web site contains proprietary notices and copyright information, the terms of which must be observed and followed. Please see our Copyright section for related information.

LEADing Practice grants you a non-exclusive, non-transferable, limited permission to access and display the Web pages within this site as a customer or potential customer of LEADing Practice provided you comply with these Terms of Use, and all copyright, trademark, and other proprietary notices remain intact. The use authorized under this agreement is non-commercial in nature (e.g., you may not sell the content you access on or through this Web site). All other use of this site is prohibited.

Except for the limited permission in the preceding paragraph, LEADing Practice does not grant you any express or implied rights or licenses under any patents, trademarks, copyrights, or other proprietary or intellectual property rights. You may not mirror any of the content from this site on another Web site or in any other media. Any standards, software and other materials that are made available for downloading, access, or other use from this site with their own license terms will be governed by such terms, conditions, and notices. Your failure to comply with such terms or any of the terms on this site will result in automatic termination of any rights granted to you, without prior notice, and you must immediately destroy all copies of downloaded materials in your possession, custody or control.

=== '''Website content and Copyright''' ===

LEADing Practice does not grant any licenses to any copyrights, patents or any other intellectual property rights. This Website is the property of LEADing Practice and is protected by Laws of Denmark, U.S. and international copyright law and conventions. LEADing Practice grants to User the right to access and use the Website, so long as such use is for internal information purposes, and User does not alter, copy, disseminate, redistribute or republish any content or feature of this Website. User acknowledges that access to and use of this Website is subject to these TERMS OF USE and any expanded access or use must be approved in writing by LEADing Practice.

=== '''Enterprise Standards example content and Copyright on Website''' ===

On the webpage you are granted access to example content of Enterprise Standards, Industry Standards and Leading Practice. YOU AGREE NOT TO REPRODUCE, MODIFY, COPY, AGGREGATE, DISTRIBUTE, TRANSMIT, DISPLAY, PUBLISH, LICENSE, TRANSFER OR CREATE DERIVATIVE WORKS OR SELL ANY INFORMATION YOU AGAIN ACCESS TO THROUGH LEADING PRACTICE. PLEASE REVIEW OUR ENTIRE INTELLECTUAL PROPERTY (IP) NOTICE BEFORE PROCEEDING. IF YOU DO NOT AGREE WITH THESE TERMS, YOU MUST EXIT THIS WEBSITE IMMEDIATELY.

=== '''Disclaimer of Warranties''' ===

LEADing Practice does not make any warranties, express or implied, including, without limitation, those of merchantability and fitness for a particular purpose, with respect to this Website. Although LEADing Practice takes reasonable steps to screen this Website for infection by viruses, worms, Trojan horses or other code manifesting contaminating or destructive properties, LEADing Practice cannot guarantee that it will be free of infection or that it will be available at any particular time or location.

=== '''Accuracy of Information''' ===

The LEADing Practice assumes no responsibility regarding the accuracy of the information that is provided by LEADing Practice and use of such information is at the recipient’s own risk. LEADing Practice provides no assurances that any reported problems may be resolved with the use of any information that LEADing Practice provides. By furnishing information, LEADing Practice does not grant any licenses to any copyrights, patents or any other intellectual property rights.

While the information contained on this Website has been obtained from sources believed to be reliable, LEADing Practice disclaims all warranties as to the accuracy, completeness or adequacy of such information. User assumes sole responsibility for the use it makes of this Website to achieve his/her intended results.

=== '''Third Party Links''' ===

This Website may contain links to other third party websites, which are provided as additional resources for the convenience of Users. LEADing Practice does not endorse, sponsor or accept any responsibility for these third party websites, User agrees to direct any concerns relating to these third party websites to the relevant website administrator.

LEADing Practice makes no representations whatsoever about any other web site, which you may access through this one. When you access a third-party web site, even one that may contain the LEADing Practice logo, please understand that it is independent from LEADing Practice and that LEADing Practice has no control over the content on that web site.

In addition, a link to a third-party web site does not mean that LEADing Practice endorses or accepts any responsibility for the content, or the use, of such web site. It is up to you to take precautions to ensure that whatever you select for your use is free of such items as viruses, worms, trojan horses and other items of a destructive nature.

=== '''Third Party Rights''' ===

The terms hereunder regarding Disclaimer of Warranty, Limitation of Liability and Indemnification are for the benefit of LEADing Practice , and its licensors, employees and agents, each of whom shall have the right to assert and enforce those terms against a User. LEADing Practice links to independent, third-party information considered relevant and valuable to our audience. The views and opinions expressed there do not necessarily reflect the views of LEADing Practice, its members or its sponsors.

=== '''Limitation of Liability''' ===

In no event will LEADing Practice be liable to any party for any direct, indirect, special or other consequential damages for any use of this website, newsletter or email services or on any other hyper linked website, including, without limitation, any lost profits, business interruption, loss of programs or otherwise, even if we are expressly advised of the possibility of such damages. All information is provided by the LEADing Practice on an “as is” basis only. LEADing Practice provides no representations and warranties express or implied, including the implied warranties of fitness for particular purpose, merchantability and non-infringement.

=== '''Privacy Statement''' ===

User’s right to privacy is of vital importance to LEADing Practice. When you register to use our Website, LEADing Practice will ask you to provide your name, organization, email address, and other related information. LEADing Practice will use this information to provide you with a more personalized online experience and, where applicable, to process orders, as well as to keep track of what topics are of interest to our Users. LEADing Practice will not share this information with any third party.

LEADing Practice does not want to receive confidential or proprietary information from you through our website. Please note that any information or material sent to LEADing Practice will be deemed NOT to be confidential. By sending LEADing Practice any information or material, you grant LEADing Practice an unrestricted, irrevocable license to use, reproduce, display, perform, modify, transmit and distribute those materials or information, and you also agree that LEADing Practice is free to use any ideas, concepts, know-how or techniques that you send us for any purpose. However, we will not release your name or otherwise publicize the fact that you submitted materials or other information to us unless: (a) we obtain your permission to use your name; or (b) we first notify you that the materials or other information you submit to a particular part of this site will be published or otherwise used with your name on it; or (c) we are required to do so by law. To learn how we maintain your privacy, please review our Privacy statement.

=== '''Restriction on Use''' ===

User will not (i) violate the security of the Site nor attempt to gain unauthorized access to the Site, data, materials, information, computer systems or networks connected to any server associated with the Site, through hacking, password timing or any other means; (ii) take nor attempt any action that, in the sole discretion of LEADing Practice, imposes or may impose an unreasonable or disproportionately large burden on the Site or its infrastructure; (iii) use nor attempt to use any “scraper,” “robot,” “bot,” “spider,” “data mining,” “computer code,” or any other automated device, program, tool, algorithm, process or methodology to access, acquire, copy, or monitor any portion of the Site, any data or content found on or accessed through the Site without the prior written consent of LEADing Practice; (iv) forge headers or otherwise manipulate identifiers in order to disguise the origin of any other content.

== '''Overview''' ==

The following are the terms of an agreement between you and LEADing Practice. By accessing, or using this Web site, you acknowledge that you have read, understand, and agree to be bound by these terms and to comply with all applicable laws and regulations, including export and re-export control laws and regulations. If you do not agree to these terms, please do not use this Web site.

LEADing Practice may, without notice to you, at any time, revise these Terms of Use and any other information contained in this Web site. LEADing Practice may also make improvements or changes in the standards, software, services, or programs described in this site at any time without notice.

=== '''Changes or Updates to the Web site''' ===

LEADing Practice reserves the right to change, update or discontinue any aspect of this Website at any time without notice. Your continued use of the Website after any such change constitutes your agreement to these TERMS OF USE, as modified. LEADing Practice may at any time revise these terms by updating this posting. By using this web site, you agree to be bound by any such revisions and should therefore periodically visit this page to determine the then current terms to which you are bound.

=== '''Termination''' ===

In accessing and using this Website, User agrees to comply with all applicable laws and agrees not to take any action that would compromise the security or viability of this Website. LEADing Practice may terminate User’s access to this Website at any time for any reason. The terms hereunder regarding Disclaimer of Warranty, Accuracy of Information, Indemnification, and Third Party Rights shall survive termination.

=== '''Indemnification''' ===

User agrees to indemnify, defend and hold harmless LEADing Practice, its affiliates, licensors, and their respective officers, directors, employees and agents from and against all losses, expenses, damages and costs, including reasonable attorneys’ fees, arising out of User’s use/misuse of this Website.

=== '''General Provisions''' ===

Any provision in any written communication received by LEADing Practice in connection with this Website, which is inconsistent with, or adds to, these TERMS OF USE is void. If any term hereunder is determined by a court of competent jurisdiction to be invalid, all remaining terms will remain in full force and effect.

=== '''Governing Law''' ===

These TERMS OF USE and the resolution of any dispute arising hereunder shall all be governed and construed in accordance with the laws of Denmark, without regard to its conflicts of law principles. User consents to the jurisdiction of the laws of Denmark.

Industry:Oil & Gas

2017-12-01T07:03:31Z

Ufo:

{{DISPLAYTITLE: Oil & Gas User Group & Industry Standards}}
The Oil & Gas User Group provides a global platform for executives, experts, academics, thought-leaders and researchers and industry peers to share Oil & Gas leading and best practices and lessons learned, conduct research and explore new ideas to continuously improve Oil & Gas Industry Standard assets and artefacts that are applied in specific and ongoing projects.

In our Oil & Gas User Group, we work energetically to create industry standards that provide our members with maximum value to accelerating impact initiatives such as integrated and standardized solutions, business model innovation, cost-cutting, performance measurements, single point of truth as well as operating model improvements.

The Oil & Gas User Group & Industry Standard Committee consist of:

Working Group

Defines and tailors Oil & Gas Industry Standards, provides guidance supporting the standards, develops additional support documentation, provides implementation guidance and defines procedures for continuous improvement and governance.

Advisory Board

Provides guidance and advice to the members of the working group.

Academia

Provides prototyping, research and validation support.

Depending on the initiative, the following examples provide a strong combination of Oil & Gas industry standards and accelerators that has proven very useful:

{|class="wikitable" style="width:100%" |
|class="thead" style="background-color:rgb(195, 217, 255);width: 50%;text-align:left;padding-left:1%;padding-top:1%;" |
'''Standard/Artefact'''
|class="thead" style="background-color:rgb(195, 217, 255);width: 25%;text-align:left;padding-left:1%;padding-top:1%;" |
'''Reference Content'''
|class="thead" style="background-color:rgb(195, 217, 255);width: 25%;text-align:left;padding-left:1%;padding-top:1%;" |
'''ID #'''
|-
|[[Media:LEAD-Oil-Gas-Industry-Standard-LEAD-IS50001-Upstream-Competency-Assessment.pdf|Oil & Gas Competency Map]]
|Competency Reference Content
|LEAD-ES20013BC
|-
|[[Media:LEAD-Business-Model-Reference-Content-BML1-Oil-Gas-Corporate-01.png|Oil & Gas Business Model (Upstream Value Chain View)]]
|Business Model Reference Content
|LEAD-ES20004BC
|-
|[[Media:LEAD-Business-Model-Reference-Content-BML2-Oil-Gas-Upstream-Petroleum-01.png|Oil & Gas Business Model (Upstream Accountability View)]]
|Business Model Reference Content
|LEAD-ES20004BC
|-
|[[Media:LEAD-Business-Model-Reference-Content-BML3-Oil-Gas-Exploration-01.png|Oil & Gas Operating Model (Example Exploration)]]
|Operating Model Reference Content
|LEAD-ES20010BC
|-
|[[Media:Oil-Gas-Upstream-Operating-Model-overview.png|Oil & Gas Operating Model (Example Upstream)]]
|Operating Model Reference Content
|LEAD-ES20010BC
|-
|Top Strategic Business Objectives (SBO's) of Oil & Gas
|Value Reference Content
|LEAD-ES10003PG
|-
|[[Media:Oil-Gas-Strategy-Map-Finance-example.jpg|Oil & Gas Strategy Map & Model (Example Financial)]]
|Value Reference Content
|LEAD-ES10003PG
|-
|Major Critical Success Factors (CSF's) of Oil & Gas
|Value Reference Content
|LEAD-ES10003PG
|-
|[[Media:Define-your-Financial-Operating-Model-based-on-Value-Drivers.png|Oil & Gas Value Drivers (Example Define Operations)]]
|Value Reference Content
|LEAD-ES10003PG
|-
|[[Media:Define-your-Financial-Operating-Model-based-on-Cost-Drivers.png|Major Oil & Gas Cost Drivers (Example Define Operations)]]
|Performance Reference Content
|LEAD-ES10004PG
|-
|Key Performance Indicators (KPI's) of Oil & Gas
|Measurement Reference Content
|LEAD-ES20014PG
|-
|[[Media:Oil-Order-Entry-As-Is-BPMN-Diagram.pdf|Example of Oil & Gas Oil Order Entry - As Is BPMN Diagram]]
|Business Process Reference Content
|LEAD-IS50001
|-
|[[Media:Oil-Order-Entry-What-If-BPMN-Diagram.pdf|Example of Oil & Gas Oil Order Entry - What if BPMN Diagram]]
|Business Process Reference Content
|LEAD-IS50001
|-
|Oil & Gas Process Map
|Business Process Reference Content
|LEAD-ES20005BP
|-
|Oil & Gas Process Model (BPM Notations)
|Business Process Reference Content
|LEAD-ES20005BP
|-
|Oil & Gas Service Matrix
|Service Model Reference Content
|LEAD-ES20008BCBS
|-
|Oil & Gas Service Architecture Flow
|Service-Oriented Architecture Reference Content
|LEAD-ES40005BS
|-
|Oil & Gas Information Flow Architecture
|Information Reference Content
|LEAD-ES50015BCIDSA
|-
|Oil & Gas Maturity Model
|Maturity Reference Content
|LEAD-ES60003AL
|-
|[[Media:Example-of-Upstream-Duplication-Identify-Transformation-Potential.png|Identify Transformation Potential (Example Upstream)]]
|Alignment & Unity Reference Content
|LEAD-ES60001AL
|-
|[[Media:Business-Architecture-Process-Modelling-example.pdf|Oil & Gas Business Architecture]]
|Business Architecture Reference Content
|LEAD-ES40002PGBCPSI
|-
|[[Media:LEAD-Oil-Gas-Industry-Standard-LEAD-IS50001-ERP-Upstream-Assessment.pdf|ERP Upstream Assessment]]
|ERP Reference Content
|LEAD-ES50013SADIBC
|-
|}

[[Category:Energy Sector]]

Industry:Oil & Gas

2017-10-04T06:48:48Z

Ufo:

{{DISPLAYTITLE: Oil & Gas User Group & Industry Standards}}
The Oil & Gas User Group provides a global platform for executives, experts, academics, thought-leaders and researchers and industry peers to share Oil & Gas leading and best practices and lessons learned, conduct research and explore new ideas to continuously improve Oil & Gas Industry Standard assets and artefacts that are applied in specific and ongoing projects.

In our Oil & Gas User Group, we work energetically to create industry standards that provide our members with maximum value to accelerating impact initiatives such as integrated and standardized solutions, business model innovation, cost-cutting, performance measurements, single point of truth as well as operating model improvements.

The Oil & Gas User Group & Industry Standard Committee consist of:

Working Group

Defines and tailors Oil & Gas Industry Standards, provides guidance supporting the standards, develops additional support documentation, provides implementation guidance and defines procedures for continuous improvement and governance.

Advisory Board

Provides guidance and advice to the members of the working group.

Academia

Provides prototyping, research and validation support.

Depending on the initiative, the following examples provide a strong combination of Oil & Gas industry standards and accelerators that has proven very useful:

{|class="wikitable" style="width:100%" |
|class="thead" style="background-color:rgb(195, 217, 255);width: 50%;text-align:left;padding-left:1%;padding-top:1%;" |
'''Standard/Artefact'''
|class="thead" style="background-color:rgb(195, 217, 255);width: 25%;text-align:left;padding-left:1%;padding-top:1%;" |
'''Reference Content'''
|class="thead" style="background-color:rgb(195, 217, 255);width: 25%;text-align:left;padding-left:1%;padding-top:1%;" |
'''ID #'''
|-
|[[Media:LEAD-Oil-Gas-Industry-Standard-LEAD-IS50001-Upstream-Competency-Assessment.pdf|Oil & Gas Competency Map]]
|Competency Reference Content
|LEAD-ES20013BC
|-
|[[Media:LEAD-Business-Model-Reference-Content-BML1-Oil-Gas-Corporate-01.png|Oil & Gas Business Model (Upstream Value Chain View)]]
|Business Model Reference Content
|LEAD-ES20004BC
|-
|[[Media:LEAD-Business-Model-Reference-Content-BML2-Oil-Gas-Upstream-Petroleum-01.png|Oil & Gas Business Model (Upstream Accountability View)]]
|Business Model Reference Content
|LEAD-ES20004BC
|-
|[[Media:LEAD-Business-Model-Reference-Content-BML3-Oil-Gas-Exploration-01.png|Oil & Gas Operating Model (Example Exploration)]]
|Operating Model Reference Content
|LEAD-ES20010BC
|-
|[[Media:Oil-Gas-Upstream-Operating-Model-overview.png|Oil & Gas Operating Model (Example Upstream)]]
|Operating Model Reference Content
|LEAD-ES20010BC
|-
|[[#|Top Strategic Business Objectives (SBO's) of Oil & Gas]]
|Value Reference Content
|LEAD-ES10003PG
|-
|[[Media:Oil-Gas-Strategy-Map-Finance-example.jpg|Oil & Gas Strategy Map & Model (Example Financial)]]
|Value Reference Content
|LEAD-ES10003PG
|-
|[[#|Major Critical Success Factors (CSF's) of Oil & Gas]]
|Value Reference Content
|LEAD-ES10003PG
|-
|[[Media:Define-your-Financial-Operating-Model-based-on-Value-Drivers.png|Oil & Gas Value Drivers (Example Define Operations)]]
|Value Reference Content
|LEAD-ES10003PG
|-
|[[Media:Define-your-Financial-Operating-Model-based-on-Cost-Drivers.png|Major Oil & Gas Cost Drivers (Example Define Operations)]]
|Performance Reference Content
|LEAD-ES10004PG
|-
|[[#|Key Performance Indicators (KPI's) of Oil & Gas]]
|Measurement Reference Content
|LEAD-ES20014PG
|-
|[[Media:Oil-Order-Entry-As-Is-BPMN-Diagram.pdf|Example of Oil & Gas Oil Order Entry - As Is BPMN Diagram]]
|Business Process Reference Content
|LEAD-IS50001
|-
|[[Media:Oil-Order-Entry-What-If-BPMN-Diagram.pdf|Example of Oil & Gas Oil Order Entry - What if BPMN Diagram]]
|Business Process Reference Content
|LEAD-IS50001
|-
|[[#|Oil & Gas Process Map]]
|Business Process Reference Content
|LEAD-ES20005BP
|-
|[[#|Oil & Gas Process Model (BPM Notations)]]
|Business Process Reference Content
|LEAD-ES20005BP
|-
|[[#|Oil & Gas Service Matrix]]
|Service Model Reference Content
|LEAD-ES20008BCBS
|-
|[[#|Oil & Gas Service Architecture Flow]]
|Service-Oriented Architecture Reference Content
|LEAD-ES40005BS
|-
|[[#|Oil & Gas Information Flow Architecture]]
|Information Reference Content
|LEAD-ES50015BCIDSA
|-
|[[#|Oil & Gas Maturity Model]]
|Maturity Reference Content
|LEAD-ES60003AL
|-
|[[Media:Example-of-Upstream-Duplication-Identify-Transformation-Potential.png|Identify Transformation Potential (Example Upstream)]]
|Alignment & Unity Reference Content
|LEAD-ES60001AL
|-
|[[Media:Business-Architecture-Process-Modelling-example.pdf|Oil & Gas Business Architecture]]
|Business Architecture Reference Content
|LEAD-ES40002PGBCPSI
|-
|[[Media:LEAD-Oil-Gas-Industry-Standard-LEAD-IS50001-ERP-Upstream-Assessment.pdf|ERP Upstream Assessment]]
|ERP Reference Content
|LEAD-ES50013SADIBC
|-
|}

[[Category:Energy Sector]]

Maps:Strategy Map

2017-10-02T10:00:41Z

Ufo:

{{DISPLAYTITLE: Strategy Map}}
=== Introduction ===

Strategy is a complex subject that interlinks with multiple components within the organization. In order to better capture and document all of the objects, Strategy is built as a map. The Strategy Map is an accurate list and representation of decomposed and/or composed objects. A map is often represented in the form of a simple list or a chart laid out in columns in either a document or a spreadsheet. It’s appearance ranges from that of a single list of one object or that of multiple objects across multiple rows within one or more (specific) columns.

The purpose of constructing an Strategy Map is to build an inventory or indexed list of objects that are to be either decomposed or composed for later usage within the business layer, information layer and/or technology layer of an enterprise. It is a powerful yet simple to use tool that allows the practitioner to document large amounts of information in a structured and coherent way.

=== Strategy Map Description ===

The Strategy Map provides you with a detailed overview of identified strategies (each identified with a unique name and ID number), value indicators (CSFs), strategic business objectives (SBOs), objectives, organizational units, organizational areas and/or groups, service areas and groups as well as process areas and groups.

=== How to use the Strategy Map ===

Identify and capture the strategies, value indicators, strategic business objectives, objectives, organizational units, organizational areas and groups, service areas and groups as well as process areas and groups.

'''For example:'''
#A strategy may have multiple yet specific associations with value indicators, strategic business objectives, objectives, organizational units, organizational areas and groups, service areas and groups as well as process areas and groups.
#Multiple strategies may have an association to any single specific value indicators, strategic business objectives, objectives, organizational units, organizational areas and groups, service areas and groups as well as process areas and groups.

{{#lead: MapsTables}}

[[Category:Maps]]

Maps:Strategy Map

2017-10-02T10:00:04Z

Ufo: