incodoc 0.5.0

Incorporeal document format.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152

features:

- [x] metadata
  - tags: string
  - props: key pairs
- [x] navigation
  - links lists of lists of links
- [x] headings
- [x] sections
- [x] text
- [x] links
  - tag, local file, web url, email, ...
  - link type hint in meta: img, vid, pdf
- [x] emphasis
  - emphasis/deemphasis
  - light, medium, strong
- [x] lists
  - ordered, unordered, checked, recursive
- [x] paragraphs
  - single lines by hinting in meta
- [x] tables
  - header rows and regular rows
  - rows of paragraphs
- [x] code
  - language hint
  - mode hint: show, executable, replace with result, ...
  - could be opened in editor
  - could be assigned a renderer by the user (eg. bat)
- background text: in props
  - titles for links
  - alt for images
  - etc
- tags
  - anything can have a tag
  - links can link to tags

heading
  - wrong level: auto fix?
link
  - empty items: fix by putting url as text

dedup nav, par, section

think about doing:

recursive is_contentless? eg section with empty par

things to write about

- all the features and suggested use
https://www.gnu.org/licenses/license-recommendations.html
https://www.marginalia.nu/log/a_119_pdf/

think about:

common image
  string -> image
  user supplies the images
  emoji, stickers, gifs, etc
  fallback img
  link with url convention?
tables and graphs
  regular table with incodoc items in it
  data frames that can be rendered as tables or graphs
  links to outside resources (csv, etc)

anti features:

colours
fonts
spacing
layout

are these anti features?

line breaks?
horizontal rules?

half cooked examples:

'Truth table for X AND Y',
data{
    props{
        ("type-hint", "table"),
        ("ex-hint", "suggested"),
    },
    [
        [
            ['T', F],
            ['T', F],
        ],
        [
            ['T', 'F'],
            ['F', 'F'],
        ],
    ],
},
'This is a graph of my happiness:',
data{
    props{
        ("type-hint", "line-graph"),
        ("ex-hint", "suggested"),
    },
    [
        [
            'year',
            'happiness',
        ],
        [
            (0, 100), (1, 90.5), (2, 72.3), (3, 45.9), (4, 17.6), (5, 0.3),
        ],
    ],
},

Some markdown like language that would be parsed and turned into the above format.
For actual writing.

```md
$prop language en
$nav ""
  $nav "top level"
    - [home](/home)
    - [about](/about)
    - [now](/now)
    - [blog](/blog/index)
  $nav "other articles"
    - [I like cheese](cheese)
    - [Sosig is happiness](sosig)

# very important

One must see this image.

![very important image](image.png)

Also this one.

![another important image](website.com/image.jpg)

For further questions see [questions](##questions)

## questions

Why is this important?
Because it is.
For even further questions email me at <email@address.com>.

$footer

Copyright(C) some dude
```