The `card` setting in the example config.yml was used in the first iteration of the card UI.
The code was later changed to infer the fields that appear in the card, instead of having to configure them (see commit 2a2497072dd2c538735a92a1f6e93de6af7c796d).
The old card settings, however, were left in the example configuration file, which leads to confusion.
Switches back to custom frontmatter stringification
until support lands in preliminaries. This is necessary
because we use custom schemas for certain data types,
such as dates and times.
* Files based collections skeleton
* listing file based cards
* create new entry with collection
* moved lookupEntry to main backend
* Editing single page Collections file
* List widget basic implementation
* Adjustments for test-repo
* check if value exists before trying to iterate over
