a brief introduction to an interesting language ---Markdown

Beatless7 commented 3 years ago

Preface

Well, it's my first time to blog. In fact, the purpose of blog for me is to improve my knowledge and communicate with fans in the field of computer technology. I'm a college student major in computer science and technology, I learn a variety of knowledge almost everyday. As a result, I'd like to not only record what I learn everyday but also share and discuss with you. Let's get to the point！

Markdown

I choose Markdown as my first theme of blog because it's essential to learn. He is obviously useful in recording, Blog publishing needs markdown language.

So what is Markdown?

Markdown is a lightweight markup language for creating formatted text using a plain-text editor. John Gruber and Aaron Swartz created Markdown in 2004 as a markup language that is appealing to human readers in its source code form. Markdown is widely used in blogging, instant messaging, online forums, collaborative software, documentation pages, and readme files.

Why use Markdown？

You might be wondering why people use Markdown instead of a WYSIWYG editor. Why write with Markdown when you can press buttons in an interface to format your text? As it turns out, there are a couple different reasons why people use Markdown instead of WYSIWYG editors.

Markdown can be used for everything. People use it to create websites, documents, notes, books, presentations, email messages, and technical documentation.

Markdown is portable. Files containing Markdown-formatted text can be opened using virtually any application. If you decide you don’t like the Markdown application you’re currently using, you can import your Markdown files into another Markdown application. That’s in stark contrast to word processing applications like Microsoft Word that lock your content into a proprietary file format.

Markdown is platform independent. You can create Markdown-formatted text on any device running any operating system.

Markdown is future proof. Even if the application you’re using stops working at some point in the future, you’ll still be able to read your Markdown-formatted text using a text editing application. This is an important consideration when it comes to books, university theses, and other milestone documents that need to be preserved indefinitely.

Markdown is everywhere. Websites like Reddit and GitHub support Markdown, and lots of desktop and web-based applications support it.

how to use it

To use Markdown, you just apply simple tags to your text. Headings

# H1              This is a first level title
## H2            This is a second level title
### H3          This is a third level title

Wrapping Text

Splitting long lines (preferably up to 100 characters) can make it easier to provide feedback on small chunks of text. Do not leave blank spaces after the last word of the line broken within a paragraph, unless you want it to be intentionally broken with a
.

This text is a paragraph.
This won't be another paragraph, it will join the line above it.

This will be another paragraph, as it has a blank line above it.

Emmm, I don't know why is it wrong , please tell me if you know about it!

bold and italic

This is **bold** and this is _italic_.

This is ***bold and italic***.

Links

There are a few different ways to display links with markdown markup, but to keep some standards, let's try to use the following options only.

Important notes:

Don't take it as a restrictive rule, but avoid using meaningless text for links as "this article" or "read here." The link text should be meaningful even if taken out of context; this makes the links more useful and accessible for people using screen readers. Check for broken links: http://www.deadlinkchecker.com/ Inline Links We'd rather use inline links, such as Text to display, as they are easier to maintain. To make an inline link open in a new tab, you can add {:target="_blank"} to the end. Ex: Text to display{:target="_blank"}

Relative links Use relative links when referring to links found on about.gitlab.com. For example, a link to our blog handbook should look like this /handbook/marketing/blog/ and not this /handbook/marketing/blog/. Remove everything from the https through about.gitlab.com, but retain the forward slash after .com.

Learn more in the Markdown Guide.

For links to GitLab.com or anywhere else you must use the entire link, including the http:.

Mailto links If you're adding an email address to a page be sure to format your link with mailto to avoid creating broken links. For example, example@gitlab.com

Lists

Both ordered and unordered lists are very straightforward to produce. There are a few ways to produce the same results, but let's stick with the following, again, to maintain some standards.

Always use 3 blank spaces to indent a nested list (to create sub items).

Tip: don't leave blank lines between the items, unless you have a reason to do so. Ordered lists Ordered lists are pretty easy to create. Couldn't be more intuitive:

Paragraph:
1. Item one
   1. Sub item one
   2. Sub item two
   3. Sub item three
2. Item two

Unordered lists

Paragraph:

- Item 1
- Item 2
- Item 3
   - Sub item 1
   - Sub item 2
- Item 4

Images

To insert images to your markdown file, use the markup . The path can either be relative to the website, or a full URL for an external image. The supported formats are .png, .jpg, .gif. You might be able to use some .svg files too, depending on its structure.

**![Semantic description of image](/images/path/to/folder/image.png "Image Title")**

You can also use an identifier, as we do for links:

![Semantic description of image][identifier]

Epilogue

Well, That's all for now. I will keep updating this topic .There may be many inappropriate places in the article. I hope you will give me your advice! Thanks a lot!

Password-ops commented 3 years ago

The article of the blogger is really wonderful, which benefits me a lot. I think the first article of the blogger is very good. I look forward to more excellent works of the blogger.

Beatless7 commented 3 years ago

The article of the blogger is really wonderful, which benefits me a lot. I think the first article of the blogger is very good. I look forward to more excellent works of the blogger.

Well, It'my pleasure that my passage benifit a lot, hope we can make progress together!

Beatless7 / beatless.github.io