Resources
Resources available
Markdown
This document is based on the Markdown Cheatsheet by Adam Pritchard, and is released under a CC-BY license.
Headers
# H1
## H2
### H3
#### H4
##### H5
###### H6
Alternatively, for H1 and H2, an underline-ish style:
Alt-H1
======
Alt-H2
------
Emphasis
Emphasis, aka italics, with *asterisks* or _underscores_.
Strong emphasis, aka bold, with **asterisks** or __underscores__.
Combined emphasis with **asterisks and _underscores_**.
Strikethrough uses two tildes. ~~Scratch this.~~
Emphasis, aka italics, with asterisks or underscores.
Strong emphasis, aka bold, with asterisks or underscores.
Combined emphasis with asterisks and underscores.
Strikethrough uses two tildes. Scratch this.
Lists
Todo: Replace this example with one that works on the wiki. It appears that the wiki doesn't like splitting lists.
- Testing
- Testing
- Testing
- Testing
- Testing
- Testing
- Testing
(In this example, leading and trailing spaces are shown with with dots: ⋅)
1. First ordered list item
2. Another item
⋅⋅* Unordered sub-list.
1. Actual numbers don't matter, just that it's a number
⋅⋅1. Ordered sub-list
4. And another item.
⋅⋅⋅You can have properly indented paragraphs within list items. Notice the blank line above, and the leading spaces (at least one, but we'll use three here to also align the raw Markdown).
⋅⋅⋅To have a line break without a paragraph, you will need to use two trailing spaces.⋅⋅
⋅⋅⋅Note that this line is separate, but within the same paragraph.⋅⋅
⋅⋅⋅(This is contrary to the typical GFM line break behaviour, where trailing spaces are not required.)
* Unordered list can use asterisks
- Or minuses
+ Or pluses
- First ordered list item
- Another item
- Unordered sub-list.
-
Actual numbers don't matter, just that it's a number
-
Ordered sub-list
-
And another item.
You can have properly indented paragraphs within list items. Notice the blank line above, and the leading spaces (at least one, but we'll use three here to also align the raw Markdown).
To have a line break without a paragraph, you will need to use two trailing spaces.
Note that this line is separate, but within the same paragraph.
(This is contrary to the typical GFM line break behaviour, where trailing spaces are not required.)
- Unordered list can use asterisks
- Or minuses
- Or pluses
Links
There are two ways to create links.
[I'm an inline-style link](https://www.google.com)
[I'm an inline-style link with title](https://www.google.com "Google's Homepage")
[I'm a reference-style link][Arbitrary case-insensitive reference text]
[You can use numbers for reference-style link definitions][1]
Or leave it empty and use the [link text itself].
URLs and URLs in angle brackets will automatically get turned into links.
http://www.example.com or <http://www.example.com> and sometimes
example.com (but not on Github, for example).
Some text to show that the reference links can follow later.
[arbitrary case-insensitive reference text]: https://www.mozilla.org
[1]: http://slashdot.org
[link text itself]: http://www.reddit.com
I'm an inline-style link with title
You can use numbers for reference-style link definitions
Or leave it empty and use the link text itself.
URLs and URLs in angle brackets will automatically get turned into links.
http://www.example.com or http://www.example.com and sometimes
example.com (but not on Github, for example).
Some text to show that the reference links can follow later.
You can also create standard HTML anchors in a document, and link to them in the markdown using standard links.
Text you want to link to later <a name="something"></a>
...
[A link that links up to the text above](#something)
Text you want to link to later
...
A link that links up to the text above
Images
Here's our logo (hover to see the title text):
Inline-style:
Reference-style:
![alt text][logo]
[logo]: https://sfcommunity.wiki/favicon.ico "Logo Title Text 2"
Here's our logo (hover to see the title text):
Inline-style:
Reference-style:
Code and Syntax Highlighting
Todo: Remove this section, as it's pretty much impossible to show a code block in a code block.
Code blocks are part of the Markdown spec, but syntax highlighting isn't. However, many renderers -- like Github's and Markdown Here -- support syntax highlighting. Which languages are supported and how those language names should be written will vary from renderer to renderer. Markdown Here supports highlighting for dozens of languages (and not-really-languages, like diffs and HTTP headers); to see the complete list, and how to write the language names, see the highlight.js demo page.
Inline `code` has `back-ticks around` it.
Inline code has back-ticks around it.
Blocks of code are either fenced by lines with three back-ticks ```, or are indented with four spaces. I recommend only using the fenced code blocks -- they're easier and only they support syntax highlighting.
var s = "JavaScript syntax highlighting";
alert(s);
s = "Python syntax highlighting"
print s
No language indicated, so no syntax highlighting.
But let's throw in a <b>tag</b>.
var s = "JavaScript syntax highlighting";
alert(s);
s = "Python syntax highlighting"
print s
No language indicated, so no syntax highlighting in Markdown Here (varies on Github).
But let's throw in a <b>tag</b>.
Tables
Tables aren't part of the core Markdown spec, but they are part of GFM and Markdown Here supports them. They are an easy way of adding tables to your email -- a task that would otherwise require copy-pasting from another application.
Colons can be used to align columns.
| Tables | Are | Cool |
| ------------- |:-------------:| -----:|
| col 3 is | right-aligned | $1600 |
| col 2 is | centered | $12 |
| zebra stripes | are neat | $1 |
There must be at least 3 dashes separating each header cell.
The outer pipes (|) are optional, and you don't need to make the
raw Markdown line up prettily. You can also use inline Markdown.
Markdown | Less | Pretty
--- | --- | ---
*Still* | `renders` | **nicely**
1 | 2 | 3
Colons can be used to align columns.
| Tables | Are | Cool |
|---|---|---|
| col 3 is | right-aligned | $1600 |
| col 2 is | centered | $12 |
| zebra stripes | are neat | $1 |
There must be at least 3 dashes separating each header cell.
The outer pipes (|) are optional, and you don't need to make the
raw Markdown line up prettily. You can also use inline Markdown.
| Markdown | Less | Pretty |
|---|---|---|
| Still | renders |
nicely |
| 1 | 2 | 3 |
Blockquotes
> Blockquotes are very handy in email to emulate reply text.
> This line is part of the same quote.
Quote break.
> This is a very long line that will still be quoted properly when it wraps. Oh boy let's keep writing to make sure this is long enough to actually wrap for everyone. Oh, you can *put* **Markdown** into a blockquote.
Blockquotes are very handy in email to emulate reply text. This line is part of the same quote.
Quote break.
Blockquotes are very handy in email to emulate reply text.
This line is part of the same quote.
Quote break.
This is a very long line that will still be quoted properly when it wraps. Oh boy let's keep writing to make sure this is long enough to actually wrap for everyone. Oh, you can put Markdown into a blockquote.
Blockquotes are very handy in email to emulate reply text. This line is part of the same quote.
Quote break.
Horizontal Rule
Three or more...
---
Hyphens
***
Asterisks
___
Underscores
Hyphens must have a blank line above them, or they're interpreted as a heading.
Three or more...
Hyphens
Asterisks
Underscores
Hyphens must have a blank line above them, or they're interpreted as a heading.
Line Breaks
My basic recommendation for learning how line breaks work is to experiment and discover -- hit
Here are some things to try out:
Here's a line for us to start with.
This line is separated from the one above by two newlines, so it will be a *separate paragraph*.
This line is also a separate paragraph, but...
This line is only separated by a single newline, so it's a separate line in the *same paragraph*.
Here's a line for us to start with.
This line is separated from the one above by two newlines, so it will be a separate paragraph.
This line is also begins a separate paragraph, but...
This line is only separated by a single newline, so it's a separate line in the same paragraph.
(Technical note: Markdown Here uses GFM line breaks, so there's no need to use MD's two-space line breaks.)
Sidebars
::: sidebar left
![SFCommunity Wiki Logo][sitelogo]
This is a left sidebar.
:::
::: sidebar right
![SFCommunity Wiki][sitelogo]
This is a right sidebar.
:::
[sitelogo]: https://sfcommunity.wiki/uploads/logo.png
This is a left sidebar.
This is a right sidebar.
Templates
Creature/NPC (CR X)
XP 307,200
Space goblin technomancer
NE Large humanoid (goblinoid)
Init +9; Senses darkvision 60 ft.; Perception +34
Aura unnatural aura (30 ft.)
DEFENSE
HP 395; RP 7
EAC 34; KAC 35
Fort +17; Ref +17; Will +22; +4 vs. enchantments
Defensive Abilities natural invisibility; DR 10/magic; Immunities fire; Resistances sonic 20; SR 31
Weaknesses light sensitivity
OFFENSE
Speed 35 ft., climb 20 ft., swim 30 ft.; earth glide
Melee quantum dogslicer +28 (13d6+22 S)
Multiattack quantum dogslicer +24 (13d6+22 S), bite +24
(9d6+22 P)
Ranged junklaser bazooka +3 (4d12+20 F; critical burn 1d8)
Space 10 ft.; Reach 10 ft. (15 ft. with bite)
Offensive Abilities breath weapon (80-ft. line, 5d8 A, Reflex DC 27 half, usable every 1d4 rounds)
Spell-Like Abilities (CL 20th)
At will—charm person (DC 24)
Technomancer Spells Known (CL 20th)
6th (7/day)—chain surge (DC 29), disintegrate (DC 29), flight, interplanetary teleport, true seeing
5th (7/day)—control machines (DC 28), heat leech (DC 28), synapse overload (DC 28), telekinesis, wall of force
4th (7/day)—corrosive haze (DC 27), dimension door, overload systems (DC 27), rewire flesh (DC 27), soothing protocol, wall of fire
STATISTICS
Str +2; Dex +9; Con +2; Int +12; Wis +2; Cha +6
Skills Computers +39, Engineering +34, Stealth +39
Feats Cleave, Mobility
Languages Common, Goblin
Other Abilities water breathing
Gear nanotube carbon skin, junklaser bazooka, quantum dogslicer, spell cache, 1,000 credits
ECOLOGY
Environment any
Organization solitary or cult (1 plus 20–30 space goblins of CR 3–4)
SPECIAL ABILITIES
Breath Weapon (Su) A space goblin monark can exhale a line of caustic acid as a standard action.
Race
Insert image here, replacing this text
Racial Traits
Ability Adjustments: +2 Con, +2 Int, -2 Str
Hit Points: 6
Size and Type: Greox are small humanoids, with the greox subtype.
Natural Weapons: Greox have natural weapons that functions like those of vesk, except the greok's bite deals piercing damage.
Scrounger: Greox receive a +2 racial bonus to Engineering, Stealth, and Survival checks.
Scrappy: Despite their small size, greox are surprisingly resilient. Greox gain 1 additional Resolve Point at 1st level.
Toxicity Resistance: Greox have a +2 racial bonus to saving throws vs poisons and diseases. Greox have acid resistance 5, which stacks with one other source of acid resistance.
Easily Frightened: Greox have a -2 racial penalty to saving throws vs fear effects.
Description
Physical Description
Replace this text with a physical description of the race.
Homeworld
Replace this text with information about the race's homeworld, if they have one. You can also use links to link to a page about it, if it exists.
Society and Alignment
*Replace this text with information about the major society comprised of by the race, and the usual temperment and aligment of creatures of this race.
Relations
Replace this text with a specific examples of other races that this race may have particular relations with, such as rivalries or partnerships.
Adventurers
Replace this text with a description of the usual mindset or justifications that members of this race that tend to go out and become adventurers has or exhibits.
Names
Replace this text with a list of some example names for the race, to give folks a good idea of how to make their own.