<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Git on Werk Space</title>
    <link>/tags/git/</link>
    <description>Recent content in Git on Werk Space</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 06 Aug 2026 17:39:13 +0000</lastBuildDate>
    <atom:link href="/tags/git/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Git Workflow</title>
      <link>/docs/document-system/git-workflow/</link>
      <pubDate>Thu, 06 Aug 2026 00:00:00 +0000</pubDate>
      <guid>/docs/document-system/git-workflow/</guid>
      <description>&lt;h2 id=&#34;the-repository&#34;&gt;The repository&lt;/h2&gt;&#xA;&lt;p&gt;The entire site lives in one public GitHub repository, &lt;a href=&#34;https://github.com/gary-dalton/public-documents&#34;&gt;gary-dalton/public-documents&lt;/a&gt;. Git provides three things here: versioning for every document, transfer between working machines and the host, and the trigger for deployment. Every push to &lt;code&gt;master&lt;/code&gt; causes a fresh build of the live site (see &lt;a href=&#34;/docs/document-system/hosting/&#34;&gt;Hosting&lt;/a&gt;).&lt;/p&gt;&#xA;&lt;p&gt;If you need to install git first, see &lt;a href=&#34;&#34;&gt;the development environment instructions&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-working-cycle&#34;&gt;The working cycle&lt;/h2&gt;&#xA;&lt;p&gt;Routine work is a short loop:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Edit content in &lt;code&gt;content/en/&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Preview locally with drafts visible:&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;hugo server -D --watch --poll 700ms --bind 0.0.0.0 --liveReloadPort&lt;span style=&#34;color:#ce5c00;font-weight:bold&#34;&gt;=&lt;/span&gt;&lt;span style=&#34;color:#0000cf;font-weight:bold&#34;&gt;1313&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;&#xA;&lt;li&gt;Commit with a message that says what changed and why.&lt;/li&gt;&#xA;&lt;li&gt;Push to &lt;code&gt;master&lt;/code&gt;. The host then builds and deploys automatically.&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;Publication is controlled entirely by the front matter: a page with &lt;code&gt;draft: true&lt;/code&gt; renders in the local preview (because of the &lt;code&gt;-D&lt;/code&gt; flag) but is excluded from the production build. Flipping &lt;code&gt;draft: false&lt;/code&gt; and pushing is the &lt;strong&gt;act of publishing&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Research and Publishing Workflow</title>
      <link>/docs/document-system/publishing-workflow/</link>
      <pubDate>Thu, 06 Aug 2026 00:00:00 +0000</pubDate>
      <guid>/docs/document-system/publishing-workflow/</guid>
      <description>&lt;h2 id=&#34;two-paths-to-publication&#34;&gt;Two paths to publication&lt;/h2&gt;&#xA;&lt;p&gt;Most articles are written directly on this site. A page starts as &lt;code&gt;draft: true&lt;/code&gt; in the content tree, gets written and revised in place, and publishes when the flag flips. A second path exists for complex or in-depth work: a private research repository holds the piece until it is ready, and it arrives here only at publication. Which path a piece takes depends on one question: does it matter if someone reads the work before it is finished?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
