<h2>Guidealines</h2>
CLiki links are case-insensitive. "CLiki" will point to the same node as "cliki". However, node names are case-sensitive, and may show up in searches among topics, etc. So keep your node names uniform to the elements of the same category. For example, _(term) nodes should be capitalized, as well as _(topic)s.

Also, the use of topic indicators should be minimized. For example, acronyms are generally not glossary terms unless they are in common usage in a generic sense. Some general advice:
<ul>
  <li>Pages for persons should have the * (person) topic in them. If the person is a contributor of the _(TUNES project) you should also put the * (contributor) topic.</li>
  <li>An entry in the _(Operating systems review| Operating Systems) section must have the _(topic) * (OS) in it</li>
  <li>An entry in the _(Glossary) section should have the _(topic) * (term) in it.</li>
  <li>An acronym should have the _(topic) * (acronym) in it.
  <li>Look at the other sections, and cross-reference when it's useful and possible.
</ul>

Style-sheet support to keep in mind:
<ul>
  <li>If you put code examples, include them in <code>CODE</code> tags.
  <li>If you put a list (<tt>UL</tt> (Unordered List) or <tt>OL</tt> (Ordered List)) of off-text links to external sites at the bottom of your new entry, put <span class="links">class="links"</span>.
    <br>In case such links are about implementations, put <span class="implementations">class="implementations"</span>.
  <li>Use a tag, tipically <tt>SPAN</tt>, with attribute <tt>class="comment"</tt> if you want your remarks to <span class="comment">stand separately from the main document</span> and be noticed as such.
</ul>

<h2>Markup</h2>
Most of the weird and wonderful markup syntax of the original Wiki is omitted, as HTML markup is allowed.  This is easily abusable: I'd rather receive patches to fix it than I would see the problem demonstrated.

We have our own special markup too, of course: this consists of a funny character followed by an argument in parens.  To avoid quoting nightmares, on this page I have inserted an extra space between the character and the open-paren.  Don't type it for real.

<dl>
  <dt>Internal links:</dt>
  <dd><nobr>_ (Foo)</nobr> renders as _(Foo). <nobr>_ (Ex Em Ell|XML)</nobr> renders as _(Ex Em Ell|XML). Cliki page titles aren't case-sensitive, and spaces and underscores are treated equivalently, but Cliki will remember the way the title was written when you first created the page, and format it that way forevermore.  So, please make some effort to use capitals where appropriate.  In keeping with the precedent set by _(Ward's Wiki), links to pages that don't exist are displayed less obtrusively than links to pages that do.</dd>
  
  <dt>External links:</dt>
  <dd><nobr>_ (Foo | http://www.google.com/)</nobr> renders as _(Foo | http://www.google.com/).  <nobr>_ (http://www.google.com/)</nobr> renders as _(http://www.google.com/). <nobr>_ ("Alias|Wavefront"|http://www.aliaswavefront.com/)</nobr> renders as _("Alias|Wavefront"|http://www.aliaswavefront.com/) and <nobr>_ (Alias\|Wavefront|http://www.aliaswavefront.com/)</nobr> renders as _(Alias\|Wavefront|http://www.aliaswavefront.com/). So <nobr>_ (anchor | URL)</nobr> provides a convenient wiki-style external link.</dd>
  
  <dt>Topic markers:</dt>
  <dd><nobr>* (Foo)</nobr> declares this page to be relevant to topic Foo.  This means that (a) it will have Foo listed in the footer, (b) it will be listed on pages which include a topic search for Foo.  Usually there will be a page called Foo that contains such a search.</dd>
  
  <dt>_(CLHS) references:</dt>
  <dd><nobr># H(FOO)</nobr>, where FOO is a standard CL symbol, will expand into a link to the appropriate Hyperspec page.  Thanks to Eric Marsden for the code that does this.  It presently goes to the Xanalys site, because the _(ALU) site was down when I tried it.</dd>
  
  <dt>Searches:</dt>
  <dd><nobr>/ ("Lisp" :attribute :title :match :substring :case-sensitive nil)</nobr> renders as
  /("Lisp" :attribute :title :match :substring :case-sensitive nil)
  <br>  :attribute is (or :title :topic :body), :match is (or :exact :substring), :case-sensitive is (or nil t).  The search code is still in development: title searches work, topics work only for exact matches (and ignore the setting of <tt>case-sensitive</tt>), body text doesn't at all.
  <br>At some later date, searches will be optionally able to display also the first sentence or first paragraph of the page found. _(CLiki Style) encourages the use of inverted pyramid style.</dd>
</dl>

As a convenience, text is assumed to start a new paragraph -- will be rendered preceded by a P tag -- if preceded by a blank line and not starting with a left-angle bracket. This seems to work passably well unless you want to start a paragraph with marked-up text.  You'll just have to add the P tag yourself in that case.

<a name="SGML bug"></a><h2>SGML entities bug</h2>
Don't expect to be able to type SGML entities (e.g. ampersand-l-t-semicolon), and have them work, as they tend to be translated into the actual characters they represent (e.g. less-than sign).  This is listed on the _(CLiki bugs|http://www.cliki.net/CLiki%20Bugs) page, but is unlikely to get fixed any time soon. In any case if you mantain and edit a local version of a node and then copy the result this is a minor annoyance. See also _(HTML special characters and symbols)
