TITLE GOES HERE

Please use only permissive licensing, such as CC-BY or CC-BY-SA. Something like the following works well:

GIMP Tutorial - TITLE (text & images) by Pat David is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Pelican makes it easy to generate a Table of Contents for your tutorial based on headings. Just include [TOC] on a line by itself where you’d like an automatic TOC list generated.

Table of Contents:

We recommend to use standard Markdown formatting for posts:

Headings¶

Headings in Markdown are denoted using two different syntaxes (setext and atx). Usually the <H1> element of a page is already being used for a title, so the tutorial should use at most H2 and below. Thus, the easiest way to denote headings is using the atx-style:

# This is an H1 (do not use it)
## This is an H2
### This is an H3
...
###### This is an H6

Try to use logical heading structure for your tutorials. This will make easier for readers to follow your content.

Paragraphs and Line Breaks¶

Paragraphs are one or more consecutive lines of text, separated by one or more blank lines. A blank line will indicate a new paragraph to begin.

If a hard <br/> (line break) is desired, simply end the line with two or more spaces.

Emphasis¶

Asterisks (*) and underscores (_) are used as indicators of emphasis. Text wrapped in on asterisk or underscore will be wrapped with an HTML <em> (aka italic) element. Double asterisks or underscores will be wrapped with an HTML <strong> (aka bold) tag:

*single asterisk*
_single underscore_
**double asterisks**
__double underscores__

Links¶

Markdown links are written in one of two ways, inline or reference. The link text is delimited using [square brackets] in both ways.

Inline links are created by:

Here's a link to [GIMP.org](https://www.gimp.org)

Reference links follow the link text with square brackets again with a label or reference for the link. Then anywhere else in the document the link label is defined with the url:

Here's a link to [GIMP.org][wgo]

...more content...

[wgo]: https://www.gimp.org

Note: another type of reference link that works with our flavor of Markdown is to forgo the ref name, and instead refer to the link text:

Here's a link to [GIMP.org][]

...more content...

[GIMP.org]: https://www.gimp.org

Images¶

The tutorial file structure tries to be self-contained. This means that you should try to keep any assets needed for the tutorial together in the same directory (this helps with portability in case the tutorial gets used somewhere else).

You can insert images using Markdown like this (but should really use the <figure> option described below):

![Alt Text](wilber-big.png)

It may make more semantic sense to encapsulate images inside of <figure> tags. This will also allow the use of a <figcaption> element to provide a caption:

<figure>
<img src="wilber-big.png" alt="Alt Text">
<figcaption>
A caption for the image.
</figcaption>
</figure>

Use this form wherever an image is to be included (which should be almost always). (Possible exception use-cases might be right/left aligned small images that don’t require a full figure+caption).

GIMP Menu Commands¶

For consistency, there is a pre-defined class for referencing menu commands in GIMP, which can be accomplished using class='GIMPCmd' on a div (or a <span> or <kbd>):

<div class='GIMPCmd'>Filters → Blur → Gaussian Blur</div>

This is used when referring to operations that require menu interactions with GIMP.

Horizontal Rule¶

A horizontal rule tag <hr/> can be inserted by simply using three or more hyphens, asterisks, or underscores on a line by themselves:

* * *
***
*********
- - -
---
_________

Be careful to not put the horizontal rule under a line with text, or it will be interpreted as a heading in setext style.

Lists¶

Ordered and unordered lists are supported.

Unordered lists use asterisks, pluses, and/or hyphens — interchangeably — as markers:

* Red
+ Green
- Blue

Ordered lists use numbers followed by periods:

1. One Fish
2. Two Fish
3. Red Fish
5. Blue Fish

Notice that the actual numbers are not used in creation of the list! The last element in our example is not a typo - it is a number “5”, not 4.

Code¶

An inline span of code uses the backtick quote (`) to offset it from surrounding text.

You can use the `printf()` function.

With the Python-Markdown extensions, you can also include an explicit declaration of the type of code for highlighting. Begin the code block with three colons followed by the language to highlight as:

\`\`\`c
printf()
\`\`\`

Blockquotes¶

Blockquotes use a familiar email-style “>” character for quoting:

> This is a blockquote with some information. If you
think this needs to be quoted, here it is. Now, here is
a nested quote inside this blockquote:
> > A nested quote inside a previous blockquote!

> Blockquotes can also have **Markdown** elements
inside them that *will* get parsed.

> ### A Header 3
For all to see.