{"_id":"56b79f827ced7f17003ab198","githubsync":"","__v":2,"project":"56b79ef9a6c10c0d00a2d67d","version":{"_id":"56b79f817ced7f17003ab196","__v":1,"project":"56b79ef9a6c10c0d00a2d67d","createdAt":"2016-02-07T19:48:17.460Z","releaseDate":"2016-02-07T19:48:17.460Z","categories":["56b79f827ced7f17003ab197"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"2.0.0","version":"2.0"},"user":"56b534d0168b5c1700c159a7","category":{"_id":"56b79f827ced7f17003ab197","pages":["56b79f827ced7f17003ab198","56b7a33f6c2a240d0094ae96","56b7a50cd22adc0d0053f4bf","56b7a55deb783a0d0078950f"],"project":"56b79ef9a6c10c0d00a2d67d","version":"56b79f817ced7f17003ab196","__v":4,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-02-07T19:46:02.504Z","from_sync":false,"order":0,"slug":"documentation","title":"Documentation"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-02-07T19:46:04.494Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"Kurenai can be used to parse documents of varying formats that have embedded metadata.\n\nLet's start by taking a look at a Kurenai document.\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"<metadata exists here>\\n======================\\n<content exists here>\",\n      \"language\": \"text\"\n    }\n  ]\n}\n[/block]\nKurenai documents have both a metadata and content section, separated by three or more `=` equals signs. Both the metadata and the content can support a variety of formats. Let's try another example.\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"{\\n  \\\"title\\\": \\\"My title here.\\\"\\n  \\\"date\\\":  \\\"12-12-1984\\\"\\n}\\n===========================\\n# Hi There\\n\\nHow are you doing?\",\n      \"language\": \"text\"\n    }\n  ]\n}\n[/block]\nHere, we have our metadata defined using [JSON](http://www.json.org/), and our content written in [Markdown](https://daringfireball.net/projects/markdown/) format.\n\nWe'll learn how to parse documents in the next section.","excerpt":"","slug":"getting-started","type":"basic","title":"Introduction"}
Kurenai can be used to parse documents of varying formats that have embedded metadata. Let's start by taking a look at a Kurenai document. [block:code] { "codes": [ { "code": "<metadata exists here>\n======================\n<content exists here>", "language": "text" } ] } [/block] Kurenai documents have both a metadata and content section, separated by three or more `=` equals signs. Both the metadata and the content can support a variety of formats. Let's try another example. [block:code] { "codes": [ { "code": "{\n \"title\": \"My title here.\"\n \"date\": \"12-12-1984\"\n}\n===========================\n# Hi There\n\nHow are you doing?", "language": "text" } ] } [/block] Here, we have our metadata defined using [JSON](http://www.json.org/), and our content written in [Markdown](https://daringfireball.net/projects/markdown/) format. We'll learn how to parse documents in the next section.