[Tutoriel] Le langage de ce forum : ** Markdown **



  • Les forums ont toujours utilisé le bbcode pour la syntaxe, mais depuis quelques années, le Markdown s’est imposé sur de nombreuse plateformes.

    Voici un résumé des possibilités :

    Headers

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

    H1

    H2

    H3

    H4

    H5
    H6

    Emphase

    Italic avec *asterisks* or _underscores_.
    
    Gras avec **asterisks** or __underscores__.
    
    Emphases combinées avec **asterisks and _underscores_**.
    
    Barrés avec deux tildes. ~~Barrez moi.~~
    

    Italic avec asterisks or underscores.

    Gras avec asterisks or underscores.

    Emphases combinées avec asterisks and underscores.

    Barrés avec deux tildes. Barrez moi.

    Listes

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

    Liens

    Il y a deux façon de créer des liens

    [I'm an inline-style link](https://www.google.com)
    
    [I'm an inline-style link with title](https://www.google.com "Google's Homepage")
    
    [I'm a reference-style link][Arbitrary case-insensitive reference text]
    
    [I'm a relative reference to a repository file](../blob/master/LICENSE)
    
    [You can use numbers for reference-style link definitions][1]
    
    Or leave it empty and use the [link text itself]
    
    Some text to show that the reference links can follow later.
    
    [arbitrary case-insensitive reference text]: https://www.mozilla.org
    [1]: http://slashdot.org
    [link text itself]: http://www.reddit.com
    

    I’m an inline-style link

    I’m an inline-style link with title

    I’m a reference-style link

    I’m a relative reference to a repository file

    You can use numbers for reference-style link definitions

    Or leave it empty and use the link text itself

    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://github.com/adam-p/markdown-here/raw/master/src/common/images/icon48.png "Logo Title Text 1")
    
    Reference-style: 
    ![alt text][logo]
    
    [logo]: https://github.com/adam-p/markdown-here/raw/master/src/common/images/icon48.png "Logo Title Text 2"
    

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

    Inline-style:
    alt text

    Reference-style:
    alt text

    Code and Syntax Highlighting

    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 highlight.js demo page.

    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 <code>```</code>, or are indented with four spaces. I recommend only using the fenced code blocks – they’re easier and only they support syntax highlighting.

    <pre lang=“no-highlight”><code>```javascript
    var s = “JavaScript syntax highlighting”;
    alert(s);

     
    ```python
    s = "Python syntax highlighting"
    print s
    
    No language indicated, so no syntax highlighting. 
    But let's throw in a &lt;b&gt;tag&lt;/b&gt;.
    

    </code></pre>

    var s = "JavaScript syntax highlighting";
    alert(s);
    
    s = "Python syntax highlighting"
    print s
    
    No language indicated, so no syntax highlighting in Markdown Here (varies on Github). 
    But let's throw in a <b>tag</b>.
    

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

    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

    <a name=“blockquotes”/>

    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.

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



  • je n’ai pas encore tout traduit, mais je suppose que la plupart des gens ici savent parler anglais :P





  • Hello,
    ouai, moi qui connaissait un peu le bbcode …
    J’ai pas vraiment la patience d’apprendre le Markdown … -------> je vais me désinscrire de CryptoFR.
    PS : Non, j’déconne… ce forum est très cool, bravo à ffmad (et puis en + faut pas croire toutes les conneries que j’écris).



  • @Crypto_King a dit :

    Hello,
    ouai, moi qui connaissait un peu le bbcode …
    J’ai pas vraiment la patience d’apprendre le Markdown … -------> je vais me désinscrire de CryptoFR.
    PS : Non, j’déconne… ce forum est très cool, bravo à ffmad (et puis en + faut pas croire toutes les conneries que j’écris).

    tu penses quoi du markdown ?

    Au début je trouvais çà un peu dérangeant (en ayant écrit en bbcode pendant des années), mais au final c’est beaucoup plus intuitif je trouve ^^


Se connecter pour répondre