{"id":"33b7b70ae11b5a4d629432b115149006b8079b4565cc51a328079204544d252a","type":"Contented","path":"/others/limitations","modifiedDate":1686373756200,"sections":["Others"],"fields":{"title":"Known Limitations"},"html":"<nav class=\"toc\"><ol class=\"toc-level toc-level-1\"><li class=\"toc-item toc-item-h1\"><a class=\"toc-link toc-link-h1\" href=\"#known-limitations\">Known Limitations</a><ol class=\"toc-level toc-level-2\"><li class=\"toc-item toc-item-h2\"><a class=\"toc-link toc-link-h2\" href=\"#customization\">Customization</a></li></ol></li></ol></nav><h1 id=\"known-limitations\"><a aria-hidden=\"true\" tabindex=\"-1\" href=\"#known-limitations\"><span class=\"icon icon-link\"></span></a>Known Limitations</h1>\n<h2 id=\"customization\"><a aria-hidden=\"true\" tabindex=\"-1\" href=\"#customization\"><span class=\"icon icon-link\"></span></a>Customization</h2>\n<p>Since the purpose of Contented is to encourage authoring through a set of tools and workflows, the outcome has always\nbeen for engineers to produce more markdowns (_.md) or processed prose (<code>_.json</code>). The focus is never about building a\ncomplete documentation website.</p>\n<p>In fact, you should take the output(s) of <a href=\"../api#contented-build\"><code>contented build</code></a> that are published into npm; and pull them\ninto your main/official website for re-presentation (<code>npm i, import from</code>). Remember, the prose/content/narrative\ncreated is what's valuable here. Design can easily change, but your content stands the test of time.</p>","headings":[{"depth":1,"id":"known-limitations","title":"Known Limitations","children":[{"depth":2,"id":"customization","title":"Customization","children":[]}]}]}