<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>site/src/content/docs/reference/example.md - fork/glide @ v0.1.0</title>
<meta name="description" content="site/src/content/docs/reference/example.md in fork/glide at v0.1.0.">
<meta property="og:title" content="site/src/content/docs/reference/example.md - fork/glide @ v0.1.0">
<meta property="og:description" content="site/src/content/docs/reference/example.md in fork/glide at v0.1.0.">
<meta property="og:type" content="website">
<meta property="og:site_name" content="git.julia.blue">
<link rel="stylesheet" href="/css/style.css?v=62">
<script type="module" src="/js/main.js?v=62"></script>
</head>
<body>
<main data-ref="v0.1.0" data-tip="2bb8ae6eee01e61b0e3ad22dbf93455c15478fbe">
<noscript>
  <div class="callout">
    <p>
      hey! this is a static git repo viewer. commit diffs, file history,
      older commits and other revisions won't load without javascript.
    </p>
    <p>
      you are still able to view source files on branch/tag tips,
      but the experience is degraded.
    </p>
  </div>
</noscript>
<header class="repo"><div>
<h1>fork/glide</h1>
</div>
<pre class="clone">git clone https://git.julia.blue/fork/glide</pre>
</header>
<p class="snapshot-commit"><span class="commit-author">Tyler Mandry</span><span class="commit-message" data-commit="ed0a39a103df306371d35605c5fb4a64aa2bddd7">Merge pull request #15 from glide-wm/site</span><span class="snapshot-sha sha" data-commit="ed0a39a103df306371d35605c5fb4a64aa2bddd7">ed0a39a</span><time datetime="2025-07-13T20:51:50-07:00" title="2025-07-13 20:51:50 -0700">2025-07-13</time></p>
<header class="topbar"><details class="switcher"><summary>v0.1.0</summary><div class="menu"><strong>branches</strong><a href="/fork/glide/ref/main/">main</a><strong>tags</strong><a class="current" href="/fork/glide/ref/v0.1.0/">v0.1.0</a><a href="/fork/glide/ref/v0.1.1/">v0.1.1</a><a class="all" href="/fork/glide/refs">all refs →</a></div></details><nav class="crumbs"><a href="/fork/glide/">glide</a> / <a href="/fork/glide/ref/v0.1.0/tree/site/">site</a> / <a href="/fork/glide/ref/v0.1.0/tree/site/src/">src</a> / <a href="/fork/glide/ref/v0.1.0/tree/site/src/content/">content</a> / <a href="/fork/glide/ref/v0.1.0/tree/site/src/content/docs/">docs</a> / <a href="/fork/glide/ref/v0.1.0/tree/site/src/content/docs/reference/">reference</a> / <span class="cur">example.md</span></nav>
<span class="view-stats"><span>422 B</span><span>11 lines</span></span><span class="actions"><a class="raw" href="/fork/glide/raw/0224f096ce6c7118e9b3843149f753f6148e636b/site/src/content/docs/reference/example.md">raw</a></span></header>
<div class="markdown-view"><input type="radio" name="markdown-view" id="markdown-rendered" checked><label for="markdown-rendered">rendered</label><input type="radio" name="markdown-view" id="markdown-code"><label for="markdown-code">code</label><section class="readme rendered"><hr />
<h2>title: Example Reference
description: A reference page in my new Starlight docs site.</h2>
<p>Reference pages are ideal for outlining how things work in terse and clear terms.
Less concerned with telling a story or addressing a specific use case, they should give a comprehensive outline of what you're documenting.</p>
<h2>Further reading</h2>
<ul>
<li>Read <a href="https://diataxis.fr/reference/">about reference</a> in the Diátaxis framework</li>
</ul>
</section><div class="code-panel"><pre class="code src language-markdown"><span class="code-line"><a class="ln" id="L1" href="#L1">1</a><span class="code-text"><a-p>---</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L2" href="#L2">2</a><span class="code-text"><a-pr>title</a-pr><a-p>:</a-p> <a-s>Example Reference</a-s></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L3" href="#L3">3</a><span class="code-text"><a-pr>description</a-pr><a-p>:</a-p> <a-s>A reference page in my new Starlight docs site.</a-s></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L4" href="#L4">4</a><span class="code-text"><a-p>---</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L5" href="#L5">5</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L6" href="#L6">6</a><span class="code-text">Reference pages are ideal for outlining how things work in terse and clear terms.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L7" href="#L7">7</a><span class="code-text">Less concerned with telling a story or addressing a specific use case, they should give a comprehensive outline of what you&#39;re documenting.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L8" href="#L8">8</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L9" href="#L9">9</a><span class="code-text"><a-p>##</a-p> <a-tt>Further reading</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L10" href="#L10">10</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L11" href="#L11">11</a><span class="code-text"><a-p>- </a-p>Read [about reference](https://diataxis.fr/reference/) in the Diátaxis framework</span></span></pre></div></div>
</main>
</body>
</html>
