<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Wordpress on Marco&#39;s Blog</title>
    <link>https://www.mrgazz.com/tags/wordpress/</link>
    <description>Recent content in Wordpress on Marco&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <managingEditor>marco@mrgazz.com (Marco)</managingEditor>
    <webMaster>marco@mrgazz.com (Marco)</webMaster>
    <lastBuildDate>Thu, 04 Jan 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.mrgazz.com/tags/wordpress/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Porting a Template from WordPress to Hugo</title>
      <link>https://www.mrgazz.com/post/2024-01-04-porting-a-template-from-wordpress-to-hugo/</link>
      <pubDate>Thu, 04 Jan 2024 00:00:00 +0000</pubDate><author>marco@mrgazz.com (Marco)</author>
      <guid>https://www.mrgazz.com/post/2024-01-04-porting-a-template-from-wordpress-to-hugo/</guid>
      <description>Static Site Generators (SSG) are all the rage and are quickly becoming viable alternative to heavier Content Management Systems (CMS) like WordPress. I switched sites from WordPress to Hugo, one of the leadings SSG sites, but wanted to keep the site look and feel the same. To do so, I needed to port the theme I had used on WordPress. This article shows how to go about it if you want to do the same.</description>
    </item>
    <item>
      <title>Moving on again: Joomla to WordPress to Hugo</title>
      <link>https://www.mrgazz.com/post/2023-11-09-moving-on-again-joomla-to-wordpress-to-hugo/</link>
      <pubDate>Thu, 09 Nov 2023 00:00:00 +0000</pubDate><author>marco@mrgazz.com (Marco)</author>
      <guid>https://www.mrgazz.com/post/2023-11-09-moving-on-again-joomla-to-wordpress-to-hugo/</guid>
      <description>&lt;p&gt;It&amp;rsquo;s that time of the century again: I need to move on from one platform to another and carry (almost) all the content with me. This time, the move was not &lt;em&gt;necessary&lt;/em&gt; and I could have continued working with WordPress. But updating the software every few days added up in time, the concern that eventually I&amp;rsquo;d be caught by a WordPress flaw that allowed remote execution, and ultimate takeover of the server, and the resources required to run PHP and MySQL were all too much.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Long Time No Read!</title>
      <link>https://www.mrgazz.com/post/2018-03-24-long-time-no-read/</link>
      <pubDate>Sat, 24 Mar 2018 19:21:27 +0000</pubDate><author>marco@mrgazz.com (Marco)</author>
      <guid>https://www.mrgazz.com/post/2018-03-24-long-time-no-read/</guid>
      <description>&lt;p&gt;The spiders are busy deciding what happened to the old links on this site, while humans find the content just fine using the &lt;em&gt;Search&lt;/em&gt; feature. But what happened? In short, we switched from Joomla to WordPress. It’s been a painful process, but one that couldn’t be postponed.&lt;/p&gt;&#xA;&lt;p&gt;What was wrong with Joomla? Nothing major, really. Joomla is a fine piece of software, despite not being as popular or as beloved by the geeky masses. The crown of the former Kingdom belongs to WordPress, while the one of the other probably to Drupal, as far as PHP is concerned. But I grew increasingly frustrated with the direction Joomla was taking, and the camel’s back broke when I tried to get an Esperanto version of the software. I spent weeks translating and translating, the most boring and redundant strings, only to have the translation administrator disappear, then reappear, then declare he was going to take care of translating from then on, and then disappear again.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
