<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0"
  xmlns:atom="http://www.w3.org/2005/Atom"
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Projects - Pocket Hugo</title>
    <link>https://theme.leftn.com/categories/projects/</link>
    <description>Projects</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 20 Apr 2026 02:51:39 &#43;0000</lastBuildDate>
    <atom:link href="https://theme.leftn.com/categories/projects/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pocket Hugo</title>
      <link>https://theme.leftn.com/projects/pocket-hugo/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 &#43;0000</pubDate>
      <guid>https://theme.leftn.com/projects/pocket-hugo/</guid>
      <description>A browser-first writing and publishing workflow for Hugo.</description>
      <content:encoded><![CDATA[<div class="shortcode-note shortcode-note--info"><div class="shortcode-note__title">Project focus</div><div class="shortcode-note__body">
    Pocket Hugo is a browser-first writing and publishing tool for Hugo. It tries to bring drafting, organizing, image handling, and publishing into a lighter workflow that feels closer to actual writing.
  </div>
</div>

<p><span class="shortcode-badge shortcode-badge--default">Browser-first</span>
 <span class="shortcode-badge shortcode-badge--info">Writing workflow</span>
 <span class="shortcode-badge shortcode-badge--info">Hugo</span>
</p>
<p><a class="shortcode-button shortcode-button--primary" href="https://github.com/h2dcc/pocket-hugo">View on GitHub</a>

<a class="shortcode-button shortcode-button--ghost" href="https://pockethugo.cc/">Open Homepage</a>
</p>
<h2 id="what-this-project-is-trying-to-solve">What this project is trying to solve</h2>
<p>Pocket Hugo is less about building one more editor and more about reducing friction across the whole writing flow. The goal is to make Hugo feel closer to &ldquo;open the browser and start writing&rdquo; instead of depending on a heavy local setup and a scattered publishing process.</p>
<h2 id="best-fit">Best fit</h2>
<div class="shortcode-columns">
  
<div class="shortcode-columns__item shortcode-columns__item--1">
  <h3 id="better-for">Better for</h3>
<ul>
<li>writers who want to keep Hugo but simplify the workflow</li>
<li>people who need to manage drafts, assets, and publishing together</li>
<li>publishing setups that benefit from staying lightweight</li>
</ul>

</div>

<div class="shortcode-columns__item shortcode-columns__item--1">
  <h3 id="not-mainly-about">Not mainly about</h3>
<ul>
<li>full CMS dashboards</li>
<li>complex team collaboration systems</li>
<li>highly coupled editing platforms</li>
</ul>

</div>


</div>

<h2 id="project-rhythm">Project rhythm</h2>
<div class="shortcode-timeline">
  
<div class="shortcode-timeline__item">
  <div class="shortcode-timeline__rail"></div>
  <div class="shortcode-timeline__content">
    <div class="shortcode-timeline__date">Step 1</div>
    <div class="shortcode-timeline__title">Write and organize</div>
    <div class="shortcode-timeline__body">Work directly with Hugo-style content, drafts, and related assets.</div>
  </div>
</div>

<div class="shortcode-timeline__item">
  <div class="shortcode-timeline__rail"></div>
  <div class="shortcode-timeline__content">
    <div class="shortcode-timeline__date">Step 2</div>
    <div class="shortcode-timeline__title">Handle images and publishing</div>
    <div class="shortcode-timeline__body">Bring image processing and publishing into a smoother browser workflow.</div>
  </div>
</div>

<div class="shortcode-timeline__item">
  <div class="shortcode-timeline__rail"></div>
  <div class="shortcode-timeline__content">
    <div class="shortcode-timeline__date">Step 3</div>
    <div class="shortcode-timeline__title">Maintain for the long run</div>
    <div class="shortcode-timeline__body">Keep personal publishing sustainable without making it heavier than necessary.</div>
  </div>
</div>


</div>

<h2 id="why-it-fits-this-demo">Why it fits this demo</h2>
<p>Pocket Hugo is a good example for this theme because it represents the writing side of the same publishing stack. One project focuses on creating and shipping content, while the other focuses on presentation and reading.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Pocket Hugo Theme</title>
      <link>https://theme.leftn.com/projects/pocket-hugo-theme/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 &#43;0000</pubDate>
      <guid>https://theme.leftn.com/projects/pocket-hugo-theme/</guid>
      <description>A Hugo theme for multilingual writing, cover-driven presentation, and long-form reading.</description>
      <content:encoded><![CDATA[<div class="shortcode-note shortcode-note--tip"><div class="shortcode-note__title">Theme direction</div><div class="shortcode-note__body">
    Pocket Hugo Theme is a Hugo theme designed for multilingual writing, long-form reading, and cover-driven presentation. Its priority is not feature overload, but rhythm, consistency, and maintainability over time.
  </div>
</div>

<p><span class="shortcode-badge shortcode-badge--default">Multilingual</span>
 <span class="shortcode-badge shortcode-badge--info">Long-form reading</span>
 <span class="shortcode-badge shortcode-badge--info">Cover-driven</span>
</p>
<a class="shortcode-button shortcode-button--primary" href="https://github.com/h2dcc/pocket-hugo-theme">View on GitHub</a>

<h2 id="what-the-theme-cares-about">What the theme cares about</h2>
<p>Many themes look fine when a site is small, but start to drift once the content grows: article pages and fixed pages feel unrelated, language switching becomes awkward, cover cards lose consistency, and mobile reading gets cramped. Pocket Hugo Theme tries to keep those details coherent.</p>
<h2 id="best-fit">Best fit</h2>
<div class="shortcode-columns">
  
<div class="shortcode-columns__item shortcode-columns__item--1">
  <h3 id="better-for">Better for</h3>
<ul>
<li>personal blogs and long-term writing sites</li>
<li>sites with bilingual or multilingual content</li>
<li>writers who care about list pages, covers, and reading order</li>
</ul>

</div>

<div class="shortcode-columns__item shortcode-columns__item--1">
  <h3 id="not-chasing">Not chasing</h3>
<ul>
<li>dashboard-like component aesthetics</li>
<li>flashy interaction for its own sake</li>
<li>visual tricks that hurt reading comfort</li>
</ul>

</div>


</div>

<h2 id="theme-rhythm">Theme rhythm</h2>
<div class="shortcode-timeline">
  
<div class="shortcode-timeline__item">
  <div class="shortcode-timeline__rail"></div>
  <div class="shortcode-timeline__content">
    <div class="shortcode-timeline__date">Layer 1</div>
    <div class="shortcode-timeline__title">Content structure</div>
    <div class="shortcode-timeline__body">Keep homepage, articles, archives, taxonomies, and fixed pages speaking the same language.</div>
  </div>
</div>

<div class="shortcode-timeline__item">
  <div class="shortcode-timeline__rail"></div>
  <div class="shortcode-timeline__content">
    <div class="shortcode-timeline__date">Layer 2</div>
    <div class="shortcode-timeline__title">Reading experience</div>
    <div class="shortcode-timeline__body">Focus on covers, typography, language switching, and long-form pacing.</div>
  </div>
</div>

<div class="shortcode-timeline__item">
  <div class="shortcode-timeline__rail"></div>
  <div class="shortcode-timeline__content">
    <div class="shortcode-timeline__date">Layer 3</div>
    <div class="shortcode-timeline__title">Long-term maintenance</div>
    <div class="shortcode-timeline__body">Keep configuration and behavior clear enough that the site stays usable as it grows.</div>
  </div>
</div>


</div>

<h2 id="why-it-fits-this-demo">Why it fits this demo</h2>
<p>This example shows the theme describing itself without turning into documentation-only copy. The page still reads like a project profile rather than a config reference.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
