f1xska

<h1>WikiDoc Content guidelines</h1>
<div class="level1">
<ul>
<li class="level1"></li>
</ul>

<p>
Be succinct. More words take longer to read and edit. Be afraid of TLDR
</p>
<ul>
<li class="level1"></li>
</ul>

<p>
Choose keywords wisely, think of others who will need to find what you write
</p>
<ul>
<li class="level1"></li>
</ul>

<p>
Dont put more than screeful portion of information on the same page. Use “<a href="/doku.php?id=content_guideline:child_page" class="wikilink1" title="content_guideline:child_page" data-wiki-id="content_guideline:child_page">child page</a>” extensively.
</p>
<ul>
<li class="level1"></li>
</ul>

<p>
Choose page path (the portion after doku.php?id=) wisely, it is shown in “sitemap” hierachy. Use searchable keywords.
</p>
<ul>
<li class="level1"></li>
</ul>

<p>
If in doubt - ask seniors where to put this or that memo
</p>
<ul>
<li class="level1"></li>
</ul>

<p>
Delete mercilessly. We have revisions history, if needed.
</p>
<ul>
<li class="level1"></li>
</ul>

<p>
Less “How” more “Why”. “How” is volatile, can be found again, but “Why” are the real gems
</p>

</div>

Enable Complex Tables Editor Height px Turn supplementary image paste support on

Edit summary: Minor changes