Codenrock
  • Codenrock
  • Руководство по настройке
    • С чего начать?
    • Быстрый старт
    • Регистрация
    • Создание мероприятия
    • Настройка мероприятия
      • Вкладка "Главное"
      • Вкладка "Прочее"
      • Вкладки "Интеграции", "Меню", "Действия"
      • Загрузка баннера события
      • Страница "О событии"
      • Страница "Правила"
      • Страница “Анкета”
      • Страница "Задания"
      • Страница "Голосование"
      • Страница "FAQ"
      • Совместный доступ
      • Генератор сертификатов
      • Форма обратной связи
      • Публикация мероприятия
    • Статистики
      • Дашбоард
      • Общий рейтинг
      • Список участников
      • Команды
      • Рассылки
      • Вопросы
      • Активности
      • Экспорт и импорт
    • Настройки firewall для Codenrock
    • Помощь по загрузке решений
  • Setup guide
    • Where to start from?
    • Quick Start
    • Registration
    • How to Create an Event
    • Setting up an event
      • Main Tab
      • Other Tab
      • “Integrations”, “Menu”, and “Actions” Tabs
      • How to Upload the Event Banner
      • “About” Page
      • “Rules” Page
      • "Registration Form" Page
      • "Tasks" Pag
      • "Voting" Page
      • "FAQ" Page
      • How to Publish an Event
    • Statistics
      • Dashboard
      • Overall Rating
      • List of participants
      • Teams
      • Notifications
      • Questions
      • Activities
      • Export and Import
  • Дополнительная информация
    • Markdown Cheatsheet
    • Помощь по редактору в Обсуждениях
  • Наша история и ценности
  • О продукте
  • Информационная поддержка мероприятий
  • Курс: Организатор хакатонов с нуля до PRO
Powered by GitBook
On this page
  • Headers
  • Lists
  • Links
  • Images
  • Code and Syntax Highlighting
  • Tables
  • Blockquotes
  • Horizontal Rule
  • Line Breaks
  • YouTube Videos

Was this helpful?

  1. Дополнительная информация

Markdown Cheatsheet

PreviousExport and ImportNextПомощь по редактору в Обсуждениях

Last updated 3 years ago

Was this helpful?

This is intended as a quick reference and showcase. For more complete info, see and the .

Headers

# H1
## H2
### H3
#### H4
##### H5
###### H6

Alternatively, for H1 and H2, an underline-ish style:

Alt-H1
======

Alt-H2
------

Lists

(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
  1. First ordered list item

  2. Another item

  • Unordered sub-list.

  1. Actual numbers don't matter, just that it's a number

  2. Ordered sub-list

  3. 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.codenrock.com)

[I'm an inline-style link with title](https://www.codenrock.com "Codenrock 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.codenrock.com
[1]: http://codenrock.org
[link text itself]: http://www.codenrock.com

Some text to show that the reference links can follow later.

Images

Here's our logo (hover to see the title text):

Inline-style: 
![alt text](https://contestfiles.s3.eu-central-1.amazonaws.com/tilda/20753841/tild3535-3832-4938-b836-386533353930___1ldpi.svg "Logo Title Text 1")

Reference-style: 
![alt text][logo]

[logo]: https://contestfiles.s3.eu-central-1.amazonaws.com/tilda/20753841/tild3535-3832-4938-b836-386533353930___1ldpi.svg "Logo Title Text 2"

Here's our logo (hover to see the title text):

Code and Syntax Highlighting

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.

```javascript
var s = "JavaScript syntax highlighting";
alert(s);
```
 
```python
s = "Python syntax highlighting"
print s
```

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.

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.

Horizontal Rule

Three or more...

---

Hyphens

***

Asterisks

___

Underscores

Three or more...

Hyphens

Asterisks

Underscores

Line Breaks

My basic recommendation for learning how line breaks work is to experiment and discover -- hit <Enter> once (i.e., insert one newline), then hit it twice (i.e., insert two newlines), see what happens. You'll soon learn to get what you want. "Markdown Toggle" is your friend.

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.)

YouTube Videos

They can't be added directly but you can add an image with a link to the video like this:

<a href="http://www.youtube.com/watch?feature=player_embedded&v=YOUTUBE_VIDEO_ID_HERE
" target="_blank"><img src="http://img.youtube.com/vi/YOUTUBE_VIDEO_ID_HERE/0.jpg" 
alt="IMAGE ALT TEXT HERE" width="240" height="180" border="10" /></a>

Or, in pure Markdown, but losing the image sizing and border:

[![IMAGE ALT TEXT HERE](http://img.youtube.com/vi/YOUTUBE_VIDEO_ID_HERE/0.jpg)](http://www.youtube.com/watch?v=YOUTUBE_VIDEO_ID_HERE)

Or leave it empty and use the .

URLs and URLs in angle brackets will automatically get turned into links. or and sometimes example.com (but not on Github, for example).

Inline-style:

Reference-style:

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 .

Author: Adam Pritchard Origin text:

John Gruber's original spec
Github-flavored Markdown info page
I'm an inline-style link
I'm an inline-style link with title
I'm a reference-style link
You can use numbers for reference-style link definitions
link text itself
http://www.example.com
http://www.example.com
highlight.js demo page
https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet
alt text
alt text