> For the complete documentation index, see [llms.txt](https://ykkim.gitbook.io/ec/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ykkim.gitbook.io/ec/other-programming/markdown.md).

# Markdown

## Markdown Editor

We will use 'Typora' as the offline Markdown editor.

Typora(무료, 구버전): [Download from here](https://drive.google.com/file/d/1UmDNSUdOqj_w2y3YWqwOY-gAXmrvtxKO/view?usp=sharing)

Typora(유료, 최신버전): [Download from here](https://typora.io/#windows)

## What is Markdown?

[Markdown](http://daringfireball.net/projects/markdown/) is a way to style text on the web. You control the display of the document; formatting words as bold or italic, adding images, and creating lists are just a few of the things we can do with Markdown. Mostly, Markdown is just regular text with a few non-alphabetic characters thrown in, like `#` or `*`.

You can use Markdown most places around GitHub:

* [Gists](https://gist.github.com)
* Comments in Issues and Pull Requests
* Files with the `.md` or `.markdown` extension: README.md

## Syntax guide

Here’s an overview of Markdown syntax that you can use anywhere on GitHub.com or in your own text files.

#### Headers

```
# This is an <h1> tag
## This is an <h2> tag
###### This is an <h6> tag
```

#### Emphasis

```
*This text will be italic*
_This will also be italic_

**This text will be bold**
__This will also be bold__

_You **can** combine them_
```

**Unordered List**

```
* Item 1
* Item 2
  * Item 2a
  * Item 2b
```

**Ordered List**

```
1. Item 1
1. Item 2
1. Item 3
   1. Item 3a
   1. Item 3b
```

#### Images

```
Format: ![Alt Text](url)

![GitHub Logo](/images/logo.png)
![Image of Yaktocat](https://octodex.github.com/images/yaktocat.png)
```

#### Links

```
http://github.com - automatic!
[GitHub](http://github.com)
```

#### Blockquotes

```
As Kanye West said:

> We're living the future so
> the present is our past.
```

#### Inline code

```
I think you should use an
`<addr>` element here instead.
```

**Block code**

````
```javascript
function fancyAlert(arg) {
  if(arg) {
    $.facebox({div:'#foo'})
  }
}
```


```C
int main()
{
 return 0;
}
```
````

## Examples

* [Text](https://guides.github.com/features/mastering-markdown/)
* [Lists](https://guides.github.com/features/mastering-markdown/)
* [Images](https://guides.github.com/features/mastering-markdown/)
* [Headers & Quotes](https://guides.github.com/features/mastering-markdown/)
* [Code](https://guides.github.com/features/mastering-markdown/)
* [Extras](https://guides.github.com/features/mastering-markdown/)

````
There are many different ways to style code with GitHub's markdown. If you have inline code blocks, wrap them in backticks: `var example = true`.  If you've got a longer block of code, you can indent with four spaces:

    if (isAwesome){
      return true
    }

GitHub also supports something called code fencing, which allows for multiple lines without indentation:

```
if (isAwesome){
  return true
}
```

And if you'd like to use syntax highlighting, include the language:

```javascript
if (isAwesome){
  return true
}
```
````

There are many different ways to style code with GitHub’s markdown. If you have inline code blocks, wrap them in backticks: `var example = true`. If you’ve got a longer block of code, you can indent with four spaces:

```
if (isAwesome){
  return true
}
```

GitHub also supports something called code fencing, which allows for multiple lines without indentation:

```
if (isAwesome){
  return true
}
```

And if you’d like to use syntax highlighting, include the language:

```
if (isAwesome){
  return true
}
```

## Reference

{% embed url="<https://guides.github.com/features/mastering-markdown/#syntax>" %}

##


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ykkim.gitbook.io/ec/other-programming/markdown.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.