<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Theo Bertol</title>
    <description>The latest articles on Forem by Theo Bertol (@abeelha).</description>
    <link>https://forem.com/abeelha</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3702634%2Fbaa41bb4-ad3d-4729-969c-4109c1830530.png</url>
      <title>Forem: Theo Bertol</title>
      <link>https://forem.com/abeelha</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/abeelha"/>
    <language>en</language>
    <item>
      <title>Turn your Obsidian Vault into a beautiful website with Flowershow!</title>
      <dc:creator>Theo Bertol</dc:creator>
      <pubDate>Fri, 06 Feb 2026 14:11:01 +0000</pubDate>
      <link>https://forem.com/flowershow/turn-your-obsidian-vault-into-a-beautiful-website-with-flowershow-14ee</link>
      <guid>https://forem.com/flowershow/turn-your-obsidian-vault-into-a-beautiful-website-with-flowershow-14ee</guid>
      <description>&lt;p&gt;Hey 👋&lt;/p&gt;

&lt;p&gt;If you use &lt;strong&gt;Obsidian&lt;/strong&gt; and have ever wanted to publish your notes as a website, we’ve built something that makes this easy.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Flowershow&lt;/strong&gt; lets you turn an Obsidian vault into a fast, clean website — perfect for blogs, notes, or digital gardens. And to make publishing simpler, we built an &lt;strong&gt;Obsidian plugin&lt;/strong&gt; that connects your vault directly to Flowershow.&lt;/p&gt;

&lt;h3&gt;
  
  
  Publish your vault to the web — directly from Obsidian
&lt;/h3&gt;

&lt;p&gt;With the Flowershow Obsidian plugin, you can publish your notes without setting up repositories or dealing with complex workflows.&lt;/p&gt;

&lt;p&gt;The idea is simple:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Install the plugin&lt;/li&gt;
&lt;li&gt;Connect it to Flowershow&lt;/li&gt;
&lt;li&gt;Click &lt;strong&gt;Publish&lt;/strong&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Your notes are uploaded, built, and published as a website — straight from Obsidian.&lt;/p&gt;

&lt;p&gt;No Git required.&lt;br&gt;
No command line.&lt;br&gt;
Just write, then publish.&lt;/p&gt;

&lt;p&gt;If that sounds useful, you can learn more here:&lt;br&gt;
👉 &lt;a href="https://flowershow.app/blog/announcing-obsidian-plugin-4" rel="noopener noreferrer"&gt;https://flowershow.app/blog/announcing-obsidian-plugin-4&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We’d love to hear what you think 🌸&lt;/p&gt;

</description>
      <category>obsidian</category>
      <category>markdown</category>
      <category>opensource</category>
      <category>blogging</category>
    </item>
    <item>
      <title>Flowershow now supports HTML publishing!</title>
      <dc:creator>Theo Bertol</dc:creator>
      <pubDate>Thu, 29 Jan 2026 15:45:36 +0000</pubDate>
      <link>https://forem.com/flowershow/flowershow-now-supports-html-publishing-27mn</link>
      <guid>https://forem.com/flowershow/flowershow-now-supports-html-publishing-27mn</guid>
      <description>&lt;h1&gt;
  
  
  Flowershow now supports raw HTML publishing! 🚀
&lt;/h1&gt;

&lt;p&gt;Sometimes converting to Markdown just feels wrong—whether it’s a hand-coded portfolio, a data dashboard, or a custom landing page. You want the file exactly as it is.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Old Way:&lt;/strong&gt; Piling HTML into Markdown blocks, fighting &lt;code&gt;layout: plain&lt;/code&gt; frontmatter, and hoping the parser didn't break your CSS. It was brittle and frustrating.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The New Way:&lt;/strong&gt; Drop your &lt;code&gt;.html&lt;/code&gt; file into your content folder and publish.&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;flowershow publish index.html
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;No configuration needed.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No formatting errors.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mix-and-match:&lt;/strong&gt; Keep your docs in Markdown, but use raw HTML for custom landing pages or HTML reports&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;It just works.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Check out the full announcement:&lt;a href="https://flowershow.app/blog/announcing-html-support" rel="noopener noreferrer"&gt;https://flowershow.app/blog/announcing-html-support&lt;/a&gt;&lt;/p&gt;

</description>
      <category>indiedev</category>
      <category>html</category>
      <category>publishing</category>
      <category>coding</category>
    </item>
    <item>
      <title>Turn your Obsidian vault into dynamic galleries with Obsidian Bases</title>
      <dc:creator>Theo Bertol</dc:creator>
      <pubDate>Mon, 26 Jan 2026 17:26:08 +0000</pubDate>
      <link>https://forem.com/flowershow/turn-your-obsidian-vault-into-dynamic-galleries-with-obsidian-bases-3ofj</link>
      <guid>https://forem.com/flowershow/turn-your-obsidian-vault-into-dynamic-galleries-with-obsidian-bases-3ofj</guid>
      <description>&lt;p&gt;If you use Obsidian, you probably have "collections" – a folder of books you've read, a directory of project notes, or a list of recipes.&lt;/p&gt;

&lt;p&gt;Usually, these notes have metadata (frontmatter) — covers, ratings, dates, tags.&lt;/p&gt;

&lt;p&gt;You often want to list them in a nice way, displaying those fields (like a gallery of book covers with ratings), instead of just a text list.&lt;/p&gt;

&lt;p&gt;But automatically generating these views on a static site is hard. You often end up manually maintaining a brittle Markdown list (&lt;code&gt;- [[Book A]]&lt;/code&gt;, &lt;code&gt;- [[Book B]]&lt;/code&gt;). It’s tedious, and it breaks the moment you add a file but forget to update the index.&lt;/p&gt;

&lt;p&gt;We added &lt;strong&gt;Obsidian Bases&lt;/strong&gt; support to Flowershow to fix this.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;filters:
  file.folder == "books"
views:
  - type: cards
    image: cover_image
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Flowershow takes that, scans your folder, and renders a beautiful, filterable grid of cards.&lt;br&gt;
It lets you define dynamic views — like Cards or Tables — directly in your Markdown.&lt;/p&gt;

&lt;p&gt;Instead of writing a list, you write a query:&lt;br&gt;
&lt;strong&gt;Check out our Announcement Blog here:&lt;/strong&gt; &lt;a href="https://flowershow.app/blog/announcing-obsidian-bases-beta" rel="noopener noreferrer"&gt;https://flowershow.app/blog/announcing-obsidian-bases-beta&lt;/a&gt;&lt;/p&gt;

</description>
      <category>markdown</category>
      <category>obsidian</category>
      <category>publishing</category>
      <category>indiedev</category>
    </item>
    <item>
      <title>I wanted to publish one Markdown file, not start a project</title>
      <dc:creator>Theo Bertol</dc:creator>
      <pubDate>Wed, 21 Jan 2026 22:46:58 +0000</pubDate>
      <link>https://forem.com/flowershow/i-wanted-to-publish-one-markdown-file-not-start-a-project-18o2</link>
      <guid>https://forem.com/flowershow/i-wanted-to-publish-one-markdown-file-not-start-a-project-18o2</guid>
      <description>&lt;p&gt;Most publishing tools assume you’re building something permanent.&lt;/p&gt;

&lt;p&gt;But a lot of writing doesn’t look like that.&lt;/p&gt;

&lt;p&gt;Sometimes it’s a single Markdown file sitting on your machine. You’ve finished writing, and all you want is a link you can share.&lt;/p&gt;

&lt;p&gt;We built a small &lt;strong&gt;CLI&lt;/strong&gt; for that moment.&lt;/p&gt;

&lt;p&gt;The &lt;em&gt;Flowershow CLI&lt;/em&gt; lets you publish directly from your terminal — without setting up a repo or clicking through a dashboard.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Quick start&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm i &lt;span class="nt"&gt;-g&lt;/span&gt; @flowershow/publish
publish auth login
publish ./my-folder
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Done!&lt;/strong&gt; You'll get a ready to share URL!&lt;/p&gt;

&lt;p&gt;If you make changes later:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;publish &lt;span class="nb"&gt;sync&lt;/span&gt; ./my-folder
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This doesn’t replace UI-based workflows. It’s for people who already live in their editor and terminal and want publishing to feel like part of the same flow.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;It’s currently in beta and requires Node.js.&lt;/em&gt;&lt;br&gt;
Docs cover the details, or you can explore via publish &lt;code&gt;--help&lt;/code&gt;.&lt;br&gt;
Docs here: &lt;a href="https://flowershow.app/docs/cli" rel="noopener noreferrer"&gt;https://flowershow.app/docs/cli&lt;/a&gt;&lt;br&gt;
Blog here: &lt;a href="https://flowershow.app/blog/announcing-flowershow-cli" rel="noopener noreferrer"&gt;https://flowershow.app/blog/announcing-flowershow-cli&lt;/a&gt;&lt;/p&gt;

</description>
      <category>markdown</category>
      <category>indiedev</category>
      <category>publishing</category>
      <category>cli</category>
    </item>
    <item>
      <title>I wanted to publish one Markdown file, not start a project</title>
      <dc:creator>Theo Bertol</dc:creator>
      <pubDate>Wed, 21 Jan 2026 14:36:23 +0000</pubDate>
      <link>https://forem.com/abeelha/i-wanted-to-publish-one-markdown-file-not-start-a-project-2i5e</link>
      <guid>https://forem.com/abeelha/i-wanted-to-publish-one-markdown-file-not-start-a-project-2i5e</guid>
      <description>&lt;p&gt;Most publishing tools assume you’re building something permanent.&lt;/p&gt;

&lt;p&gt;But a lot of writing doesn’t look like that.&lt;/p&gt;

&lt;p&gt;Sometimes it’s a single Markdown file sitting on your machine. You’ve finished writing, and all you want is a link you can share.&lt;/p&gt;

&lt;p&gt;We built a small &lt;strong&gt;CLI&lt;/strong&gt; for that moment.&lt;/p&gt;

&lt;p&gt;The &lt;em&gt;Flowershow CLI&lt;/em&gt; lets you publish directly from your terminal — without setting up a repo or clicking through a dashboard.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Quick start&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm i &lt;span class="nt"&gt;-g&lt;/span&gt; @flowershow/publish
publish auth login
publish ./my-folder
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Done!&lt;/strong&gt; You'll get a ready to share URL!&lt;/p&gt;

&lt;p&gt;If you make changes later:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;publish &lt;span class="nb"&gt;sync&lt;/span&gt; ./my-folder
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This doesn’t replace UI-based workflows. It’s for people who already live in their editor and terminal and want publishing to feel like part of the same flow.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;It’s currently in beta and requires Node.js.&lt;/em&gt;&lt;br&gt;
Docs cover the details, or you can explore via publish &lt;code&gt;--help&lt;/code&gt;.&lt;br&gt;
Docs here: &lt;a href="https://flowershow.app/docs/cli" rel="noopener noreferrer"&gt;https://flowershow.app/docs/cli&lt;/a&gt;&lt;br&gt;
Blog here: &lt;a href="https://flowershow.app/blog/announcing-flowershow-cli" rel="noopener noreferrer"&gt;https://flowershow.app/blog/announcing-flowershow-cli&lt;/a&gt;&lt;/p&gt;

</description>
      <category>indiedev</category>
      <category>markdown</category>
      <category>publishing</category>
      <category>blogging</category>
    </item>
  </channel>
</rss>
