In the Pandoc Plugin settings, add — citeproc to the ‘Extra Pandoc arguments’ setting. This will be what takes the markdown citations and converts them to in-text citations in the conversion process. It also inserts a full reference list on the end of your document automatically, all completely formatted. To get this to work, you have to specify the location of the .bib file on your system by adding the path, in quotations, to a ‘bibliography’ YAML property.

Python — Json documents double as valid Python literals with minimal adaptation, and Python supports trailing commas and comments. It has variables and functions, powerful string interpolation, and json.dump built in. A self-contained Python file that prints json to stdout goes a long way!

always quote all strings. (Indeed, you can tell that somebody is an experienced yaml engineer when they defensively quote all the strings.) We can choose to always use true and false rather than yes and no, and generally stay away from the arcane features.

I think the main reason that yaml is so prevalent despite its pitfalls, is that for a long time it was the only viable configuration format.

Diet YAML is a light weight version of YAML that removes much of the complex aspects of the mainline YAML specification.

JSON is a similar, perhaps even more popular, format (and almost[!] a subset of YAML 1.2).

Yes, using custom tags. Example in Python, making the !join tag join strings in an array:

To get a sorted list of all glossary items you could use YAML in the front matter of each glossary term then use the dataview plugin and sort ascending.

An extension to python markdown that takes metadata embedded as YAML in a page of markdown and render it as JSON-LD in the HTML created by MkDocs.

Extension: yaml_metadata_block

Using |- preserves newlines within the command and does not append a newline at the end of the command string. Beforehand I was using > which replaces newlines in the command string with spaces.

Not merge the values of the keys.

GitLab will perform a reverse deep merge based on the keys

It’s an alternative to using YAML anchors and is a little more flexible and readable

A notebook, at a very basic level, is just a bunch of JSON that references blocks of code and the order in which they should be executed.But notebooks prioritize presentation and interactivity at the expense of reproducibility. YAML is the other side of that coin, ignoring presentation in favor of simplicity and reproducibility—making it much better for production.

There is no hidden state or arbitrary execution order in a YAML file, and any changes you make to it can easily be tracked by Git

I wrote a plugin for Vim that lets you easily toggle a YML file between nested format: xx.yml1 2 3 4 en: baz: "baize" foo: bar: "baare" and a flat format: xx.yml1 2 en.baz: "baize" en.foo.bar: "baare" This is really useful, as the flat format is easier to search and edit.

Note: When mapping ports in the HOST:CONTAINER format, you may experience erroneous results when using a container port lower than 60, because YAML will parse numbers in the format xx:yy as sexagesimal (base 60). For this reason, we recommend always explicitly specifying your port mappings as strings.