Looks cool (I'm a big fan of Typst), but I do question the value of moving the data to yaml, rather than just building a set of Typst functions and styles (see example below).<p>To me, it's one of those things people often do because it _feels_ nice, but when you really think about it the benefits are often very small (and the costs are quite high). The most obvious benefit is that the yaml data can be parsed by other programs, but is anyone really going to do that?<p>For an example of what I mean, is [1] (plus all the supporting code) really a better DX than [2] (which is also simpler to implement and much easier to debug and modify)?<p>[1]<p><pre><code> work:
# Can't use markup or code in most of these fields, even if I wanted to.
- organization: X Company
position: Senior Developer
url: https://example.com
location: Remote / New York, New York
startDate: 2021-08-01
endDate: "present"
highlights:
- "Any markup I use here needs to be `eval`ed, and I don't get syntax highlighting etc."
</code></pre>
[2]<p><pre><code> == Work Experience
#workinfo(
organization: "X Company",
position: "Senior Developer",
url: "https://example.com",
location: "Remote / New York, New York",
startDate: "2021-08-01",
endDate: "present",
highlights: (
[I don't need to use `eval` any more],
[etc...]),
)
#workinfo(etc...)</code></pre>