Lines Matching full:markdown

1 # Markdown style guide
3 Much of what makes Markdown great is the ability to write plain text, and get
5 your Markdown should be simple and consistent with the whole corpus wherever
11 2. *Markdown files are maintainable over time and across teams.*
32     1.  [Use informative Markdown link titles](#use-informative-markdown-link-titles)
35 1.  [Strongly prefer Markdown to HTML](#strongly-prefer-markdown-to-html)
41 ```markdown
72 …[`[TOC]` documentation](https://gerrit.googlesource.com/gitiles/+/master/Documentation/markdown.md…
85 ```markdown
90 …et. See the [foo docs](https://gerrit.googlesource.com/gitiles/+/master/Documentation/markdown.md).
96 ```markdown
98 [foo docs](https://gerrit.googlesource.com/gitiles/+/master/Documentation/markdown.md)
111 Best practice is to avoid the need for a `<br />` altogether. Markdown creates
118 ```markdown
126 ```markdown
135 ```markdown
145 ```markdown
156 Markdown is smart enough to let the resulting HTML render your numbered lists
160 ```markdown
171 ```markdown
181 ```markdown
196 ```markdown
205 ```markdown
217 ```markdown
233 ```markdown
242 ```markdown
246 Backticks are the most common approach for "escaping" Markdown metacharacters;
272 ```markdown
304 ```markdown
317 ```markdown
327 Long links make source Markdown difficult to read and break the 80 character
330 ### Use informative Markdown link titles
332 Markdown link syntax allows you to set a link title, just as HTML does. Use it
338 ```markdown
347 ```markdown
359 See [image syntax](https://gerrit.googlesource.com/gitiles/+/master/Documentation/markdown.md#Image…
363 Any tables in your Markdown should be small. Complex, large tables are difficult
366 ```markdown
378 ```markdown
400 ```markdown
408 ## Strongly prefer Markdown to HTML
410 Please prefer standard Markdown syntax wherever possible and avoid HTML hacks.
412 need it. Except for [big tables](#prefer-lists-to-tables), Markdown meets almost