Good point. I guess what I’m aiming for in terms of “visual metadata” (As opposed to hidden metadata like with
| example ), is a commonmark document that can be read as easily if formatted correctly to json. E.g. https://jsonresume.org/ but which can look as good as it can be easily parsed.
E.g. Formatting this txt resume to be easily read as a json data structure. resume example in markdown
Approach for visual metadata
hmmmm… noticed that people type list often like this
# header title (secondary descriptor): description Loose Key (secondary descriptor): description List name: * item name1 (secondary descriptor): description * item name2 (secondary descriptor): description * item name3 (secondary descriptor): description
# About Animals (Year:1986) : You know you want to know more! Written By (Author): Greg Publisher: Burkank Animals: * bob (cat) : barfs furballs * george (dog) : very lazy * alex (cat) : likes birds
The common thing is that it uses “
Key(2nd value): Value” structure like YAML,
Key(2nd value) - Value” used for this example.
Perhaps we can use that?
Extra example of textual resumes: http://media.wiley.com/Lux/assets/03/126203.08037X%20fg0401.pdf