((p "A zettel consists of two parts: the metadata and the zettel content." " " "Metadata gives some information mostly about the zettel content, how it should be interpreted, how it is sorted within Zettelstore." " " "The zettel content is, well, the actual content." " " "In many cases, the content is in plain text form." " " "Plain text is long-lasting." " " "However, content in binary format is also possible.") (p "Metadata has to conform to a " (a (@ (href . "00001006010000")) "special syntax") "." " " "It is effectively a collection of key/value pairs." " " "Some keys have a " (a (@ (href . "00001006020000")) "special meaning") " and most of the predefined keys need values of a specific " (a (@ (href . "00001006030000")) "type") ".") (p "Each zettel is given a unique " (a (@ (href . "00001006050000")) "identifier") "." " " "To some degree, the zettel identifier is part of the metadata..") (p "The zettel content is your valuable content." " " "Zettelstore contains some predefined parsers that interpret the zettel content to the syntax of the zettel." " " "This includes markup languages, like " (a (@ (href . "00001007000000")) "Zettelmarkup") " and " (a (@ (href . "00001008010500")) "CommonMark") "." " " "Other text formats are also supported, like CSS and HTML templates." " " "Plain text content is always Unicode, encoded as UTF-8." " " "Other character encodings are not supported and will never be" (sup (@ (id . "fnref:1")) (a (@ (class . "zs-noteref") (href . "#fn:1") (role . "doc-noteref")) "1")) "." " " "There is support for a graphical format with a text representation: SVG." " " "And there is support for some binary image formats, like GIF, PNG, and JPEG.") (h2 (@ (id . "plain-parsed-and-evaluated-zettel")) "Plain, parsed, and evaluated zettel") (p "Zettelstore may present your zettel in various forms, typically retrieved with the " (a (@ (href . "00001012920000")) "endpoint") " " (kbd "/z/{ID}") "." " " "One way is to present the zettel as it was read by Zettelstore." " " "This is called " (@L (@H "“") (a (@ (href . "00001012053300")) "plain zettel") (@H "”")) ".") (p "The second way is to present the zettel as it was recognized by Zettelstore." " " "This is called " (@L (@H "“") (a (@ (href . "00001012053600")) "parsed zettel") (@H "”")) ", also retrieved with the " (a (@ (href . "00001012920000")) "endpoint") " " (kbd "/z/{ID}") ", but with the additional query parameter " (kbd "parseonly") "." " " "Such a zettel was read and analyzed." " " "It can be presented in various " (a (@ (href . "00001012920500")) "encodings") "." (sup (@ (id . "fnref:2")) (a (@ (class . "zs-noteref") (href . "#fn:2") (role . "doc-noteref")) "2"))) (p "However, a zettel such as this one you are currently reading, is a " (@L (@H "“") (a (@ (href . "00001012053500")) "evaluated zettel") (@H "”")) ", also retrieved with the " (a (@ (href . "00001012920000")) "endpoint") " " (kbd "/z/{ID}") " and specifying an encoding." " " "The biggest difference to a parsed zettel is the inclusion of " (a (@ (href . "00001007031100")) "block transclusions") " or " (a (@ (href . "00001007040324")) "inline transclusions") " for an evaluated zettel." " " "It can also be presented in various encoding, including the " (@L (@H "“") "zmk" (@H "”")) " encoding." " " "Evaluations also applies to metadata of a zettel, if appropriate.") (p "Please note, that searching for content is based on parsed zettel." " " "Transcluded content will only be found in transcluded zettel, but not in the zettel that transcluded the content." " " "However, you will easily pick up that zettel by follow the " (a (@ (href . "00001006020000#backward")) "backward") " metadata key of the transcluded zettel."))