Skip to content

Commit

Permalink
Markdown Tutorial
Browse files Browse the repository at this point in the history
  • Loading branch information
hsrai authored Dec 30, 2024
1 parent 4f716fb commit 478a036
Showing 1 changed file with 127 additions and 0 deletions.
127 changes: 127 additions & 0 deletions HSRai/Files/GiHubPages/MarkDown.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,127 @@
## Sample of ~~marcdn~~ markdown ~AMC single tidle~

[Link to another page](./another-page.html). This link points to no-existance file, so will not work.

[Link to real page | First Encounter to GitHub](taskStatement.md)

There should be whitespace between paragraphs.

# Header 1

This is a normal paragraph following a header (the largest, bigger one, normaly used for title). We need to use `# <and one space>Title`
GitHub is a code hosting platform for version control and collaboration.
It lets you and others work together on projects from anywhere.

The above three will nor rendered as separate 3 lines, but produces one single paragraph.

## Header 2

> This is a blockquote following a header.
>
> When something is important enough, you do it even if the odds are not in your favor. `##` Used for Major heading.
### Header 3

`###` used for sub-heading.

Single backtick (`) is used to write some coding part withing a paragraph. It is is also
known as backquote, grave, or grave accent.

Longer code (multiple lise) is enclosed within triple backtick, and `computer language` is written after the
opening triple backticks. Like `js` for `Javascript`.

```js
// Javascript code with syntax highlighting.
var fun = function lang(l) {
dateformat.i18n = require('./lang/' + l)
return true;
}
```

```ruby
# Ruby code with syntax highlighting
GitHubPages::Dependencies.gems.each do |gem, version|
s.add_dependency(gem, "= #{version}")
end
```

#### Header 4

* This is an unordered list following a header (`Star/Asterisk<Space>).
* This is an unordered list following a header.
* This is an unordered list following a header.

##### Header 5

1. This is an ordered list following a header.
2. This is an ordered list following a header.
3. This is an ordered list following a header.

###### Header 6

| head1 | head two | three |
|:-------------|:------------------|:------|
| ok | good swedish fish | nice |
| out of stock | good and plenty | nice |
| ok | good `oreos` | hmm |
| ok | good `zoute` drop | yumm |

### There's a horizontal rule below this.

* * *

***

---

Another way:

---

### Here is an unordered list:

* Item foo
* Item bar
* Item baz
* Item zip

### And an ordered list:

1. Item one
1. Item two
1. Item three
1. Item four

### And a nested list:

- level 1 item
- level 2 item
- level 2 item
- level 3 item
- level 3 item
- level 1 item
- level 2 item
- level 2 item
- level 2 item
- level 1 item
- level 2 item
- level 2 item
- level 1 item

### Small image

![Octocat](https://github.githubassets.com/images/icons/emoji/octocat.png)

### Large image

![Branching](https://guides.github.com/activities/hello-world/branching.png)

Text can be _italic_, or ~~strikethrough~~.

```
Long, single-line code blocks should not wrap. They should horizontally scroll if they are too long. This line should be long enough to demonstrate this.
```

```
The final element.
```

0 comments on commit 478a036

Please sign in to comment.