Built site for gh-pages

Author: timothypratley

.nojekyll

@@ -1 +1 @@
-f3ae3f74
+d1eb232d

about.html

@@ -304,23 +304,15 @@
             <ul class="navbar-nav navbar-nav-scroll ms-auto">
   <li class="nav-item">
     <a class="nav-link" href="./posts.html"> 
-<span class="menu-text">Blog</span></a>
+<span class="menu-text">Posts</span></a>
   </li>  
   <li class="nav-item">
     <a class="nav-link" href="./ideas.html"> 
 <span class="menu-text">Ideas</span></a>
   </li>  
   <li class="nav-item">
-    <a class="nav-link" href="./talks.html"> 
-<span class="menu-text">Talks</span></a>
-  </li>  
-  <li class="nav-item">
-    <a class="nav-link" href="./tutorials.html"> 
-<span class="menu-text">Tutorials</span></a>
-  </li>  
-  <li class="nav-item">
-    <a class="nav-link" href="./pages.html"> 
-<span class="menu-text">Pages</span></a>
+    <a class="nav-link" href="./libs.html"> 
+<span class="menu-text">Libraries and Tools</span></a>
   </li>  
   <li class="nav-item">
     <a class="nav-link active" href="./about.html" aria-current="page"> 
@@ -399,7 +391,7 @@ <h3 class="anchored" data-anchor-id="write-notebooks">Write notebooks</h3>
 </section>
 <section id="preview-the-full-website" class="level3">
 <h3 class="anchored" data-anchor-id="preview-the-full-website">Preview the full website</h3>
-<div class="sourceCode" id="cb1"><pre class="sourceCode sh code-with-copy"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" aria-hidden="true" tabindex="-1"></a><span class="ex">clojure</span> <span class="at">-M:m</span></span></code><button title="Copy to Clipboard" class="code-copy-button"><i class="bi"></i></button></pre></div>
+<div class="sourceCode" id="cb1"><pre class="sourceCode sh code-with-copy"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" aria-hidden="true" tabindex="-1"></a><span class="ex">clojure</span> <span class="at">-M:clay</span> <span class="at">-a</span> <span class="pp">[</span><span class="ss">:markdown</span><span class="pp">]</span></span></code><button title="Copy to Clipboard" class="code-copy-button"><i class="bi"></i></button></pre></div>
 <div class="sourceCode" id="cb2"><pre class="sourceCode sh code-with-copy"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" aria-hidden="true" tabindex="-1"></a><span class="ex">quarto</span> preview site</span></code><button title="Copy to Clipboard" class="code-copy-button"><i class="bi"></i></button></pre></div>
 </section>
 <section id="publish" class="level3">
@@ -412,6 +404,7 @@ <h2 class="anchored" data-anchor-id="rationale">Rationale</h2>
 <div style="text-align: center; font-family: 'Georgia', serif; font-size: 1.5rem; margin: 2rem 0; color: #2e7d32;">
 <p>Exploramus, Communicamus, Crescimus<br> <small style="font-size: 1rem; color: #555;">We explore, we share, we grow.</small></p>
 </div>
+<p>Civitas Clojure offers a hassle-free way to host and share your notebooks without the overhead of creating a new project each time. By providing a shared, well-organized platform, it lets you focus on your ideas and code while automatically publishing your work to GitHub Pages. This streamlines collaboration, increases visibility, and makes contributing simple and efficient—so you can spend less time on setup and more time creating.</p>
 <p>Learning technical subjects involves navigating complex webs of concepts. Currently, resources for learning Clojure exist as isolated articles, unconnected tutorials, or flat lists that do not capture how ideas relate to each other. This makes it difficult for learners to determine logical next steps or see how topics connect. Teachers and curriculum designers face similar challenges when trying to organize material in ways that reflect actual dependencies and alternatives.</p>
 <p>Civitas approaches this problem by implementing a structured knowledge base where resources are explicitly linked based on their conceptual relationships. The hexagonal grid interface provides a visual representation of these connections, allowing users to naturally discover related content. Each resource includes metadata to indicate prerequisites, alternatives, and deeper explorations.</p>
 <p>This structure serves several practical purposes. Learners can see multiple valid paths through the material. Teachers can construct guided sequences while maintaining visibility of adjacent concepts. The community can improve resources incrementally by adding or refining connections. The system is designed to grow organically as new relationships are identified and documented.</p>
@@ -428,8 +421,8 @@ <h2 class="anchored" data-anchor-id="design">Design</h2>
 <h3 class="anchored" data-anchor-id="file-system-organization">File system organization</h3>
 <table class="caption-top table">
 <colgroup>
-<col style="width: 25%">
-<col style="width: 74%">
+<col style="width: 18%">
+<col style="width: 81%">
 </colgroup>
 <thead>
 <tr class="header">
@@ -444,52 +437,35 @@ <h3 class="anchored" data-anchor-id="file-system-organization">File system organ
 </tr>
 <tr class="even">
 <td><code>content</code></td>
-<td>Notebooks (Clojure and Markdown), images, data files</td>
-</tr>
-<tr class="odd">
-<td><code>content/posts</code></td>
-<td>Time-anchored content (blog posts, announcements, analyses)</td>
-</tr>
-<tr class="even">
-<td><code>content/pages</code></td>
-<td>Timeless or evolving content related to this site</td>
+<td>Source root for notebooks (Clojure and Markdown), images, data files</td>
 </tr>
 <tr class="odd">
-<td><code>content/tutorials</code></td>
-<td>Learning materials (tutorials, workshops, guides)</td>
+<td><code>content/idea</code></td>
+<td>The <code>idea</code> namespace hosts explorations, concepts and insights</td>
 </tr>
 <tr class="even">
-<td><code>content/talks</code></td>
-<td>Presentation slides and related materials</td>
+<td><code>content/lib</code></td>
+<td>The <code>lib</code> namespace is tied to libraries, tools, and projects</td>
 </tr>
 <tr class="odd">
-<td><code>content/ideas</code></td>
-<td>Drafts, experiments, and work-in-progress content</td>
-</tr>
-<tr class="even">
 <td><code>site</code></td>
-<td>Quarto configuration for the website</td>
+<td>Temporary build target for the Quarto website</td>
 </tr>
 </tbody>
 </table>
-<p>Each of <code>posts</code>, <code>pages</code>, <code>tutorials</code>, <code>talks</code>, <code>ideas</code> is a source-root. These directories make it easier to distinguish blog posts from everything else.</p>
-<p>Namespace selection for notebooks follow standard Clojure namespace conventions to avoid conflicts.</p>
-<p>Library-related notebooks: Use the library’s namespace prefix (e.g., scicloj.clay.v2.guide.getting-started).</p>
-<p>Disambiguation: If a topic exists, qualify with additional context (e.g., scicloj.clay.v2.guide.getting-started.intellij).</p>
-<p>Dependent utils/modules: Nest under a parent namespace (e.g., …getting-started.index, …getting-started.utils).</p>
+<p>Shared images can go in <code>content/images</code>, but prefer images and data files as siblings to your namespace.</p>
+<p>The difference between a posts and a page is identified by the presence or absence of <code>date</code> metadata.</p>
+<p>Namespace selection for notebooks follow standard Clojure namespace conventions to avoid conflicts. Choose namespaces that fit with the content-first hierarchy. Files are grouped by what they’re about (not who wrote them or where they were presented). Author, date, tags and categories are included in metadata and will be used for grouping, filter of views.</p>
+<p>Disambiguation: If a topic exists, qualify with additional context.</p>
 <p>Civitas invokes <a href="https://github.com/scicloj/clay">Clay</a> to convert Clojure notebooks into Markdown files, placing them in the <code>site</code> directory. This <code>site</code> directory serves as a build folder for <a href="https://quarto.org/">Quarto</a>. Avoid adding files directly to <code>site</code>.</p>
 <p>Static assets (such as images or data files) should be placed in the <code>content</code> directory. During the build process, any files in the <code>content</code> directory that are not Clojure files, are copied into the <code>site</code> directory. Quarto then builds the Markdown in <code>site</code> into HTML, which is placed in <code>_site</code> before deploying it to GitHub Pages.</p>
 <p>During development, Clay serves HTML from the <code>temp</code> directory, which is git ignored.</p>
 <p>Goal: Align with Clojure’s code organization while allowing organic, practical growth.</p>
 </section>
 <section id="topic-organization" class="level3">
 <h3 class="anchored" data-anchor-id="topic-organization">Topic organization</h3>
-<p>Notebooks are tagged with a primary topic (first in list) and optional additional topics.</p>
-<p>Fixed top-level topics: <code>:community</code>, <code>:core</code>, <code>:data</code>, <code>:system</code>, <code>:tooling</code>, <code>:web</code>.</p>
-<p>Subtopics: Semi-open (e.g., :web/frontend implies :web). Expect these to evolve.</p>
-<p>Topics are one tagging method; others may emerge.</p>
-<p>Tags want to be free: https://gwern.net/doc/philosophy/ontology/2005-04-shirky-ontologyisoverratedcategorieslinksandtags.html</p>
-<p>But also we can help curate the content with a good set of top-level topics.</p>
+<p>Follow the Quarto convention of categories, tags, and keywords. Fixed categories; <code>community</code>, <code>clojure</code>, <code>data</code>, <code>system</code>, <code>tooling</code>, <code>web</code>. Tags; flexible, open-ended for finer-grained labeling (e.g.&nbsp;<code>frontend</code>, <code>reagent</code>). Keywords; for SEO or search indexing; typically fewer and focused on discoverability.</p>
+<p>Tags and metadata are the preferred organization principle: <a href="https://gwern.net/doc/philosophy/ontology/2005-04-shirky-ontologyisoverratedcategorieslinksandtags.html">Categories, Links, and Tags</a></p>
 <p>Goal: Constellations, not cabinets.</p>
 </section>
 <section id="dependency-management" class="level3">