<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>css on keyes.ie</title>
    <link>https://keyes.ie/tags/css/</link>
    <description>Recent content in css on keyes.ie</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 08 May 2020 23:45:00 +0000</lastBuildDate>
    
	<atom:link href="https://keyes.ie/tags/css/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Tailwind CSS &#43; Hugo | Step 3 – Adding some basic content.</title>
      <link>https://keyes.ie/tailwindcss-hugo-step-3/</link>
      <pubDate>Fri, 08 May 2020 23:45:00 +0000</pubDate>
      
      <guid>https://keyes.ie/tailwindcss-hugo-step-3/</guid>
      <description>I added some basic content to the site index page tonight.
I don&amp;rsquo;t want to design the layout in isolation from the content. Real content allows me to do this piece by piece, and gives me some confidence in my approach.
Yes I could pre-plan this, and I&amp;rsquo;ve flip-flopped on writing up a design doc on this before doing any more work. However, what this would contain is beyond the horizon, and I fear I&amp;rsquo;d remain static.</description>
    </item>
    
    <item>
      <title>Tailwind CSS &#43; Hugo | Step 2 – Create a Basic Layout</title>
      <link>https://keyes.ie/tailwindcss-hugo-step-2/</link>
      <pubDate>Wed, 29 Apr 2020 22:45:00 +0000</pubDate>
      
      <guid>https://keyes.ie/tailwindcss-hugo-step-2/</guid>
      <description>It&amp;rsquo;s been a while since Step 1 but I&amp;rsquo;ve finally come back to have a little further exploration with Tailwind.
After Step 1, I had a very very basic site in place, so I decided it&amp;rsquo;s time to create a basic layout.
I&amp;rsquo;ve decided not to be very adventurous to start-out, and so I stick with the single column layout I currently have on the site, along with three main sections of content.</description>
    </item>
    
    <item>
      <title>Tailwind CSS &#43; Hugo | Step 1 – Create the Theme</title>
      <link>https://keyes.ie/tailwindcss-hugo-step-1/</link>
      <pubDate>Sun, 16 Feb 2020 19:26:00 +0000</pubDate>
      
      <guid>https://keyes.ie/tailwindcss-hugo-step-1/</guid>
      <description>The first step in this process is to create a new Hugo theme.
hugo new theme tailwind-keyes This command creates a skeleton theme:
themes/tailwind-keyes ├── archetypes │ └── default.md ├── layouts │ ├── 404.html │ ├── _default │ │ ├── baseof.html │ │ ├── list.html │ │ └── single.html │ ├── index.html │ ├── partials │ │ ├── footer.html │ │ ├── header.html │ │ └── head.html ├── LICENSE ├── static │ ├── css │ └── js └── theme.</description>
    </item>
    
    <item>
      <title>Tailwind CSS &#43; Hugo</title>
      <link>https://keyes.ie/tailwindcss-hugo/</link>
      <pubDate>Fri, 14 Feb 2020 22:56:00 +0000</pubDate>
      
      <guid>https://keyes.ie/tailwindcss-hugo/</guid>
      <description>I&amp;rsquo;ve seen Tailwind CSS mentioned more than once over the past couple of years, and these mentions have always been favourable.
My web design days are fading in the distance, so I thought it might be a good idea to attempt to create a Hugo template based on tailwind.
I&amp;rsquo;ve cloned this site to a new domain tailwind.keyes.ie and the new theme will be used for that site. This will be a bit by bit approach, and hopefully it&amp;rsquo;ll keep me interested enough to post updates here.</description>
    </item>
    
  </channel>
</rss>