/[svn]/doc/docbase/writing_docs/01_writing_docs.html
ViewVC logotype

Diff of /doc/docbase/writing_docs/01_writing_docs.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 2733 by schoenebeck, Sun Apr 26 23:49:16 2015 UTC revision 2741 by schoenebeck, Wed Apr 29 00:14:30 2015 UTC
# Line 3  Line 3 
3      <meta name="author" content="Christian Schoenebeck">      <meta name="author" content="Christian Schoenebeck">
4      <title>Writing Docs</title>      <title>Writing Docs</title>
5      <meta name="description" content="Writing new articles for this site.">      <meta name="description" content="Writing new articles for this site.">
6        <link rel="stylesheet" href="http://doc.linuxsampler.org/css/preview.css">
7        <script type="text/javascript" src="http://doc.linuxsampler.org/js/preview.js"></script>
8    </head>    </head>
9    <body>    <body>
10      <p>      <p>
# Line 122  Line 124 
124        Creating a new article for this site is as simple as creating a new text        Creating a new article for this site is as simple as creating a new text
125        file and adding following text:        file and adding following text:
126      </p>      </p>
127      <code l="html">      <code lang="html">
128  <h1>My First Article</h1>  <h1>My First Article</h1>
129  <p>  <p>
130    This is the first paragraph.    This is the first paragraph.
# Line 289  Line 291 
291        which will be shown at the left side next to your article on our site.        which will be shown at the left side next to your article on our site.
292      </p>      </p>
293      <p>      <p>
294        Once your article is uploaded to our site, IDs for the individual        Once your article is
295          <a href="02_uploading_docs.html">uploaded to our site</a>, IDs for the individual
296        headlines will automatically be generated for you. If for example you had        headlines will automatically be generated for you. If for example you had
297        somewhere in your article a headline called "Conclusion of Topic", then        somewhere in your article a headline called "Conclusion of Topic", then
298        this particular paragraph of your article may be directly linked to from        this particular paragraph of your article may be directly linked to from
299        other articles or other sites with an URL like        other articles or other sites with an URL like
300        <code>http://doc.linuxsampler.org/path/to/your/article/#conclusion_of_topic</code>.        <code lang="none">http://doc.linuxsampler.org/path/to/your/article/#conclusion_of_topic</code>.
301        If you want to override this behavior, because you rather want to use your        If you want to override this behavior, because you rather want to use your
302        own ID for a paragraph of your article, then simply set the desired ID with        own ID for a paragraph of your article, then simply set the desired ID with
303        your headline:        your headline:
304      </p>      </p>
305      <code>      <code lang="html">
306  <h3 id="my_conclusion">Conclusion of topic</h3>  <h3 id="my_conclusion">Conclusion of topic</h3>
307      </code>      </code>
308            
# Line 441  Line 444 
444            
445      <h3>Unique Pictures</h3>      <h3>Unique Pictures</h3>
446      <p>      <p>
447        Once your article and its picture(s) are uploaded to our server, our        Once your article and its picture(s) are
448          <a href="02_uploading_docs.html">uploaded to our server</a>, our
449        system will automatically check that all images on our entire site have        system will automatically check that all images on our entire site have
450        unique and unambiguous file names, no matter at which directory they        unique and unambiguous file names, no matter at which directory they
451        are stored to exactly. The "file name" that is checked in this case, is        are stored to exactly. The "file name" that is checked in this case, is
# Line 567  end on Line 571  end on
571        do that: simply put the code block into the paragraph text block of your        do that: simply put the code block into the paragraph text block of your
572        HTML file:        HTML file:
573      </p>      </p>
574      <code>      <code lang="html">
575  <p>  <p>
576    A variable is assigned with NKSP like this &lt;code&gt;$foo := 5&lt;/code&gt;, in this    A variable is assigned with NKSP like this &lt;code&gt;$foo := 5&lt;/code&gt;, in this
577    case you are assigning &lt;code&gt;5&lt;/code&gt; to the integer variable &lt;code&gt;$foo&lt;/code&gt;.    case you are assigning &lt;code&gt;5&lt;/code&gt; to the integer variable &lt;code&gt;$foo&lt;/code&gt;.
# Line 588  end on Line 592  end on
592    
593      <note>      <note>
594        Syntax highlighting of source code is automatically generated by our site's software        Syntax highlighting of source code is automatically generated by our site's software
595        once the document is uploaded to our server. So when you are just        once the document is
596          <a href="02_uploading_docs.html">uploaded to our server</a>.
597          So when you are just
598        previewing your article with source code snippets on your local machine,        previewing your article with source code snippets on your local machine,
599        then those source code snippets will yet be displayed monochrome,        then those source code snippets will yet be displayed monochrome,
600        without any syntax highlighting.        without any syntax highlighting.
# Line 596  end on Line 602  end on
602            
603      <h3>Metaphors</h3>      <h3>Metaphors</h3>
604      <p>      <p>
605        You might have noticed, we have used a special kind of <code>??place-holder??</code> for        You might have noticed, we have used a special kind of <code lang="html">??place-holder??</code> for
606        human-readable portions in source code before, which shall outline to the reader        human-readable portions in source code before, which shall outline to the reader
607        that it is not actually "real" source code, but just reflecting its semantic meaning.        that it is not actually "real" source code, but just reflecting its semantic meaning.
608        Simply put the respective pseudo-code into a pair of two question marks,        Simply put the respective pseudo-code into a pair of two question marks,
609        like so:        like so:
610      </p>      </p>
611      <code>      <code lang="html">
612  &lt;code&gt;  &lt;code&gt;
613  on init  on init
614    declare const $i = \?\?some-value\?\?    declare const $i = \?\?some-value\?\?
# Line 635  end on Line 641  end on
641        If you want to add links in your article to another article or to some        If you want to add links in your article to another article or to some
642        other website, then you just use an ordinary HTML link tag pair:        other website, then you just use an ordinary HTML link tag pair:
643      </p>      </p>
644      <code>      <code lang="html">
645  <p>  <p>
646    This paragraph contains &lt;a href="../nksp.html"&gt;a link to another article&lt;/a&gt;    This paragraph contains &lt;a href="../nksp.html"&gt;a link to another article&lt;/a&gt;
647    and to &lt;a href="http://www.linuxsampler.org"&gt;another website&lt;/a&gt;.    and to &lt;a href="http://www.linuxsampler.org"&gt;another website&lt;/a&gt;.
# Line 665  end on Line 671  end on
671        An article file on our site usually has the following        An article file on our site usually has the following
672        file name form:        file name form:
673      </p>      </p>
674      <code>      <code lang="none">
675  ??number-prefix??_??unique-name??.html  ??number-prefix??_??unique-name??.html
676      </code>      </code>
677      <p>      <p>
# Line 688  end on Line 694  end on
694        Technical terms and abbreviations are often used in articles to reduce        Technical terms and abbreviations are often used in articles to reduce
695        the amount of text for transmitting some kind of information about a        the amount of text for transmitting some kind of information about a
696        certain topic to the reader. You might want to emphasize technical terms and abbreviations        certain topic to the reader. You might want to emphasize technical terms and abbreviations
697        in your article, by wrapping the term into a pair of <code><i></code> HTML        in your article, by wrapping the term into a pair of <code lang="html"><i></code> HTML
698        tags. On our site this will not only show the term in a special unified        tags. On our site this will not only show the term in a special unified
699        font style (currently italic), but it allows you also to define the        font style (currently italic), but it allows you also to define the
700        meaning of the term <b>once</b>. Which goes like this:        meaning of the term <b>once</b>. Which goes like this:
# Line 698  end on Line 704  end on
704       <p>       <p>
705        You may define a new term like this:        You may define a new term like this:
706      </p>      </p>
707      <code>      <code lang="html">
708  <p>  <p>
709    He left the bar and jumped right into his    He left the bar and jumped right into his
710    &lt;i title="A very large vehicle."&gt;Mega Liner&lt;/i&gt;    &lt;i title="A very large vehicle."&gt;Mega Liner&lt;/i&gt;
# Line 722  end on Line 728  end on
728        Obviously you don't want to define        Obviously you don't want to define
729        the same term over and over again, just to provide the user the meaning of        the same term over and over again, just to provide the user the meaning of
730        it at any occurence of the site. That's why our software does that        it at any occurence of the site. That's why our software does that
731        automatically for you once your article is uploaded to our server. Now        automatically for you once your article is
732        when you use the term at another place, i.e. in another article, then        <a href="02_uploading_docs.html">uploaded to our server</a>.
733          Now when you use the term at another place, i.e. in another article, then
734        it will automatically have the same meaning attached to it:        it will automatically have the same meaning attached to it:
735      </p>      </p>
736      <code>      <code>
# Line 763  end on Line 770  end on
770        Tables are written like ordinary HTML tables. That is:        Tables are written like ordinary HTML tables. That is:
771      </p>      </p>
772      <code>      <code>
773  <table>  &lt;table&gt;
774    <tr>    &lt;tr&gt;
775      <th>Name</th> <th>Description</th>      &lt;th&gt;Name&lt;/th&gt; &lt;th&gt;Description&lt;/th&gt;
776    </tr>    &lt;/tr&gt;
777    <tr>    &lt;tr&gt;
778      <td>Foo</td> <td>Some text.</td>      &lt;td&gt;Foo&lt;/td&gt; &lt;td&gt;Some text.&lt;/td&gt;
779    </tr>    &lt;/tr&gt;
780    <tr>    &lt;tr&gt;
781      <td>Bar</td> <td>And more text.</td>      &lt;td&gt;Bar&lt;/td&gt; &lt;td&gt;And more text.&lt;/td&gt;
782    </tr>    &lt;/tr&gt;
783    <tr>    &lt;tr&gt;
784      <td>Thing</td> <td>And that's it.</td>      &lt;td&gt;Thing&lt;/td&gt; &lt;td&gt;And that's it.&lt;/td&gt;
785    </tr>    &lt;/tr&gt;
786  </table>  &lt;/table&gt;
787      </code>      </code>
788      <example>      <example>
789        <table>        <table>
# Line 871  end on Line 878  end on
878        manage articles of our documentation site on your own.        manage articles of our documentation site on your own.
879      </p>      </p>
880      <p>      <p>
881          You already got a Subversion account? Then continue reading
882          <a href="02_uploading_docs.html">how to upload articles</a> for this site.
883        </p>
884        <p>
885        Thanks for your support!        Thanks for your support!
886      </p>      </p>
887            

Legend:
Removed from v.2733  
changed lines
  Added in v.2741

  ViewVC Help
Powered by ViewVC