style-guide: organize content and update sections; *: fix Markdownlint errors (#12148)
* style-guide: organize content and add contents section * style-guide: fix general writing section title * style-guide: fix heading level of help and version commands * style-guide: fix heading level of see also section * cleanup: update files Signed-off-by: K.B.Dharun Krishna <kbdharunkrishna@gmail.com> * contributing: fix page for markdown lint Signed-off-by: K.B.Dharun Krishna <kbdharunkrishna@gmail.com> * fix: markdownlint errors across files Signed-off-by: K.B.Dharun Krishna <kbdharunkrishna@gmail.com> * docs: improve documentation about keycaps Signed-off-by: K.B.Dharun Krishna <kbdharunkrishna@gmail.com> * docs: add info about optional and string placeholders Signed-off-by: K.B.Dharun Krishna <kbdharunkrishna@gmail.com> * cleanup: sync changes with recent versions of style guide Signed-off-by: K.B.Dharun Krishna <kbdharunkrishna@gmail.com> * cleanup: update style guide Co-authored-by: Vítor Henrique <87824454+vitorhcl@users.noreply.github.com> * docs: update style guide Co-authored-by: Vítor Henrique <87824454+vitorhcl@users.noreply.github.com> * docs/style-guide: reword more info links section Co-authored-by: Vítor Henrique <87824454+vitorhcl@users.noreply.github.com> --------- Signed-off-by: K.B.Dharun Krishna <kbdharunkrishna@gmail.com> Co-authored-by: K.B.Dharun Krishna <kbdharunkrishna@gmail.com>
This commit is contained in:
@@ -1,3 +1,4 @@
|
||||
<!-- markdownlint-disable MD007 MD013 MD024-->
|
||||
# tldr-pages client specification
|
||||
|
||||
**Current Specification Version:** 2.2
|
||||
@@ -112,7 +113,7 @@ The structure inside these translation folders is identical to that of the main
|
||||
|
||||
## Page structure
|
||||
|
||||
Although this specification is about the interface that clients must provide, it is also worth noting that pages are written in standard [CommonMark](https://commonmark.org/), with the exception of the non-standard `{{` and `}}` placeholder syntax, which surrounds values in an example that users may edit. Clients MAY highlight the placeholders and MUST remove the surrounding curly braces. Clients MUST NOT treat them as the placeholder syntax if they are escaped using `\` (i.e. `\{\{` and `\}\}`) and MUST instead display literal braces, without backslashes. Placeholder escaping applies only when both braces are escaped (e.g. in `\{` or `\{{`, backslashes MUST be displayed). In cases when a command uses `{}` in its arguments (e.g. `stash@{0}`) ***the outer braces*** mark the placeholder - the braces inside MUST be displayed. Clients MUST NOT break if the page format is changed within the _CommonMark_ specification.
|
||||
Although this specification is about the interface that clients must provide, it is also worth noting that pages are written in standard [CommonMark](https://commonmark.org/), with the exception of the non-standard `{{` and `}}` placeholder syntax, which surrounds values in an example that users may edit. Clients MAY highlight the placeholders and MUST remove the surrounding curly braces. Clients MUST NOT treat them as the placeholder syntax if they are escaped using `\` (i.e. `\{\{` and `\}\}`) and MUST instead display literal braces, without backslashes. Placeholder escaping applies only when both braces are escaped (e.g. in `\{` or `\{{`, backslashes MUST be displayed). In cases when a command uses `{}` in its arguments (e.g. `stash@{0}`) **_the outer braces_** mark the placeholder - the braces inside MUST be displayed. Clients MUST NOT break if the page format is changed within the _CommonMark_ specification.
|
||||
|
||||
### Examples
|
||||
|
||||
|
Reference in New Issue
Block a user