![]() ![]() No language indicated, so no syntax highlighting. Var s = "JavaScript syntax highlighting" Bold markdown code#I recommend only using the fenced code blocks - they're easier and only they support syntax highlighting. Inline `code` has `back-ticks around` it.īlocks of code are either fenced by lines with three back-ticks ```, or are indented with four spaces. Bold markdown how to#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. However, many renderers - like Github's and Markdown Here - support syntax highlighting. Here's our logo (hover to see the title text):Ĭode blocks are part of the Markdown spec, but syntax highlighting isn't. Or leave it empty and use the link text itself You can use numbers for reference-style link definitions Some text to show that the reference links can follow later. Some text that should be aligned with the above item.Īctual numbers don't matter, just that it's a number Actual numbers don't matter, just that it's a number Strong emphasis, aka bold, with asterisks or underscores.Ĭombined emphasis with asterisks and underscores. ~~Scratch this.~~Įmphasis, aka italics, with asterisks or underscores. Strong emphasis, aka bold, with **asterisks** or _underscores_.Ĭombined emphasis with **asterisks and _underscores_**. Table of ContentsĪlternatively, for H1 and H2, an underline-ish style:Įmphasis, aka italics, with *asterisks* or _underscores_. In the following example, we will take those ico-font class names and place them in an array. Loop through a list of these names and then write out the HTML we need for the browser. There is no trailing space at the end of this line Let's take this and using a simple feature in HAML we can write code that will icon-strategy, icon-strategy_01, icon-chevron-right and icon-chevron-left for instance. Looking at the previous example, just about all the code is duplicated, except for the class names. ![]() There is only one trailing space at the end of this line We have the technology to make this better. That is easy to manage, but there is a lot of repeated code in there and we as developers HATE repeated code. ![]() There are two trailing spaces at the end of this line. There are no spaces at the end of this line There is only one space at the end of this line Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. There are two spaces at the end of this line You can play around with Markdown on our live demo page. This differs slightly in styling and syntax from what Github uses, so what you see below might vary a little from what you get in a Markdown Here email, but it should be pretty close. This cheatsheet is specifically Markdown Here's version of Github-flavored Markdown. ![]() For more complete info, see John Gruber's original spec and the Github-flavored Markdown info page. This is intended as a quick reference and showcase. #212121Īlternatively, for H1 and H2, an underline-ish style: Alt-H1 Alt-H2 #4d4d4d H6: Roughdraft is GitHub Gists, made pretty. #646464 H5: Roughdraft is GitHub Gists, made pretty. #7a7a7a H4: Roughdraft is GitHub Gists, made pretty. #7a7a7a H3: Roughdraft is GitHub Gists, made pretty. #7a7a7a H2: Roughdraft is GitHub Gists, made pretty. H1: Roughdraft is GitHub Gists, made pretty. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |