/tags/documentation/ Recent content in Documentation on Werk Space Hugo en Thu, 06 Aug 2026 16:53:27 +0000 /docs/overview/ Mon, 01 Jan 0001 00:00:00 +0000 /docs/overview/ <p>Initially, these documents are just built and stored in chronological order. Later, they may be organized into categories or by tags.</p> /docs/document-system/ Wed, 08 Apr 2020 09:46:25 -0500 /docs/document-system/ <div class="pageinfo pageinfo-primary"> <p>This page describes the system as it runs today: dev container, vendored theme, Render builds. The manual procedures from earlier stages of the system are preserved in the <a href="https://github.com/gary-dalton/public-documents/blob/794746085746a076e4075b0674a2fdf53b1aa540/content/en/docs/Document%20system/_index.md">2023 revision of this page</a> on GitHub.</p> </div> <h2 id="overview">Overview</h2> <p>The first step in starting a document system is to evaluate and determine which system to use. Based on experience, I decided that my system needed:</p> <ul> <li>Documents written in markdown for simplicity, universality, and versioning.</li> <li>Documents organized in a tree fashion with options for categories and tagging.</li> <li>Standardized presentation formatting.</li> <li>Advanced formatting and presentation options.</li> <li>Easily searchable.</li> <li>Available from anywhere.</li> </ul> <p>In other words, I wanted a system that converted markdown documents to an organized and hyperlinked website.</p> /docs/ Mon, 01 Jan 0001 00:00:00 +0000 /docs/ <p>This section is a conglomeration of all the documentation I create. Most documents, I create in order to recall and share what I have done. Much of it is procedural, such as how I built my <a href="/docs/document-system/">Document system</a>. Document system, first discusses the need, then lists the packages used, and finally goes step by step on installation. One reason for this is so that I may repeat the exact same installation in the future.</p>