<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Home on Behlul Ozdemir</title>
    <link>https://www.behlulozdemir.com/</link>
    <description>Recent content in Home on Behlul Ozdemir</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 29 Mar 2026 08:03:43 +0300</lastBuildDate>
    <atom:link href="https://www.behlulozdemir.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Lets Start Writing</title>
      <link>https://www.behlulozdemir.com/posts/lets-start-writing/</link>
      <pubDate>Sun, 29 Mar 2026 08:03:43 +0300</pubDate>
      <guid>https://www.behlulozdemir.com/posts/lets-start-writing/</guid>
      <description>&lt;h3 id=&#34;rebuilding-the-site-from-plain-html-to-hugo&#34;&gt;Rebuilding the Site: From Plain HTML to Hugo&lt;/h3&gt;&#xA;&lt;p&gt;For a while, my personal website relied on the absolute basics: static HTML files, standard CSS, and a bit of JavaScript for behavior. While this manual approach offers complete control, it scales poorly when you want to write and organize regular updates.&lt;/p&gt;&#xA;&lt;p&gt;Recently, I decided to overhaul the site&amp;rsquo;s underlying technology to make publishing smoother. I transitioned to Hugo, a static site generator built around Markdown. It strips away the friction of writing raw HTML, letting me focus entirely on the content while the engine handles the templating and directory structure.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Archive</title>
      <link>https://www.behlulozdemir.com/archive/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.behlulozdemir.com/archive/</guid>
      <description>&lt;p&gt;Chronological index of posts.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Publications</title>
      <link>https://www.behlulozdemir.com/publications/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.behlulozdemir.com/publications/</guid>
      <description>&lt;p&gt;Selected publications and conference work.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Signal Room</title>
      <link>https://www.behlulozdemir.com/signal-room/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.behlulozdemir.com/signal-room/</guid>
      <description>&lt;p&gt;You found a page that was not meant to be on the map.&lt;/p&gt;&#xA;&lt;p&gt;Not everything belongs in the visible structure. Some things live in side channels, maintenance corridors, and quiet backdoors left open for curiosity. Consider this one of them: a small service passage behind the interface, somewhere between a forgotten route and an intentional leak.&lt;/p&gt;&#xA;&lt;p&gt;There is nothing important here, at least not in the official sense. Only fragments, experiments, odd references, and whatever slips through the grid when no one is looking too closely.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
