tutes-dump/site-tutorials/tutorial_template.html

104 lines
4.1 KiB
HTML

<!-- SDF Tutorial Template
======================================================================
Use of this code is entirely optional. It is provided as a sample of
coding style, and a quick way to start a new tutorial for users who
may be beginners with HTML. -->
<style type="text/css">
@import url('http://sdf.org/tutorials/tutorials.css');
</style>
<!-- The title of the tutorial should be the only level-1 header
(<h1>) in the document. -->
<h1>Title of Tutorial</h1>
<!-- For longer tutorials, a table of contents is nice. Shorter
tutorials (like this one) really don't need it, so this section can be
omitted. Replace the <ul> tags with <ol> tags for a numbered list. -->
<ul>
<li>
<a href="#section-1">Section Heading</a>
<!-- to get an indented section of the list, we simply embed a
list inside of a list item -->
<ul>
<li>
<a href="#subsection-1">Subsection Heading</a>
</li>
</ul>
</li>
<li><a href="#section-2">Another Section Heading</a></li>
<li><a href="#notes">Notes</a></li>
</ul>
<!-- This is the beginning of a section. It starts with a level-2
heading (<h2>) and has been given an 'id' attribute so that it may be
linked to. -->
<h2 id="section-1">Section Heading</h2>
<!-- Remember to always contain your paragraphs in <p> tags. For
strings of code, filenames, commands, etc., which appear inside of a
paragraph, wrap them in <code> tags to differentiate them from the
rest of the paragraph's text. -->
<p>By issuing the <code>sac -nar</code> command, your spirit animal
will be changed to the narwhal.</p>
<!-- For entire blocks of code, place the <code> inside of a <pre>
instead of a <p>. Text inside of a <pre> has its whitespace characters
(space, tab, carriage-return) interpreted literally, unlike text
inside of a <p>. -->
<pre><code>10 PRINT "DO YOU EAT BOOGERS?"
20 INPUT X
30 IF X="YES" THEN PRINT "YOU'RE A GOOD MAN, CHARLIE BROWN.": END
40 IF X="NO" THEN PRINT "WHAT, YOU THINK YOU'RE BETTER THAN ME?"
</code></pre>
<!-- For sample program output, console sessions, etc., use <samp>
inside a <pre> block. -->
<pre><samp>$ finger man@arms
Login: man Name: Duncan
Directory: /eternia/heroic_warriors/man Shell: /bin/bashasaurus
No mail.
Plan: Make Orko clean-up the mess he left in my workshop.
</samp></pre>
<!-- This sub-section begins with a level-3 heading (<h3>). HTML
provides tags for sections nested six levels deep (tags <h1>
through <h6>). If you need to nest sections seven or more levels deep
...you might consider restructuring your tutorial! -->
<h3 id="subsection-1">Subsection Heading</h3>
<!-- For VERY IMPORTANT TEXT, make it <strong>. To add emphasis to a
word or phrase, use <em>. -->
<p><strong>Do not forget to flush the buffer</strong>. If you do, the
smell will be <em>intolerable</em>.</p>
<h2 id="section-2">Another Section Heading</h2>
<!-- This paragraph gives an example of two styles of footnote
referencing. Both are hyperlinked to corresponding list items (<li>)
in the Notes section below. -->
<p>The Honeywell 6080 can be induced to perform a samba by pressing
the button labeled "Samba" on the operator's
console<a href="#fn1"><sup>1</sup></a>. That mainframe's fort&eacute;,
however, is the foxtrot(<a href="#fn2">2</a>), but the inducement of
that particular step is beyond the scope of this tutorial.</p>
<!-- Here is a sample footnotes section. In this example, we're using
footnotes to cite a reference, but this same style can be used for
footnotes of any kind. Your tutorial may not require any footnotes. If
it doesn't, feel free to snip this entire section out. -->
<h2 id="notes">Notes</h2>
<!-- We're using an ordered list (<ol>) so that the notes are
automatically numbered. A single reference is cited twice in the
tutorial. As you can see, you may use an abbreviated form of citation
for subsequent references to a single work. -->
<ol>
<li id="fn1">Zurgone Vemliat, <cite>Mainframe Dancing Habits</cite> (Milwaukie: Brewers' Press, 1988), 96.</li>
<li id="fn2">Vemliat, <cite>Mainframe</cite>, 112.</li>
</ol>
<!-- At the very end, here, is the RCS Id tag. Let it be, my friend. -->
$Id: tutorial_template.html,v 1.2 2015/01/11 12:18:59 laemeur Exp $