-
Notifications
You must be signed in to change notification settings - Fork 0
08 Block quotes, lists and alerts
Markdown can produce its own numbered and unnumbered lists, these can be mixed and nested as required. These lists are quite basic and don’t look very good (lists within the PracticalSeries Wikis use tables to give better structure and formatting, see section 10 for details).
Block quotes and alerts are used to highlight particular text.
Block quotations are areas of text that are highlighted to make them distinct from the normal body text, they look like this:
This is an extract from “Race to the Moon”: Cox, Catherine Bly & Charles Murray (1989). Published by Simon and Schuster. There is a Kindle version by the same authors, but it is just called Apollo.
Block quotations are so called because they often contain quotes or references to other works. In practice, block quotations can be used for any purpose.
GitHub displays block quotations with a 4 px wide grey bar on the left-hand side of the text area. The text is indented by 4.5 spaces and is in a grey colour: #59636E
or rgb(89,99,110)
that is lighter than the body text colour. Block quotation text is the same point size as body text.
Block quotations are created in Markdown by starting the line with a single greater than sign >
followed by a space:
Markdown, HTML equivalence and GitHub output | ||
---|---|---|
|
|
|
> First line
>
> Second line
|
<blockquote>
<p>First line</p>
<p>Second line</p>
</blockquote>
|
|
Table 8.1 — Block quotes |
A blank line with a leading greater than >
can be used to separate paragraphs in a block quotation.
Block quotes can be nested by adding extra >
at the start of the text:
Markdown, HTML equivalence and GitHub output | ||
---|---|---|
|
|
|
> First level
>
>> Second level
>>
>>> Third level
>>>
>>>> Fourth level
>>>
>>> Third level
>>
>> Second level
>
> First level
|
<blockquote>
<p>First level</p>
<blockquote>
<p>Second level</p>
<blockquote>
<p>Third level</p>
<blockquote>
<p>Fourth level</p>
</blockquote>
<p>Third level</p>
</blockquote>
<p>Second level</p>
</blockquote>
<p>first level</p>
</blockquote>
|
|
Table 8.2 — Nested block quotes |
Block quotes can contain other Markdown elements such as headings, emphasis (bold, italic, underline &c.), they can also contain lists (GitHub supports lists in block quotes). The lists can be ordered or unordered (see section 8.3 and section 8.2). The following shows some examples:
Markdown, HTML equivalence and GitHub output | ||
---|---|---|
|
|
|
> # Block Quotes
>
> With lists
>
> * List point 1
> * List point 2
>
> *Last **line***
|
<blockquote>
<h1> Block Quotes </h1>
<p> With lists</p>
<ul>
<li> List point 1</li>
<li> List point 2</li>
</ul>
<p><em>Last <strong>line</strong></em></p>
</blockquote>
|
|
Table 8.3 — Markdown elements in block code |
❶ | Always leave a blank line before and after block quotes |
❷ | Separate paragraphs with a `>` on a blank line |
❸ | Block quotes can be nested without limit |
❹ | Block quotes are the same point size as body text |
List 8.1 — Markdown rules for block quotes |
---|
Unordered or unnumbered lists are the simplest form of list, they appear as indented lines with a point (•) at the start of the line:
- First point
- Second point
- Third point
Unordered lists are created in Markdown by starting the line with a single asterisk *
followed by a space, a single dash -
followed by a space or a single plus +
followed by a space.
The following all work:
Markdown, HTML equivalence and GitHub output | ||
---|---|---|
|
|
|
* First point
* Second point
* Third point Or - First point
- Second point
- Third point Or + First point
+ Second point
+ Third point
|
<ul>
<li>First point</li>
<li>Second point</li>
<li>Third point</li>
</ul>
|
|
Table 8.4 — Unordered list |
Tip
Don’t mix and match the delimiters *
, +
, or -
; if you do, GitHub will interpret it as the start of a new list and will change the line spacing, pick one and stick to it throughout the list.
Whichever delimiter you use, it must be the first character on the line (spaces in front of it will be ignored), any non-space character that precedes it will cause the line to render as normal text.
It is possible to nest unordered lists:
- Level 1 point 1
- Level 1 point 2
- Level 2 point 1
- Level 2 point 2
- Level 3 point 1
- Level 1 point 3
- Level 1 point 4
Unordered lists are nested by indenting each list by at least two spaces (four is more conventional) before the delimiter for each additional level. The above is generated as follows:
Markdown, HTML equivalence and GitHub output | ||
---|---|---|
|
|
|
* Level 1 point 1
* Level 1 point 2
* Level 2 point 1
* Level 2 point 2
* Level 3 point 1
* Level 1 point 3
* Level 1 point 4
|
<ul>
<li>Level 1 point 1</li>
<li>Level 1 point 2</li>
<ul>
<li>Level 2 point 1</li>
<li>Level 2 point 2</li>
<ul>
<li>Level 3 point 1</li>
</ul>
</ul>
<li>Level 1 point 3</li>
<li>Level 1 point 4</li>
</ul>
|
|
Table 8.5 — Nested unordered list |
Nesting uses different bullet marks for the first three levels: black circle:
- Level 1
- Level 2
- Level 3
- Level 4
- Level 5
- Level 4
- Level 3
- Level 2
Unordered lists can be indented as far as you like.
The type of bullet point used is fixed in Markdown: a black circle for the first level, open circle for the second and black square for all other layers.
HTML allows the type of bullet point to be selected (within limits) with the use of the type attribute. The type
attribute can specify a disk
, a circle
, a square
, or none
.
HTML and GitHub output | |
---|---|
|
|
<ul type = "disk">
<li>First point</li>
<li>Second point</li>
<li>Third point</li>
</ul>
|
|
<ul type = "circle">
<li>First point</li>
<li>Second point</li>
<li>Third point</li>
</ul>
|
|
<ul type = "square">
<li>First point</li>
<li>Second point</li>
<li>Third point</li>
</ul>
|
|
<ul type = "none">
<li>First point</li>
<li>Second point</li>
<li>Third point</li>
</ul>
|
|
Table 8.6 — HTML bullet types |
In terms of spacing, the point mark (•) is indented three spaces from the left edge of the text area, the text following the point mark is indented a further two spaces.
If the line of text following the point wraps at the end of a line, the text will maintain the correct indentation as follows:
- Point 1
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. In consectetur tortor a tortor ornare, non pretium diam faucibus. Morbi ut mollis dolor, nec pretium tellus. Suspendisse ornare neque placerat orci aliquam, eu sodales dui blandit. Maecenas nec risus vel magna blandit euismod. Suspendisse id finibus purus. Nam ultricies non sapien ac rutrum.
- Point 3
Here the second point wraps at the end of the line, but maintains the correct indentation.
Each nested level indents the list by a further seven spaces before the bullet point, the text following the bullet point is always indented two spaces.
A slightly misleading heading.
If you start an unordered list with a number let’s say:
Markdown and GitHub output | |
---|---|
|
|
* 2004, Markdown invented
* 2008, GitHub adds Wiki support
|
|
Table 8.7 — Numbers at the start of an unordered list |
Then everything is fine, the list displays as you would expect: bullet point followed by the text.
If however, the number was followed by a full stop:
Markdown and GitHub output | |
---|---|
|
|
* 2004. Markdown invented
* 2008. GitHub adds Wiki support
|
|
Table 8.8 — Numbers with a full stop at the start of an unordered list |
It converts the list to an ordered list (numbers followed by a full stop are interpreted as an ordered list, see section 8.3) and displays the number in roman numerals (again see section 8.3 for details). This is GitHub trying to make sense of the conflicting information we have supplied it.
It’s the full stop after the number that cause the problem, GitHub thinks were trying to create an ordered list starting at 2004, it displays it as roman numerals because it is preceded by an asterisk (see section 8.3.3 for details).
To make the list display properly, we need to escape the full stop (see Table 7.1) by putting a backslash in front of it:
Markdown and GitHub output | |
---|---|
|
|
* 2004\. Markdown invented
* 2008\. GitHub adds Wiki support
|
|
Table 8.9 — Numbers with an escaped full stop at the start of an unordered list |
It is possible to add an additional paragraph to an unordered list by indenting it by at least two spaces:
Markdown, HTML equivalence and GitHub output | ||
---|---|---|
|
|
|
* First point
Additional paragraph
* Second point
* Third point
|
<ul>
<li>First point</li>
<p>Additional paragraph</p>
<li>Second point</li>
<li>Third point</li>
</ul>
|
|
Table 8.10 — Unordered list with an additional paragraph |
The additional paragraph must have a blank line before and after.
Unordered lists can contain other Markdown elements such as headings, emphasis (bold, italic, underline &c.) and block quotes. The following shows some examples:
Markdown, HTML equivalence and GitHub output | ||
---|---|---|
|
|
|
* ### First point
> Block quote
* *Second point*
* Third point
|
<ul>
<li><h3>First point</h3></li>
<blockquote>
Block quote
</blockquote>
<li><em>Second point</em></li>
<li>Third point</li>
</ul>
|
|
Table 8.11 — Unordered list with additional elements |
❶ |
Always use the same delimiter in an unordered list, don’t mix the * , - or + in the same list. |
❷ |
If starting with a number followed by a full stop, escape the full stop by using \.
|
❸ | Nest lists by indenting the levels by at least two additional spaces before the delimiter |
List 8.2 — Markdown rules for unordered lists |
---|
Ordered or numbered lists are lists that are automatically numbered when rendered by GitHub. They consist of a number followed by a full stop. The number increments for each new line in the list:
- Point 1
- Point 2
- Point 3
Ordered lists are created in Markdown by entering a number followed by a full stop 1.
and a space.
Only the first number (top line of the list) matters, this will be the starting number of the list.
The following all work:
Markdown, HTML equivalence and GitHub output | ||
---|---|---|
|
|
|
1. First point
2. Second point
3. Third point
Or 1. First point
1. Second point
1. Third point
Or 1. First point
4. Second point
6. Third point Or 1. First point
10. Second point
3. Third point
|
<ol>
<li>First point</li>
<li>Second point</li>
<li>Third point</li>
</ol>
|
|
Table 8.12 — Ordered list |
In the above table, all the Markdown options produce the same result (a list numbered 1
, 2
and 3
), this is because the first number in each list is the number 1
. The numbers for each subsequent point in a list are calculated automatically by GitHub when it renders the page, the actual numbers in the Markdown text are ignored.
Whichever number you use, it must be the first character on the line (spaces in front of it will be ignored), any non-space character that precedes it will cause the line to render as normal text.
Markdown, HTML equivalence and GitHub output | ||
---|---|---|
|
|
|
7. First point
8. Second point
9. Third point
Or 7. First point
1. Second point
1. Third point
Or 7. First point
4. Second point
6. Third point Or 7. First point
10. Second point
3. Third point
|
<ol start="7">
<li>First point</li>
<li>Second point</li>
<li>Third point</li>
</ol>
|
|
Table 8.13 — Ordered list starting at a specific number |
Note
It is not possible to skip numbers in an ordered list.
It is possible to nest ordered lists:
- Level 1 point 1
- Level 1 point 2
*. Level 2 point 1
- Level 2 point 2
- Level 3 point 1
- Level 2 point 2
- Level 1 point 3 1 Level 1 point 4
Ordered lists are nested by indenting each list by four spaces before the number for each additional level. The above is generated as follows:
Markdown, HTML equivalence and GitHub output | ||
---|---|---|
|
|
|
1. Level 1 point 1
1. Level 1 point 2
1.. Level 2 point 1
1. Level 2 point 2
1. Level 3 point 1
1. Level 1 point 3
1 Level 1 point 4
|
<ol>
<li>Level 1 point 1</li>
<li>Level 1 point 2</li>
<ol>
<li>Level 2 point 1</li>
<li>Level 2 point 2</li>
<ol>
<li>Level 3 point 1</li>
</ol>
</ol>
<li>Level 1 point 3</li>
<li>Level 1 point 4</li>
</ol>
|
|
Table 8.14 — Nested ordered list |
Nesting uses different numbering mechanisms for the first three levels: Arabic numerals (1, 2, 3…), lower case Roaman numerals (i, ii, iii…) and lowercase letters (a, b, c…). All subsequent nesting levels use the lowercase letters.
- Level 1
- Level 2
- Level 3
- Level 4
- Level 5
- Level 4
- Level 3
- Level 2
Ordered lists can be indented as far as you like.
The type of numbering used in ordered lists is fixed in Markdown: Arabic numerals (1, 2, 3…), lower case Roaman numerals (i, ii, iii…) and lowercase letters (a, b, c…) for all other layers.
HTML allows the type of numbering to be selected (within limits) with the use of the type
attribute. The type attribute can specify Arabic numerals type = "1"
, lowercase alphabetically ordered type = "a"
, uppercase alphabetically ordered type = "A"
, lowercase Roman numerals type = "i"
or uppercase Roman numerals type = "I"
.
HTML and GitHub output | |
---|---|
|
|
<ol type = "1">
<li>First point</li>
<li>Second point</li>
<li>Third point</li>
</ol>
|
|
<ol type = "a">
<li>First point</li>
<li>Second point</li>
<li>Third point</li>
</ol>
|
|
<ol type = "A">
<li>First point</li>
<li>Second point</li>
<li>Third point</li>
</ol>
|
|
<ol type = "i">
<li>First point</li>
<li>Second point</li>
<li>Third point</li>
</ol>
|
|
<ol type = "I">
<li>First point</li>
<li>Second point</li>
<li>Third point</li>
</ol>
|
|
Table 8.15 — HTML ordered list numeral types |
Tip
There is no none
option for the type attribute when used with ordered lists (unlike the unordered list, see section 8.2.2).
In terms of spacing, the number mark is indented two normal spaces and a thin space (see section 7.2) from the left edge of the text area💠1, the text following the point mark is indented a further single space.
With nested levels, the text of each nested level is indented a further seven normal spaces.
If the line of text following the point wraps at the end of a line, the text will maintain the correct indentation as follows:
- Point 1
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. In consectetur tortor a tortor ornare, non pretium diam faucibus. Morbi ut mollis dolor, nec pretium tellus. Suspendisse ornare neque placerat orci aliquam, eu sodales dui blandit. Maecenas nec risus vel magna blandit euismod. Suspendisse id finibus purus. Nam ultricies non sapien ac rutrum.
- Point 3
Here the second point wraps at the end of the line, but maintains the correct indentation.
The full stop following the number is always in the same position from the left-hand edge of the screen.
As more digits are added (going from point 9 to point 10 or from point 99 to point 100 &c.) the left indentation becomes less. This can be seen in the following lists:
![]() |
Figure 8.1 — Ordered list indentations |
---|
In the above diagram the blue dashes show the position of the full stop following the number (these always line up), the black squares start at the left edge of the page (where the body text starts), the orange line shows the left edge of the body text area.
It can be seen that one and two-digit numbers are indented from the left-hand side of the text area, three-digit numbers start at exactly the edge of the text area and any number with more than three digit expands beyond the left edge of the text area (into the margin area).
It is possible to add an additional paragraph to an ordered list by indenting it four spaces:
Markdown, HTML equivalence and GitHub output | ||
---|---|---|
|
|
|
1. First point
Additional paragraph
1. Second point
1. Third point
|
<ol>
<li>First point</li>
<p>Additional paragraph</p>
<li>Second point</li>
<li>Third point</li>
</ol>
|
|
Table 8.16 — Ordered list with an additional paragraph |
The additional paragraph must have a blank line before and after.
Ordered lists can contain other Markdown elements such as headings, emphasis (bold, italic, underline &c.) and block quotes. The following shows some examples:
Markdown, HTML equivalence and GitHub output | ||
---|---|---|
|
|
|
1. ### First point
> Block quote
1. *Second point*
1. Third point
|
<ol>
<li><h3>First point</h3></li>
<blockquote>
Block quote
</blockquote>
<li><em>Second point</em></li>
<li>Third point</li>
</ol>
|
|
Table 8.17 — Ordered list with additional elements |
❶ | The first number on the first line of a list is the starting number for the list |
❷ | Nest lists by indenting the levels by four spaces before the number |
❸ | Lists are always Arabic numerals (1, 2, 3…), nested lists use lowercase Roman numerals (i, ii, iii…) followed by lowercase letters for all other nesting levels (a, b, c…). |
List 8.2 — Markdown rules for unordered lists |
---|
It is possible to nest together ordered and unordered lists. This usually involves having an unordered list within an ordered list:
Markdown, HTML equivalence and GitHub output | ||
---|---|---|
|
|
|
1. General Points
* Max page length
* Comments
* Keyboard shortcuts
1. Wiki structures
* Folder structures
* Conventions
1. Managing a Wiki
* Revision control
* Managing commits
|
<ol>
<li>General Points</li>
<ul>
<li>Max page length</li>
<li>Keyboard shortcuts</li>
</ul>
<li>Wiki structures</li>
<ul>
<li>Folder structures</li>
<li>Conventions</li>
</ul>
<li>Managing a Wiki</li>
<ul>
<li>Revision control</li>
<li>Managing commits</li>
</ul>
</ol>
|
|
Table 8.18 — Ordered list with nested unordered lists |
They can also be the other way round (unordered list with nested ordered list):
Markdown, HTML equivalence and GitHub output | ||
---|---|---|
|
|
|
* General Points
1. Max page length
1. Comments
1. Keyboard shortcuts
* Wiki structures
1. Folder structures
1. Conventions
* Managing a Wiki
1. Revision control
1. Managing commits
|
<ul>
<li> General Points </li>
<ol>
<li>Max page length</li>
<li>Keyboard shortcuts</li>
</ol>
<li>Wiki structures </li>
<ol>
<li>Folder structures</li>
<li>Conventions</li>
</ol>
<li>Managing a Wiki</li>
<ol>
<li>Revision control</li>
<li>Managing commits</li>
</ol>
</ul>
|
|
Table 8.19 — Unordered list with nested ordered lists |
Note
In both cases, the nested list start with the numerical arrangement or point style for that level of indentation (circles for the unordered list in the first example, Roman numerals for the ordered list in the second example).
Task lists are a special form of list with checkboxes:
- General Points
- Wiki structures
- Managing a Wik
Task lists are created in Markdown by starting the line with a single dash -
followed by a space, followed by an open bracket [
followed by a space followed by a close bracket ]
followed by a space: - [ ]
.
If the checkbox is to be shown ticked, put an x
between the brackets (the x
can be lower or uppercase).
The above image is generated with the following Markdown:
Markdown and GitHub output | |
---|---|
|
|
- [ ] General Points
- [x] Wiki structures
- [X] Managing a Wik
|
|
Table 8.20 — Task list Markdown |
Note
There is no HTML equivalent for task lists..
It is possible to nest task lists:
- General Points
- Max page length
- Comments
- Keyboard shortcuts
- Wiki structures
- Sidebars and Footnotes
- Folder structures
- Conventions
- PracticalSeries
- Standard
- Managing a Wiki
- Revision control
- Managing commits
Task lists are nested by indenting each list by four spaces before the delimiter for each additional level. The above is generated as follows:
Markdown and GitHub output | |
---|---|
|
|
- [ ] General Points
- [ ] Max page length
- [x] Comments
- [x] Keyboard shortcuts
- [ ] Wiki structures
- [ ] Sidebars and Footnotes
- [x] Folder structures
- [ ] Conventions
- [ ] PracticalSeries
- [x] Standard
- [x] Managing a Wiki
- [x] Revision control
- [x] Managing commits
|
|
Table 8.21 — Nested task lists |
Task lists can be indented as far as you like.
Alerts are similar to block quotes (see section 8.1) and are used to highlight specific information. GitHub supports five different types of alert:
Note
Sidenotes and footnotes for reference
Tip
Advice or guidance for doing something
Important
Essential information
Warning
Information for avoiding problems
Caution
Potential risks associated with specific actions
Alerts show a different coloured icon for each type and a similarly coloured 4 px wide bar at the left-hand edge of the text.
There is no HTML equivalent for alerts.
The Markdown for the above is:
Markdown and GitHub output |
---|
|
> [!NOTE]
> Sidenotes and footnotes for reference
> [!TIP]
> Advice or guidance for doing something
> [!IMPORTANT]
> Essential information
> [!WARNING]
> Information for avoiding problems
> [!CAUTION]
> Potential risks associated with specific actions
|
Table 8.22 — Alert Markdown |
Note
Alerts cannot be used inside any form of HTML tag <p>
, <table>
&c.
The Markdown is fairly self-explanatory and is very similar to block quotes.
Alerts begin with a greater than sign followed by a space, an open bracket and an exclamation mark > [!
.
It then has one of five words (in either upper or lowercase, it doesn’t matter): NOTE
, TIP
, IMPORTANT
, WARNIN
G or CAUTION
(any other word will render the line as a block quote). This is followed by a closing bracket ]
. There must be no further text on this line.
Subsequent lines in the alert begin with a greater than sign followed by a space >
. If a blank line is needed in the alert, simply start it with a greater than sign >
and leave the rest of the line blank.
Alerts use the following colours:
Alert | Colour |
---|---|
rgb(009, 105, 218) or #0969DA
|
|
rgb(026, 127, 055) or #1A7F37
|
|
rgb(130, 080, 223) or #8250DF
|
|
rgb(154, 103, 000) or #9A6700
|
|
rgb(207, 034, 046) or #CF222E
|
|
Table 8.23 — Alert colours |
Note
Alerts cannot be nested.
❶ | Always leave a blank line before and after alerts |
❷ |
Alerts always have a header line: [!type] , where type is: NOTE , TIP , IMPORTANT , WARNING or CAUTION
|
❸ |
Each line of text in an alert starts with > followed by a space |
❹ |
Separate paragraphs with a > on a blank line |
❺ | Alerts cannot be nested |
❻ | Alerts are the same point size as body text |
List 8.6 — Markdown rules for alerts |
---|
Footnotes:
Note
💠1 For the unordered list, the bullet point was indented three spaces, the thin space instead of the last space in the ordered list allows for the additional full stop character (leaving the actual text for the list indented to the same point as for an unordered list, everything lines up).↩
|
|
|
|
|
The PracticalSeries of Publications — Copyright © 2025 Michael Gledhill
⬆️ Top | [email protected] | PracticalSeries of Publications | Main repository
|
|
|
|
|
Licence
The licences and other details
The Licence
Why did I choose the MIT Licence?
Permissive licences
Copyleft licence
Limiting liabilities
Which licence to use?
A note on spelling: licence or license
1 Introducing the GitHub Wiki
1.1 What are GitHub Wiki pages?
1.2 Understanding the Wiki pages
1.3 Creating a Wiki for a repository
1.3.1 Creating the first Wiki page
1.3.2 Creating additional pages
1.3.3 Editing a Wiki page
1.4 The Wiki is its own repository
1.4.1 Viewing a Wiki page history
1.4.2 How GitHub handles Wiki branche
1.4.3 The Wiki link to the main repository
1.5 Basic components of a Wiki page
1.5.1 Title bar and revision
1.5.2 Contents (pages) area
Listing pages in the order you want
1.5.3 Sidebars
1.5.4 Footers
1.6 Sidebars and footers
1.6.1 Creating a sidebar and footer
2 Cloning a Wiki
2.1 Why clone a Wiki?
2.2 How to clone a Wiki
2.3 Pushing local changes to GitHub
2.3.1 Configuring username and email
2.3.2 Modifying the local repository
2.3.3 Committing and synchronising
3 A Wiki folder structure
3.1 The default arrangement
3.2 Create a sidebar or footer locally
3.3 Page naming and Wiki limits
3.3.1 Supported file types
3.3.2 Page names and numbering
3.3.3 Rules for page numbering
3.3.4 Limits for Wiki pages
3.4 A Practical Wiki folder structure
3.4.1 Subfolder names for Wiki pages
3.4.2 Storing images and other data
4 Different sidebars and footers
4.1 How sidebars work
4.1.1 The PracticalSeries sidebar
4.2 How footers work
4.2.1 The PracticalSeries footer
5 Markdown, GitHub Markdown and HTML
5.1 Some useful Markdown sites
5.2 An overview of Markdown
5.3 How Markdown works
5.4 Markdown flavours
5.4.1 GitHub Flavoured Markdown (GFM)
5.5 HTML and Markdown
5.5.1 HTML with GFM
GFM blacklisted HTML tags
GFM whitelisted HTML tags
GFM HTML tags - the grey area
GFM whitelisted HTML attributes
5.5.2 PracticalSeries and Markdown
5.6 Markdown difference between files
6 Basic Markdown and text formatting
6.1 Body text and fonts
6.1.1 Body text responsive design
6.1.2 Body text in sidebars and footers
6.1.3 Rules for body text
6.1.4 Body text examples
6.1.5 Alignment of Body text
Left aligned text (default)
Right aligned text
Centred text
Justified text
6.1.6 Body text propertie
6.2 Paragraphs and line breaks
6.2.1 Forced line break
6.2.2 Blank line and a line break
6.2.3 Trailing space line break
6.2.4 Paragraph and line break rules
6.2.5 Paragraph and line break examples
6.3 Horizontal line
6.3.1 Rules for horizontal lines
6.4 Emphasis with bold
6.4.1 Rules for bold
6.4.2 Bold text examples
6.5 Emphasis with italics
6.5.1 Rules for italics
6.5.2 Italic text examples
6.6 Emphasis with bold and italics
6.6.1 Rules for bold and italics
6.6.2 Bold and italic text examples
6.7 Emphasis with underlining
6.7.1 Rules for underlining
6.7.2 Underlining text examples
6.8 Emphasis with strikethrough
6.8.1 Rules for strikethrough
6.8.2 Strikethrough text examples
6.9 Superscript and subscript
6.9.1 Rules for superscript and subscript
6.9.2 Superscript and subscript examples
6.10 Headings
Alternatives for heading 1 and 2
6.10.1 Headings Markdown rules
6.10.2 Heading properties
7 Special characters and escaping characters
7.1 Escape characters and codes
7.1.1 Markdown escape sequences
7.1.2 HTML escape sequences
7.1.3 Decimal and hexadecimal codes
Hexadecimal escape codes
7.2 Special space characters
7.2.1 Escape sequence restrictions
7.3 Emojis and emoticons
A note by the Author about emojis
7.4 Comments
8 Block quotes, lists and alerts
8.1 Block quotes
8.1.1 Nested block quotes
8.1.2 Adding other elements
8.1.3 Rules for block quotes
8.2 Unordered (unnumbered) lists
8.2.1 Nested unordered lists
8.2.2 Type of bullet point
8.2.3 Indents and spacing
8.2.4 Numbers in an unordered list
8.2.5 Adding paragraphs
8.2.6 Adding other elements
8.2.7 Rules for unordered lists
8.3 Ordered (numbered) lists
8.3.1 Starting at a different number
8.3.2 Nested ordered lists
8.3.3 Type of numbering
8.3.4 Indents and spacing
8.3.5 Adding paragraphs
8.3.6 Adding other elements
8.3.7 Rules for ordered lists
8.4 Mixing ordered and unordered lists
8.5 Task lists (check boxes)
8.5.1 Nested task lists
8.6 Alerts
8.6.1 Rules for alerts
9 Links
9.1 Link to an external web page
9.1.1 A direct link to a URL
9.1.2 A link using substitute text
9.1.3 A link using tooltips
9.2 Link to another page in the Wiki
9.2.1 Rules for linking to a Wiki page
9.3 Link to headings on current page
9.3.1 Converting a heading to a link
9.3.2 An example of a heading link
9.3.3 Heading link with tooltips
9.4 Link to headings on a different page
9.4.1 An example of a heading link
9.5 Link to a named element
A note by the Author
9.5.1 Link to a point on another page
9.6 Downloading a file
9.6.1 The download attribute
9.6.2 Spaces in filenames
9.6.3 Downloading a .md file
9.7 Reference style links
9.8 Relative links
9.8.1 Relative links from any Wiki page
10 Tables
10.1 Markdown tables
10.1.1 Horizontal alignment
10.1.2 Table construction
10.1.3 Vertical line breaks and alignment
10.1.4 Making columns wider
10.1.5 Other elements in a table
10.1.6 Markdown table restrictions
10.2 HTML tables
10.2.1 A basic HTML table
10.2.2 Aligning a table on a page
10.2.3 Text wrap and side-by-side tables
What this means in practice
The problem with the align attribute
How to stop text wrapping
10.2.4 Setting the width of a table column
10.2.5 Setting the height of a table row
10.2.6 Horizontal alignment
10.2.7 Vertical alignment
10.2.8 Spanning columns and rows
10.2.9 Table border
10.2.10 Giving a table a navigable name
10.2.11 Additional HTML tags
11 Images
11.1 Markdown images
11.1.1 Image size in Markdown
11.1.2 Making the image a link
11.1.3 Drag and drop image link
A note by the Author
11.2 HTML images
11.2.1 A basic HTML image
11.2.2 Image size in HTML
11.2.3 Horizontal alignment
11.2.4 Making the image a link
11.2.5 Using a table to contain an image
11.3 Forcing an image refresh
11.4 Using a spacer image
11.5 Mermaid diagrams
11.5.1 Inserting a Mermaid diagram
11.5.2 The rendered Mermaid diagram
11.5.3 Supported version of Mermaid
11.6 Interactive maps
11.7 3D models
12 Contents (collapsible) and footnotes
12.1 A basic table of contents
12.2 Understanding the space characters
12.3 Collapsible content
12.3.1 Defaulting to open
12.3.2 Markdown restrictions
12.4 Collapsible TOC
12.5 TOCs in tables
12.6 Footnotes
13 Code fragments
13.1 Inline code
13.2 Code blocks
13.2.1 Preferred mechanism
13.3 Syntax highlighting
13.3.1 Supported languages
13.4 HTML code fragments
13.4.1 Converting HTML to code
14 Mathematical formulae
14.1 An overview of LaTex
14.2 Inserting an inline formula
14.2.1 Alternative delimiter
14.3 A formula block
14.4 Some example formulae
14.5 LaTeX syntax
14.5.1 Greek lowercase
14.5.2 Greek uppercase and Hebrew
14.5.3 Mathematical constructions
14.5.4 Variable sized delimiters
14.5.5 Variable sized symbols
14.5.6 Variable sized symbols with limits
14.5.7 Standard functions
14.5.8 Operators and relational symbols
14.5.9 Arrows
14.5.10 Other symbols
14.5.11 Accents
14.5.12 Matrices
14.5.13 Cases
Aligning multiple equations
14.5.14 Text formatting
Font size
Font colour
The text command
Font restrictions
14.6 Abusing LaTeX
14.6.1 Changing font colour with LaTeX
15 Navigation bars, badges and buttons
15.1 Navigation bars
15.1.1 Navigation bar practicalities
15.2 Badges
15.2.1 Creating a badge
15.2.2 Static badge options
15.2.3 Dynamic badges
15.3 Buttons
16 PracticalSeries Wiki conventions
16.1 The PracticalSeries Wiki page
16.2 The PracticalSeries folder structure
16.2.1 The root folder and home page
16.2.2 Leading pages
16.2.3 .gitkeep files
16.2.4 Folder and Markdown file names
Wiki pages that start at a section
16.3 The page title area
16.4 The page heading area
16.4.1 Top of page marker
16.4.2 Logo image
16.4.3 Web ID badge
16.5 Main body area
16.5.1 Common page elements
End of page marker
End of section elements
16.5.2 Headings
Compensating for number widths
Appendices headings
16.5.3 Tables
Links to a table
A note on Markdown tables
16.5.4 Images
Images that open in a new tab
Double images
Links to a figure
16.5.5 Lists
Common points for all lists
Basic unordered list
Basic ordered list
Mixed ordered and unordered lists
Enhanced mixed lists
Index list
Reverse index list
Index list with text wrap
Reverse index list with text wrap
Indexed, mixed list
Reverse indexed, mixed list
Task list
Enhanced task list with observations
16.5.6 Code fragments
16.5.7 Formulae
Standard formulae
Alternate formulae
16.6 Sidebar
16.6.1 sidebar files and locations
16.6.2 Sidebar title and location badge
16.6.3 Navigation bar
16.6.4 Table of contents
Unnumbered, non-collapsible TOC
Unnumbered, collapsible TOC
Single digit, collapsible TOC
Double digit, collapsible TOC
TOCs for appendices
16.6.5 End of page link
16.7 Footer
16.7.1 Footer files and locations
16.7.2 Location badge
16.7.3 Navigation bar
16.7.4 Colophon
16.7.5 Links and contacts
17 Managing a Wiki
17.1 Revision control
17.1.1 Managing commits
17.2 Finding the first Wiki commit
17.3 Rebasing the Wiki
17.3.1 Summarising the rebase process
17.3.2 Executing the rebase process
17.4 Wikis and search engine visibility
Appendices
B Full list of all emoji characters
B.1 Emojis, a brief explanation
B.1.1 Emoji short names
B.1.2 Emoji escape codes
B.1.3 Emoji variations
B.1.4 Emoji numbers
B.2 Emojis characters by category
Smileys and emotion
People and body
Component
Animals and nature
Food and drink
Travel and places
Activities
Objects
Symbols
Flags
B.3 Emoji characters by Unicode
C Segoe UI full character set
A note by the Author
C.1 Inserting Unicode characters
C.2 Characters U+00000 to U+00FFF
C.3 Characters U+01000 to U+01FFF
C.4 Characters U+02000 to U+02FFF
C.5 Characters U+03000 to U+09FFF
C.6 Characters U+0A000 to U+0AFFF
C.7 Characters U+0B000 to U+0FFFF
C.8 Characters U+10000 to U+10FFF
C.9 Characters U+11000 to U+11FFF
C.10 Characters U+12000 to U+12FFF
C.11 Characters U+13000 to U+15FFF
C.12 Characters U+16000 to U+1CFFF
C.13 Characters U+1D000 to U+1EFFF
C.14 Characters U+1F000 to U+3FFFF
⬇️ End of page |