1import{_ as o,c as e,a7 as a,o as s}from"./chunks/framework.Q1KJJagW.js";const m=JSON.parse('{"title":"How to build a documentation?","description":"","frontmatter":{},"headers":[],"relativePath":"bootcamp/docs.md","filePath":"bootcamp/docs.md","lastUpdated":1698126157000}'),i={name:"bootcamp/docs.md"};function n(d,t,r,c,p,l){return s(),e("div",null,t[0]||(t[0]=[a('<h1 id="how-to-build-a-documentation" tabindex="-1">How to build a documentation? <a class="header-anchor" href="#how-to-build-a-documentation" aria-label="Permalink to "How to build a documentation?"">â</a></h1><p>Building a documentation is simple, and Stacks helps you every step of the way.</p><p>The source of the documentation frontend lives in <code>./docs</code>. Under the hood, Stacks is powered by <a href="https://vitepress.vuejs.org/" target="_blank" rel="noreferrer">VitePress</a>, and, in short, the markdown files in <code>./docs</code> are compiled into a static website that is automatically served by the Stacks server.</p><p>Check out ./config/docs.ts for all the configuration options.</p><p>wip</p>',5)]))}const h=o(i,[["render",n]]);export{m as __pageData,h as default};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.