You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+16-4Lines changed: 16 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,12 +5,13 @@ This markdown reference generator uses
5
5
a document tree with markdown files containing
6
6
a special annotation syntax for tags and references
7
7
as input and generates an appropriate target tree with
8
-
references resolved to resolved Markdown links
8
+
references resolved to consistent Markdown links
9
9
and anchors.
10
10
11
-
- Never fix heading anymore with corrupting links all over the document tree
11
+
- Never fix headings anymore with corrupting links all over the document tree
12
12
- Never move text blocks or even complete files around in the document tree with corrupting links all over the document tree
13
13
- Use terms all over the document tree, which are automatically linked to their explanation.
14
+
- Provide examples documentation consistent with working code.
14
15
15
16
## Command Line Syntax
16
17
@@ -36,6 +37,17 @@ and usage list is printed.
36
37
37
38
The source folder may not only contain markdown files. The generator copies all non-markdown files in the same structure to the target folder.
38
39
40
+
## General Annotation Syntax
41
+
42
+
Annotations used by this generator use a common syntax
43
+
44
+
```
45
+
{{<elementsyntax>}}
46
+
```
47
+
48
+
Elements may be [anchors](doc/chapters/references.md#anchors), [term anchors](doc/chapters/terms.md#anchors), [references](doc/chapters/references.md#references) or [commands](doc/chapters/commands.md#commands).
49
+
50
+
39
51
## Reference and Anchor Syntax
40
52
41
53
Anchors and references are character sequences
@@ -53,8 +65,8 @@ may be copied or even moved into a completely different folder structure without
53
65
Therefore, the anchors must be globally unique in the
Copy file name to clipboardExpand all lines: doc/chapters/terms.md
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,8 @@
3
3
4
4
Instead of using a reference as target for a markdown
5
5
reference it may be used as complete markdown linked text.
6
-
In this case the [logical reference](references.md#reference-targets) appears inside the `[]` pair of a markdown reference, but without the target part:
6
+
In this case the [logical reference](references.md#references) appears inside the `[]` pair
7
+
of a markdown reference, but without the target part:
7
8
8
9
<pre>
9
10
A [{{<name>}}] is a ....
@@ -22,7 +23,8 @@ There are several flavors for using a term:
22
23
23
24
### Anchors
24
25
25
-
Anchors for terms are just defined by using the reference syntax outside the markdown reference syntax and adding a text separated by a colon ( `:`).
26
+
Anchors for terms are just defined by using the reference syntax outside the
27
+
Markdown reference syntax and adding a text separated by a colon ( `:`).
26
28
27
29
For example
28
30
@@ -32,4 +34,6 @@ For example
32
34
</pre>
33
35
34
36
It might be placed anywhere in a Markdown document,
35
-
therefore, it is possible to link to any location, not only section headers.
37
+
therefore, it is possible to link to any location, not only section headers.
38
+
39
+
Term anchors may be used for regular references, also.
0 commit comments