<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dale Blackburn on Medium]]></title>
        <description><![CDATA[Stories by Dale Blackburn on Medium]]></description>
        <link>https://medium.com/@dakebl?source=rss-8defc8cebced------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*5bTkA1nx43tvJRPlEHbeeQ.jpeg</url>
            <title>Stories by Dale Blackburn on Medium</title>
            <link>https://medium.com/@dakebl?source=rss-8defc8cebced------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:45:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dakebl/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Creating a Gatsby Plugin]]></title>
            <link>https://medium.com/@dakebl/creating-a-gatsby-plugin-1a0bf6767dfd?source=rss-8defc8cebced------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a0bf6767dfd</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[gatsbyjs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[plugin-development]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Dale Blackburn]]></dc:creator>
            <pubDate>Tue, 16 Apr 2019 21:00:12 GMT</pubDate>
            <atom:updated>2019-04-16T21:01:44.315Z</atom:updated>
            <content:encoded><![CDATA[<p>April 16, 2019</p><p><em>Originally posted on my site: </em><a href="https://dakebl.co.uk/gatsby-source-github-repo/"><em>https://dakebl.co.uk/gatsby-source-github-repo/</em></a></p><p>I recently spent some time updating a Gatsby plugin that I had written a few months ago while contributing to the new <a href="https://storybook.js.org/"><strong>Storybook website</strong></a>, and I realised that I hadn’t yet written about it, or about my experience with the <a href="https://www.gatsbyjs.org/docs/how-plugins-work/"><strong>Gatsby plugin system</strong></a>.</p><p>Time to change that!</p><h3>The Problem</h3><p>While helping out with the storybook site and issue popped up in which we needed to get a contributor count from GitHub.</p><p>We first attempted to fetch the data from the <a href="https://developer.github.com/v3/"><strong>GitHub API</strong></a> but we found that the <a href="https://developer.github.com/v3/repos/#list-contributors"><strong>Contributors endpoint</strong></a> responds with paginated data, showing 30 contributors at a time, with no way to get the total count:</p><p><a href="https://api.github.com/repos/storybooks/storybook/contributors"><strong>https://api.github.com/repos/storybooks/storybook/contributors</strong></a></p><p>We then tried to use <a href="https://stackoverflow.com/questions/44347339/github-api-how-efficiently-get-the-total-contributors-amount-per-repository"><strong>this trick</strong></a>, where you ask for one contributor per page and count the number of pages. But the pagination maxed out at 399, preventing us from getting an accurate count.</p><p>We eventually came to the idea of scraping the data from the GitHub repo page itself, as a pre-build step.</p><p>I created a script using <a href="https://www.npmjs.com/package/node-fetch"><strong>node-fetch</strong></a> and <a href="https://cheerio.js.org/"><strong>Cheerio</strong></a> that lifted and parsed the HTML body of the repo. This script provided the value directly from the contributor count link, and wrote it into the projects <strong>package.json</strong>, as an <a href="https://docs.npmjs.com/files/package.json#config"><strong>npm config variable</strong></a> called <strong>contributors</strong>:</p><pre>const fs = require(&#39;fs&#39;);<br>const fetch = require(&#39;node-fetch&#39;);<br>const cheerio = require(&#39;cheerio&#39;);</pre><pre>const PACKAGE = require(&#39;./package&#39;);</pre><pre>const repoURL = &#39;https://github.com/storybooks/storybook&#39;;</pre><pre>const getContributorCount = async () =&gt; {<br>  await fetch(repoURL)<br>    .then(res =&gt; res.text())<br>    .then(body =&gt; {<br>      const $ = cheerio.load(body);<br>      const count = $(&#39;a[href=&quot;/storybooks/storybook/graphs/contributors&quot;] &gt; span&#39;).html().trim();<br>      const packageJson = {...PACKAGE, config: { contributors: count }<br>      fs.writeFile(&#39;package.json&#39;, JSON.stringify(packageJson}, null, 2), (err) =&gt; {<br>        if(err) {<br>            return console.error(err);<br>        }<br>        console.log(`New contributor count added to package.json: ${count} contributors!`);<br>     }); <br>    });<br>};</pre><pre>getContributorCount();</pre><p>With this config variable, we could fetch the value using either <strong>process.env.npm_package_config_contributors</strong> or by pulling it from the <strong>package.json</strong> directly via import.</p><p>This worked great locally but had some drawbacks.</p><ul><li>Having a pre-build step isn’t an ideal way to handle data fetching, which ideally should be a part of the build itself</li><li>The build time was marginally slowed down</li><li>The script was causing an issue for visual regression testing. As the repo’s <a href="https://www.chromaticqa.com/"><strong>Chromatic</strong></a> tests all resulted in <strong>000</strong> as a contributor count.</li></ul><h3>Gatsby Plugin Library</h3><p>Thankfully for me, Gatsby has an excellent and well-documented plugins API, that leverages an extremely flexible GraphQL implementation. This would make it very easy to convert my manual, single use case scraper into a data source that could be useful to others, providing there wasn’t already a plugin out there that already did the job.</p><h4>Gatsby Plugin Types</h4><p>Gatsby defines a few types of plugin, each with it’s own purpose and naming convention:</p><ul><li><em>Data sources plugins</em>, which use <strong>gatsby-source-*</strong></li><li><em>Data transformer plugins</em>, which use <strong>gatsby-transformer-*</strong></li><li><em>Plugins for other plugins</em>, which use <strong>gatsby-[some plugin name]-*</strong></li><li><em>And a general plugin for anything else</em>, which use <strong>gatsby-*</strong></li></ul><p>You can read more about these here: <a href="https://www.gatsbyjs.org/docs/how-plugins-work/#plugin-naming-conventions"><strong>https://www.gatsbyjs.org/docs/how-plugins-work/#plugin-naming-conventions</strong></a></p><p>I searched the <a href="https://www.gatsbyjs.org/plugins/"><strong>Gatsby plugin library</strong></a> to see if a package already existed that could help us with our goal, and ended up finding some great GitHub packages, but none of them accomplished what we were trying to achieve (again, mainly due to the limitations of the GitHub API).</p><p>It looked like I was building a plugin.</p><h3>Writing a Gatsby source plugin</h3><p>I was happy to find that the documentation on <a href="https://www.gatsbyjs.org/docs/creating-a-source-plugin/"><strong>creating a Gatsby source plugin</strong></a> was well written and easy to follow, giving a step by step guide on implementing data source fetching and shaping it for the GraphQL API.</p><p>I doubt I’ll be able to write a better guide for source plugin authoring, but I’ll run you through what I did.</p><p>A plugin primarily comprises of a single file, <strong>gatsby-node.js</strong>. You can consider this file as an extension to your Gatsby projects own file of the same name. Both are intended to work with the data layer and can be used to create pages and GraphQL nodes, transform data, run web servers, modify config, and more.</p><p>You can read up about the node APIs here: <a href="https://www.gatsbyjs.org/docs/node-apis"><strong>https://www.gatsbyjs.org/docs/node-apis</strong></a>.</p><p>Conveniently, Gatsby supplies a <strong>sourceNodes</strong> extension point that contains all the functions you need to create data nodes in the GraphQL endpoint. Here’s what the boilerplate code looks like:</p><pre>const fetch = require(&#39;node-fetch&#39;)<br>const cheerio = require(&#39;cheerio&#39;)</pre><pre>exports.sourceNodes = async ({ actions, createNodeId, createContentDigest }, configOptions) =&gt; {<br>  const { createNode } = actions</pre><pre>    const repoData = {}</pre><pre>    // Code for scraping repoData goes here.</pre><pre>    const nodeId = createNodeId(`${[repoData.name, repoData.author].join(&#39;-&#39;)}`)<br>    const nodeContent = JSON.stringify(repoData)<br>    const contentDigest = createContentDigest(repoData)</pre><pre>    const nodeMeta = {<br>      id: nodeId,<br>      parent: null,<br>      children: [],<br>      internal: {<br>        type: `GitHubRepoData`,<br>        content: nodeContent,<br>        contentDigest<br>      }<br>    }</pre><pre>    const node = Object.assign({}, repoData, nodeMeta)</pre><pre>    createNode(node)<br>  })<br>}</pre><p>Let’s take some time to break this down and see what’s happening.</p><h4>The Gatsby Source API Functions</h4><p>First we pull out the <strong>actions</strong>,<strong>createNodeId</strong>, and <strong>createContentDigestfunctions</strong> from <strong>sourceNodes</strong>. We then pull the <strong>createNode</strong> function from <strong>actions</strong>.</p><p>Each of these has a specific role to play in the forming of our data node:</p><ul><li><strong>createNodeId</strong> is used to create a globally unique ID.</li><li><strong>createContentDigest</strong> is used to create a unique hex-encoded key, which is dynamically based on changes to the content.</li><li><strong>actions</strong> provides the <strong>createNode</strong> function, which is for adding data nodes to GraphQL</li></ul><p>You can read more about sourceNodes here: <a href="https://www.gatsbyjs.org/docs/node-apis/#sourceNodes"><strong>https://www.gatsbyjs.org/docs/node-apis/#sourceNodes</strong></a></p><p>After we have scraped the parts of the repo we’re interested in, we shape the data to be ready for node creation, creating custom ids and a digest along the way:</p><pre>// We generate a unique ID for our new node<br>  const nodeId = createNodeId(`${[repoData.name, repoData.author].join(&#39;-&#39;)}`)</pre><pre>  // We stringify the value of the data so that it can be be used in the contents meta data<br>  const nodeContent = JSON.stringify(repoData)</pre><pre>  // We generate a hex-encoded content digest, based our stringified data<br>  const contentDigest = createContentDigest(repoData)</pre><pre>  // We shape the required metadata, using our unique indentifiers and stringified data<br>  const nodeMeta = {<br>    id: nodeId,<br>    parent: null,<br>    children: [],<br>    internal: {<br>      type: `GitHubRepoData`, // used to generate the resulting GraphQL query name<br>      content: nodeContent,<br>      contentDigest<br>    }<br>  }</pre><pre>  // We create a new object that merges the data with it&#39;s metadata, finalising the shape of the node<br>  const node = Object.assign({}, repoData, nodeMeta)</pre><pre>  // And finally use the new node data to generate the entry in the GraphQL data source<br>  createNode(node)</pre><p>As a result of our new plugin, we now end up with the following structure and data being available:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/0*KfhdnOD5_h_DE4AN.png" /></figure><p>This data can now be exposed in our Gatsby project to do with as we please.</p><h3>Using the Plugin</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/0*b3ET3QkamWyvpDGo.png" /></figure><p>Link: <a href="https://www.npmjs.com/package/gatsby-source-github-repo"><strong>https://www.npmjs.com/package/gatsby-source-github-repo</strong></a></p><p>You can install the latest copy of the plugin using:</p><p><strong>npm i gatsby-source-github-repo@latest</strong>.</p><p>Then all you need to do is add the plugin configuration to your projects <strong>gatsby-config</strong> file:</p><pre>{<br>  plugins: [<br>    {<br>      resolve: &#39;gatsby-source-github-repo&#39;,<br>      options: {<br>        repoUrl: &#39;https://github.com/gatsbyjs/gatsby&#39;,<br>      }<br>    },<br>  ]<br>}</pre><p>You can find the plugin on npm, or in the Gatsby plugin library.</p><h3>Final thoughts</h3><p>As I mentioned, I recently updated the plugin. I decided to switch from <strong>Cheerio</strong> to <a href="https://github.com/jsdom/jsdom"><strong>JSDom</strong></a>, which I’ve found a better experience when parsing raw HTML. This is mainly due to:</p><ul><li>Cheerio’s obfuscated internal functions producing erroneous/inconsistent results.</li><li>Cheerio uses a jQuery like syntax, where as JSDom uses vanilla JS window/document methods.</li><li>JSDom yields the same experience of using a DOM window, with all it’s associated functionality.</li></ul><p>Here’s the final code:</p><pre>const fetch = require(&#39;node-fetch&#39;)<br>const { JSDOM } = require(&#39;jsdom&#39;);</pre><pre>exports.sourceNodes = async ({ actions, createNodeId, createContentDigest }, configOptions) =&gt; {<br>  const { createNode } = actions</pre><pre>  // Gatsby adds a configOption that&#39;s not needed for this plugin, delete it<br>  delete configOptions.plugins</pre><pre>  const { repoUrl, repoUrls } = configOptions<br>  if (!repoUrl || typeof repoUrl !== &#39;string&#39;) {<br>    throw new Error(&#39;You must supply a valid url string for the desired repo&#39;)<br>  }</pre><pre>  await fetch(repoUrl)<br>    .then(res =&gt; res.text())<br>    .then(body =&gt; {<br>      const dom = new JSDOM(body);<br>      const doc = dom.window.document;</pre><pre>      const title = doc.querySelector(&#39;title&#39;).textContent</pre><pre>      if (title.indexOf(&#39;Page not found&#39;) &gt;= 0) {<br>        throw new Error(&#39;Github page was not found at &quot;&#39; + repoUrl  + &#39;&quot;&#39;)<br>      }</pre><pre>      const author = doc.querySelector(&#39;h1.public span.author a&#39;) &amp;&amp; doc.querySelector(&#39;h1.public span.author a&#39;).textContent<br>      const name = doc.querySelector(&#39;h1.public strong[itemprop=&quot;name&quot;] a&#39;) &amp;&amp; doc.querySelector(&#39;h1.public strong[itemprop=&quot;name&quot;] a&#39;).textContent<br>      const description = doc.querySelector(&#39;span[itemprop=&quot;about&quot;]&#39;) &amp;&amp; doc.querySelector(&#39;span[itemprop=&quot;about&quot;]&#39;).textContent || &#39;Repo does not have a description.&#39;<br>      const website = doc.querySelector(&#39;span[itemprop=&quot;url&quot;] a&#39;) &amp;&amp; doc.querySelector(&#39;span[itemprop=&quot;url&quot;] a&#39;).href || &#39;Repo does not have a website.&#39;<br>      <br>      const topics = Object.values(doc.querySelectorAll(&#39;div.list-topics-container a&#39;)).map(topicLink =&gt; {<br>        let topic = topicLink.textContent<br>        return topic.trim()<br>      })</pre><pre>      const commitCount = doc.querySelector(&#39;.numbers-summary li.commits span&#39;) &amp;&amp; doc.querySelector(&#39;.numbers-summary li.commits span&#39;).textContent<br>      const branchCount = doc.querySelector(&#39;.numbers-summary a[href*=&quot;/branches&quot;] span&#39;) &amp;&amp; doc.querySelector(&#39;.numbers-summary a[href*=&quot;/branches&quot;] span&#39;).textContent<br>      const releaseCount = doc.querySelector(&#39;.numbers-summary a[href*=&quot;/releases&quot;] span&#39;) &amp;&amp; doc.querySelector(&#39;.numbers-summary a[href*=&quot;/releases&quot;] span&#39;).textContent<br>      const contributorCount = doc.querySelector(&#39;.numbers-summary a[href*=&quot;/graphs/contributors&quot;] span&#39;) &amp;&amp; doc.querySelector(&#39;.numbers-summary a[href*=&quot;/graphs/contributors&quot;] span&#39;).textContent</pre><pre>      let licence = &#39;Repo does not have a licence&#39;<br>      if (doc.querySelector(&#39;.numbers-summary a[href*=&quot;/LICENSE&quot;]&#39;)) {<br>        // Remove SVG from licence a tag so we can access it&#39;s adjacent licence name<br>        doc.querySelector(&#39;.numbers-summary a[href*=&quot;/LICENSE&quot;] svg&#39;).parentNode.removeChild<br>        licence =  doc.querySelector(&#39;.numbers-summary a[href*=&quot;/LICENSE&quot;]&#39;).textContent<br>      }</pre><pre>      const languageStats = Object.values(doc.querySelectorAll(&#39;ol.repository-lang-stats-numbers li a&#39;)).map(language =&gt; {<br>        let lang = language.querySelector(&#39;span.lang&#39;) &amp;&amp; language.querySelector(&#39;span.lang&#39;).textContent<br>        return {<br>          lang: lang.trim(),<br>          percentage: language.querySelector(&#39;span.percent&#39;) &amp;&amp; language.querySelector(&#39;span.percent&#39;).textContent,<br>        }<br>      })</pre><pre>      const repoData = {<br>        name: String(name).trim(),<br>        author: String(author).trim(),<br>        url: String(repoUrl),<br>        description: String(description).trim(),<br>        website: String(website).trim(),<br>        topics: (topics.length &gt; 0) ? topics : &#39;Repo does not have any defined topics.&#39;,<br>        commitCount: String(commitCount).trim(),<br>        branchCount: String(branchCount).trim(),<br>        releaseCount: String(releaseCount).trim(),<br>        contributorCount: String(contributorCount).trim(),<br>        licence: String(licence).trim(),<br>        languageStats <br>      }</pre><pre>      const nodeContent = JSON.stringify(repoData)</pre><pre>      const nodeMeta = {<br>        id: createNodeId(`${[name, author].join(&#39;-&#39;)}`),<br>        parent: null,<br>        children: [],<br>        internal: {<br>          type: `GitHubRepoData`,<br>          content: nodeContent,<br>          contentDigest: createContentDigest(repoData)<br>        }<br>      }</pre><pre>      const node = Object.assign({}, repoData, nodeMeta)<br>      createNode(node)</pre><pre>      return repoData<br>    })<br>}</pre><p>I’m a lot happier with the code and it seems to be working nicely.</p><p>In regards to writing a Gatsby plugin, I found the experience simple and delightful, much like the rest of the Gatsby developer experience.</p><p>I urge anyone looking to handle non-local data and file resource for their Gatsby project to give it a try.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a0bf6767dfd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rebuilding my website with Gatsby and Netlify]]></title>
            <link>https://medium.com/@dakebl/rebuilding-my-website-with-gatsby-and-netlify-96233f4b4c6d?source=rss-8defc8cebced------2</link>
            <guid isPermaLink="false">https://medium.com/p/96233f4b4c6d</guid>
            <category><![CDATA[brutalist-design]]></category>
            <category><![CDATA[brutalist]]></category>
            <category><![CDATA[gatsby]]></category>
            <category><![CDATA[netlify]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Dale Blackburn]]></dc:creator>
            <pubDate>Tue, 05 Feb 2019 09:09:41 GMT</pubDate>
            <atom:updated>2019-02-05T09:09:41.507Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*JBGvluKEbg7NnuW4-8YcdQ.png" /></figure><p>Last year I created a shiny new website, with the best intentions to share discoveries and pen down my thoughts. Sadly, I didn’t manage to get any further than then <a href="https://dakebl.co.uk/hello-world">the initial one</a> that announced my new websites arrival.</p><p>It seems that the only fitting thing to do now, having just rebuilt my website for the third time, is to write a new post of a similar ilk and go over the new build in a little detail.</p><h3>Previous Website</h3><p>This is how the previous version looked:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*M7TwBmg6Fn3F3TXj.png" /></figure><p>The site was built using <a href="https://nuxtjs.org/">Nuxt.js</a>, the <a href="https://vuejs.org/">Vue.js</a> equivalent of <a href="https://nextjs.org/">Next.js</a>, and was purposely simple and functional. I used the static site generator <a href="https://nuxtent.now.sh/">Nuxtent</a> to accomplish a simple document based blog and leaned into an acquired love of <a href="https://brutalist-web.design/">brutalist web design</a> for the look and feel.</p><p>I really enjoyed working on this site but I found that the resulting workflow felt a little sloppy and thrown together for the most part. This, coupled with the fact that I’ve been working with <a href="https://reactjs.org/">React</a> more than Vue over last year, made me seek out some new tech to reduce the barrier to blogging, so I might find it easier to get myself writing regularly.</p><h3>Choosing Gatsby</h3><p>What can I say about <a href="https://gatsbyjs.org/">Gatsby</a> other than that it is a dream to work with. After working on a few small Gatsby projects I found myself enamoured with the developer experience.</p><p>It provides just the right layer of abstraction, allowing you to easily provide data from any source, with it’s integrated <a href="https://graphql.org/">GraphQL</a> instance, tooling, and config driven development.</p><p>It also provides you with a useful suite of components for routing, data querying, etc that makes developing your website a breeze.</p><p>Seeing as the resulting site itself is built in React, there are no real restrictions to what you can do with it, especially with the templating and plugin systems that make it all very easy to get started.</p><p>So, with these heart eyes for Gatsby in mind, you can see why it was a clear choice for me as the next iteration of my blog.</p><h3>The New Website</h3><p>With the new site, I wanted to carry over the general feel of the previous version, basic and brutalist, so I decided to again go with a monochrome palette and plain system fonts. This time however I chose to use two system fonts:</p><pre>h1,h2,h3,h4,h5,h6 { font-family: -apple-system, BlinkMacSystemFont, Segoe UI, Roboto, Oxygen-Sans, Ubuntu, Cantarell, Helvetica Neue, sans-serif; } body { font-family: Menlo, Monaco, Lucida Console, monospace, serif; }</pre><p>This made a subtle difference that breaks up the heavy body content from the headings a little better.</p><p>The main shift in design is embedding the blog feed directly into the home page, moving the previous content into a fixed sidebar and opening up the doors to a single, load on demand list of posts. I built the layout using CSS grid, with some sensible mobile first fallbacks and I think it works rather well.</p><p>Changing over to React from Vue also allowed me to rethink my component structure and, after sketching out the layout in my notebook, the design provided a much simpler and clearer set of components to work with.</p><p>All in all, it’s not a massively different site aesthetically but I’m happy with how it’s turned out. I think the structure makes sense and I’ve really enjoyed working with Gatsby. It’s definitely the platform I’ll reach for any time I need to put a new site together going forward.</p><h3>Hosting on Netlify</h3><p>The previous version of my site was hosted using GitHub Pages, which has served me well for my hosting needs, but I felt it was time to move to something a little more robust for my next hosting and CI/CD solution.</p><p><a href="https://netlify.com/">Netlify</a> is a fantastic service and, for the basic needs I have, completely free. I’ve recently used their <a href="https://www.netlifycms.org/docs/start-with-a-template/">NetlifyCMS Gatsby Starter</a> while building a website for a client and it was a dream. If you need a CMS to go along with your Gatsby (or <a href="https://gohugo.io/">Hugo</a> or <a href="https://middlemanapp.com/">Middleman</a>) build, I’d recommend checking theirs out. It’s perfect for providing a simple editor (both rich text and markdown), as well as auth and asset management, right out of the box.</p><p>In general, I’ve found everything about Netlify’s services and OSS to be incredibly considerate and well thought out, so it was a clear choice.</p><p>As I prefer writing my markdown in <a href="https://code.visualstudio.com/">VSCode</a> directly, using its side pane preview, I didn’t need the CMS. So, having elected to simply control my blog post publishing via commits, I pointed Netlify to <a href="https://github.com/dakebl/dakebl.co.uk">the repo for this site</a>, set my deploy hook to rebuild the site on pushes to the Master branch, and here we are!</p><p>A fully automated static site pipeline and I couldn’t be happier about it!</p><p><em>Originally published at </em><a href="https://dakebl.co.uk/rebuilding-my-website-with-gatsby-and-netlify/"><em>dakebl.co.uk</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96233f4b4c6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>