<?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 Mike Harrison on Medium]]></title>
        <description><![CDATA[Stories by Mike Harrison on Medium]]></description>
        <link>https://medium.com/@the.agent?source=rss-4c4965dbdc64------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*gxgn9QGf5g6DD6hjROnYlQ.png</url>
            <title>Stories by Mike Harrison on Medium</title>
            <link>https://medium.com/@the.agent?source=rss-4c4965dbdc64------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 06:13:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@the.agent/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[Why Rebelle 8 Pro Is the Closest Thing to Real Painting]]></title>
            <link>https://medium.com/@the.agent/why-rebelle-8-pro-is-the-closest-thing-to-real-painting-0c24f94a4f16?source=rss-4c4965dbdc64------2</link>
            <guid isPermaLink="false">https://medium.com/p/0c24f94a4f16</guid>
            <category><![CDATA[digital-painting]]></category>
            <category><![CDATA[digital-art]]></category>
            <category><![CDATA[watercolor]]></category>
            <category><![CDATA[pastel]]></category>
            <category><![CDATA[art]]></category>
            <dc:creator><![CDATA[Mike Harrison]]></dc:creator>
            <pubDate>Thu, 01 Oct 2026 02:24:53 GMT</pubDate>
            <atom:updated>2026-10-01T02:53:08.717Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MZ-Sd3U3rGwOefYm_UgTsQ.jpeg" /><figcaption>Landscape, Pastel on paper, 2018, by the author</figcaption></figure><h4>I found a digital painting app that feels like traditional art supplies</h4><p>Traditional art has always been my passion. Pastel, watercolor, and coloured pencil were my preferred mediums, especially for the chalky texture of pastel on paper and the way watercolor drips and bleeds. I love using a lot of different mediums, though. One of my pastels on paper is the photo in the title. A colored pencil cherries drawing is in the middle of the article, and you can see one of my pencil drawings at the bottom.</p><p>When I started traveling, though, I couldn’t bring all my art supplies with me. Paints, papers, and boxes of pastels don’t pack easily, so I became a digital painting enthusiast.</p><p>The problem was that digital painting never felt like <em>painting</em>. I tried several applications, and while they were capable, none of them came close to the real-life experience I was used to. Something was always missing. I have always wanted an application that I could use to follow along with traditional art courses.</p><p>I used Corel Painter back in the day, and it was pretty good, but I didn’t like how the watercolor was always on its own layer, and how it didn’t perform well on my laptop. And now, it seems like Corel has basically abandoned it, so I was looking for an alternative.</p><p>And that’s when I found Rebelle 8 Pro.</p><h3>Finding Rebelle</h3><p>I came across Rebelle on Escape Motions’ YouTube channel. They have a lot of videos about it, including some showing how to use it with traditional painting techniques. That’s what caught my attention. Instead of asking you to learn a whole new way of working, Rebelle lets you paint the way you already know how.</p><h3>It really does feel like real painting</h3><p>Rebelle 8 Pro comes closer to real painting than any other application I’ve ever used. A few things stood out to me:</p><p><strong>The watercolor simulation is amazing.</strong> Paint flows, spreads, and interacts with the paper the way real watercolor does. As a watercolor painter, that was the first thing I tested, and it didn’t disappoint. The performance is outstanding, much better than the experience I had with Corel Painter.</p><p><strong>The oil impasto looks great.</strong> Thick paint has real texture and dimension. You can see the brushstrokes.</p><p><strong>The pigment mixing is very realistic.</strong> Colors blend like actual paint instead of the flat, muddy blending you often get in digital apps. This feature alone is why you want the Pro version. It’s worth it.</p><p>Most importantly, a traditional artist can work in Rebelle using pretty much the same techniques as in real life and get the same results. Everything I learned with real materials still applies.</p><h3>Every medium in one place</h3><p>I love working in all different mediums, and Rebelle has them all: watercolor, oil, acrylic, pastel, pencil, and colored pencil. For someone who’s traveling, that’s huge. My entire art studio now fits on a laptop.</p><figure><img alt="a drawing of red cherries using colored pencil on paper" src="https://cdn-images-1.medium.com/max/1024/1*_rt_wkGkfHF1esXU5bAZKQ.jpeg" /><figcaption>Cherries, Colored pencil on paper, 2018, by the author</figcaption></figure><h3>You don’t need expensive equipment</h3><p>I use a small Wacom tablet with no pen rotation or tilt support, and I still get excellent results. Those features are nice to have, but they aren’t required to enjoy Rebelle or create a beautiful work with it. If you’re worried you need a high-end setup to get started, you don’t.</p><h3>A company that stands with artists</h3><p>I also applaud Escape Motions for its stance on AI. There’s no generative AI in Rebelle, and the company has blocked AI bots from scraping artists’ work in its community gallery. You can read their statement here: <a href="https://www.escapemotions.com/blog/escape-motions-stands-by-artists">Escape Motions Stands by Artists</a>.</p><p>Honestly, Rebelle is so much fun to use. The painting process <em>is</em> the enjoyable part, so why would anyone want to skip it and just generate an image with AI?</p><h3>Final thoughts</h3><p>It was hard to find anything I didn’t like about Rebelle 8 Pro. The only thing is if I make some brushes too big, there is some lag in the brushes. Other than that, I had no issues in the 30-day trial.</p><p>I highly recommend it to traditional artists frustrated with digital painting or those who, like me, had to leave their physical supplies behind. There’s nothing better.</p><p>Escape Motions offers a free trial on their website, so you can try it yourself.</p><p>This blog article features only my traditional art because I currently cannot access anything I created in Rebelle since my trial period ended. Once I purchase the product, I’ll post some of my efforts in a future blog post.</p><p><em>Disclosure: Escape Motions offers a discount for sharing about their software. All opinions here are my own, based on my experience with the trial.</em></p><figure><img alt="a drawing of a daisy with graphite pencil on paper" src="https://cdn-images-1.medium.com/max/1024/1*OQ3y6Rsw31OGLiuBcRRezg.jpeg" /><figcaption>Daisy, Pencil on paper, 2018, by the author</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0c24f94a4f16" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hugo From the Ground Up (Part 4)]]></title>
            <link>https://medium.com/@the.agent/hugo-from-the-ground-up-part-4-24df24a5a8de?source=rss-4c4965dbdc64------2</link>
            <guid isPermaLink="false">https://medium.com/p/24df24a5a8de</guid>
            <category><![CDATA[static-site-generator]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[hugo]]></category>
            <dc:creator><![CDATA[Mike Harrison]]></dc:creator>
            <pubDate>Thu, 09 Jan 2020 04:24:00 GMT</pubDate>
            <atom:updated>2020-01-09T04:25:08.388Z</atom:updated>
            <content:encoded><![CDATA[<h3>Menu</h3><p>We have our home page and an about page now (see <a href="https://medium.com/@the.agent/hugo-from-the-ground-up-part-3-259ae114b8c9">part 3</a>), now we want to create a menu that will live in the site header, so we can navigate to all the pages on the site.</p><p>So to do this, we want to modify layout/partials/header.html as follows:</p><pre>&lt;header&gt;</pre><pre>  &lt;h1&gt;&lt;a href=&quot;{{ .Site.BaseURL }}&quot;&gt;{{ .Site.Title }}&lt;/a&gt;&lt;/h1&gt;</pre><pre>  &lt;ul&gt;</pre><pre>    {{ range .Site.Sections }}</pre><pre>      &lt;li&gt;</pre><pre>        &lt;a href=&quot;{{ .Permalink }}&quot;&gt;{{ .Title }}&lt;/a&gt;</pre><pre>      &lt;/li&gt;</pre><pre>     {{ end }}</pre><pre>  &lt;/ul&gt;</pre><pre>&lt;/header&gt;</pre><p>In the h1 tag, I added a link to the home page instead of just displaying the title. So now the title is displayed linking to .Site.BaseURL , which is the built in Hugo variable that uses the baseURL in the config.toml. When you are using the hugo development server, it points to the root of the site.</p><p>The menu is set up using an un-ordered list. We can use CSS later to style it like a real menu. But for now it will display as a bulleted list. We are using the <strong>range </strong>block to loop through the .Site.Sections array. Each folder under the <strong>content</strong> folder is a <em>section</em>. So for each entry in .Site.Sections, it will put the title of that section and link to the .Permalink, which is the link to that section. And you must end the block with a {{ end }} .</p><p>Also, we need to rename our content/about/index.md to _index.md. Otherwise it will not register as a section.</p><p>So what this gives us is this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*0KKkotNa1D94VAh5Yx8y-w.png" /></figure><p>So you can navigate to the about page by clicking the About link, and back to the home page by clicking the header title.</p><p>Next, we want this to be a blog, so we should create another section called posts.</p><p>But first we need to create a list page template, so that it can list all the blog posts for us. So create list.html in layouts/_default as follows:</p><pre>{{ define “main” }}</pre><pre>   &lt;h2&gt;List Page Template&lt;/h2&gt;</pre><pre>   {{ .Content }}</pre><pre>   {{ range .Pages }}</pre><pre>      &lt;article&gt;</pre><pre>      &lt;h2&gt;&lt;a href=”{{ .Permalink }}”&gt;{{ .Title }}&lt;/a&gt;&lt;/h2&gt;</pre><pre>      &lt;/article&gt;</pre><pre>   {{ end }}</pre><pre>{{ end }}</pre><p>If you recall our baseof.html template, it has a {{ block “main” . }} in it, so we need the {{ define “main” }} block so that it will pull this template into the baseof.html.</p><p>Then it prints the .Content . If your posts folder has an _index.md in it, it will print the content from that. If it doesn’t have one, it prints nothing.</p><p>And lastly it ranges through all the pages. .Pages is a list of all the pages in the list page’s context, so it will have an entry for each markdown file in the posts folder (except for _index.md). For each post, it will link to it with the .Permalink and display the .Title.</p><p>So let’s create the first blog entry by issuing this command:</p><pre>hugo new posts/my-first-post.md</pre><p>It will automatically create the new folder and the my-first-post.md file. Then start the hugo server again with <strong>hugo server -D</strong>, and your site should now look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/318/1*aa_rrv0RGeOfyuE3pbHWNQ.png" /></figure><p>If you click on the Posts link, you will get to a list page that Hugo has automatically generated from your list.html template:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/354/1*SFMh_Q-nXHTBd4EZ2OXFxg.png" /></figure><p>Then you can click the title of the post to get to the blog post. If you wanted to rename the section name, all you have to do is create an _index.md file, and change the title.</p><pre>hugo new posts/_index.md</pre><p>And the content of my _index.md:</p><pre>— -</pre><pre>title: “Blog”</pre><pre>date: 2020–01–08T23:06:10–05:00</pre><pre>draft: true</pre><pre> — -</pre><pre>This is my blog!</pre><p>When you restart the server, you will get:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/342/1*IJTREUwAchhTRPYMGlBBCA.png" /></figure><p>So now we have a simple blog, all you need to do to write blog entries is to create post files in the posts folder, and hugo will automatically add them to the list, in descending order by the date in the front matter of each post file.</p><p>You use markdown to write the text in the .md files. Markdown is a simplified way of formatting pages, similar to HTML but without all the tags. A complete markdown reference can be found here:</p><ul><li><a href="https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet">Markdown Cheatsheet</a></li></ul><p>In the next part of this series, we will use CSS to format our site to make it look more modern, instead of a 1993 style site.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24df24a5a8de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hugo From the Ground Up — Part 3]]></title>
            <link>https://medium.com/@the.agent/hugo-from-the-ground-up-part-3-259ae114b8c9?source=rss-4c4965dbdc64------2</link>
            <guid isPermaLink="false">https://medium.com/p/259ae114b8c9</guid>
            <category><![CDATA[template]]></category>
            <category><![CDATA[static-site-generator]]></category>
            <category><![CDATA[hugo]]></category>
            <dc:creator><![CDATA[Mike Harrison]]></dc:creator>
            <pubDate>Wed, 08 Jan 2020 00:30:23 GMT</pubDate>
            <atom:updated>2020-01-09T04:26:01.337Z</atom:updated>
            <content:encoded><![CDATA[<h3>Hugo From the Ground Up (Part 3)</h3><p>Now we have our home page (see <a href="https://medium.com/@the.agent/hugo-from-the-ground-up-part-2-4f713aa6ecf5">part 2</a>) up and running, in this part we will add an About page.</p><h3>Content</h3><p>First, we need to add some content that would be rendered on the about page. So, shut down your hugo server with Ctrl+C, and type the following command:</p><pre>hugo new about/index.md</pre><p>This creates a new folder “about” and puts an index.md file in it. It should look like this:</p><pre> — -</pre><pre>title: “About”</pre><pre>date: 2020–01–07T16:25:12–05:00</pre><pre>draft: true</pre><pre> — -</pre><p>This is just the front matter. To have some content to display, you can type it in below the front matter, after the “ — “ :</p><pre> — -</pre><pre>title: “About”</pre><pre>date: 2020–01–07T16:25:12–05:00</pre><pre>draft: true</pre><pre> — -</pre><pre>This is the about page</pre><p>The content that you entered will appear on the about page, but we need to create some templates for that page first.</p><h3>Templates</h3><p>Templates are how Hugo renders content. Hugo has specific rules for the naming of templates, and you can look at this in the <a href="https://gohugo.io/templates/lookup-order/">Template Lookup Order</a> page in the Hugo documentation.</p><p>There are 3 basic types of template: single pages, list pages, and baseof.</p><p>Single page templates are for single pages. A blog post and an about page are examples of single pages.</p><p>List page templates are for lists of things. Lists of blog posts, for example. List pages are automatically generated based on the list template you have provided. So when you navigate to your /posts endpoint, it will generate a list page of all blog posts if you have the template set up.</p><p>The “baseof” template allows you to have a common “outer shell” for all the other pages. It becomes the base of all the single and list pages on the site. So for every page on your site you can have the same menus, header and footer. And then depending on the type of page it is (list or single), Hugo will substitute in the appropriate template. If you have a list template set up, and do not have a home page (layouts/index.html), then Hugo will generate the home page from the list template. It is not used for the home page, if you have one.</p><p>We are just going to set up a base and a single page template for now, these should be named baseof.html and single.html.</p><p>Let’s start by setting up the baseof.html. Create a folder _default in the layouts folder. In that folder, create a baseof.html file, and copy everything from your home page (layouts/index.html) into it.</p><pre>&lt;!DOCTYPE html&gt;</pre><pre>&lt;html lang=&quot;en&quot;&gt;</pre><pre>&lt;head&gt;</pre><pre>&lt;meta charset=&quot;UTF-8&quot;&gt;</pre><pre>&lt;meta name=&quot;viewport&quot; content=&quot;width=device-width, initial-scale=1.0&quot;&gt;</pre><pre>&lt;meta http-equiv=&quot;X-UA-Compatible&quot; content=&quot;ie=edge&quot;&gt;</pre><pre>&lt;title&gt;{{ .Title }}&lt;/title&gt;</pre><pre>&lt;/head&gt;</pre><pre>&lt;body&gt;</pre><pre>{{ partial &quot;header.html&quot; . }}</pre><pre>{{ partial &quot;footer.html&quot; . }}</pre><pre>&lt;/body&gt;</pre><pre>&lt;/html&gt;</pre><p>We need to tell Hugo where it should insert the list or single templates, though. To do this we use a <strong>block</strong>. A block looks like this:</p><pre>{{ block &quot;main&quot; . }}</pre><pre>{{ end }}</pre><p>Just add that in between the calls to the header and footer partials.</p><p>It works very similar to a partial, so you have to send in the context (.) to the block. But the “main” is not referring to an html file like a partial does, it is referring to the block that is defined in your list or single page templates.</p><p>So let’s create the template for single pages, single.html in layouts/_default:</p><pre>{{ define &quot;main&quot; }}</pre><pre>&lt;h1&gt;{{ .Title }}&lt;/h1&gt;</pre><pre>Single Page Template</pre><pre>&lt;p&gt;</pre><pre>{{ .Content }}</pre><pre>&lt;/p&gt;</pre><pre>{{ end }}</pre><p>So this looks just like a partial, except it has {{ define “main” }} and {{ end }} surrounding the html. Hugo will take everything in between and insert it into all single pages on the site. So it will put the title of the page (defined in front matter), the string “Single Page Template”, and the content from the Markdown file. In our case the content for the about page is “This is the about page”.</p><p>This is all you need to generate the about page. If you save your work and start up the hugo server (<strong>hugo server -D</strong>) , you will be able to type in localhost:1313/about in the browser’s address bar, and the About page will display. We can see that it has the header, then the single page template, then the footer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/452/1*m38gyWobPKqaBvQhmPf3dg.png" /><figcaption>About page</figcaption></figure><p>In the same manner you can create as many single pages as you want by just creating new folders in the content folder and creating an index.md in them. Just issue the command</p><pre>hugo new &lt;folder-name&gt;/index.md</pre><p>The only thing now is, how do we link to all those single pages from the header? We want to have a menu so that we can navigate to all the pages on the site.</p><p>In the next part, we will update the header partial to build a simple menu for our site.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=259ae114b8c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hugo From the Ground Up (Part 2)]]></title>
            <link>https://medium.com/@the.agent/hugo-from-the-ground-up-part-2-4f713aa6ecf5?source=rss-4c4965dbdc64------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f713aa6ecf5</guid>
            <category><![CDATA[partial]]></category>
            <category><![CDATA[variables]]></category>
            <category><![CDATA[static-site-generator]]></category>
            <category><![CDATA[hugo]]></category>
            <dc:creator><![CDATA[Mike Harrison]]></dc:creator>
            <pubDate>Tue, 07 Jan 2020 04:30:46 GMT</pubDate>
            <atom:updated>2020-01-07T04:32:22.862Z</atom:updated>
            <content:encoded><![CDATA[<p>In the <a href="https://medium.com/@the.agent/hugo-from-the-ground-up-part-1-a6136ed50464">first part</a> of the series, we installed Hugo and got it up and running with a simple home page.</p><h3>Fixing the warnings</h3><p>Now that we have our site running with a home page, let’s look at fixing some warnings that are appearing in the output:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q2UgYTRWAnLQkPf9UXIKeg.png" /><figcaption>taxonomyTerm warnings</figcaption></figure><p>These warnings are because we have no templates defined for the default taxonomies (tags and categories). For now we are not going to use taxonomies, so we can disable them altogether by adding a line to the config.toml:</p><pre>disableKinds = [“taxonomy”, “taxonomyTerm”]</pre><p>Once you save, the site reloads and the warnings should be gone.</p><h3>Updating the Title</h3><p>Our index.html is showing a hardcoded title right now, but we can make that configurable by getting it to pick up the title attribute from the config.toml file.</p><p>To do this, we can reference the built-in .Site.Title variable that Hugo provides. Change your title tag in the index.html to this:</p><pre>&lt;title&gt;{{ .Site.Title }}&lt;/title&gt;</pre><p>The {{ }} signifies to Hugo that there is some executable template language code inside the brackets, so Hugo knows to run that code during the build process. You can just put variables to display information, but you can also use conditional and looping statements as well, we will get into that later on in the series.</p><p>Once you save the index.html and reload the page, it should now display the title that is in the config.toml file. You can try changing it in config.toml, save it, and see that the title of your page changes to match.</p><h3><strong>Partials</strong></h3><p>Let’s set up a header and footer for our site by using partials. Create a partials folder under the layouts folder, and create two files in that folder called header.html and footer.html.</p><p>In header.html, you can put your site wide header. This is where you would normally define your navbar. There is a way to make Hugo auto-generate a navbar based on the pages in the site, but we aren’t there yet. We are just going to put some static text for now:</p><pre>&lt;header&gt;</pre><pre>   &lt;h1&gt;Site Wide Header&lt;/h1&gt;</pre><pre>&lt;/header&gt;</pre><p>For footer.html:</p><pre>&lt;footer&gt;</pre><pre>&amp;copy; 2020 The Agent</pre><pre>&lt;/footer&gt;</pre><p>Now that our partials are set up, we can get Hugo to pick those up by using the partials command. In index.html, remove everything in between the &lt;body&gt;&lt;/body&gt; tags and put this:</p><pre>&lt;body&gt;</pre><pre>  {{ partial &quot;header.html&quot; . }}</pre><pre>  {{ partial &quot;footer.html&quot; . }}</pre><pre>&lt;/body&gt;</pre><p>The partial command takes two arguments. The first argument is the name of the partial template file, and the second one is the <strong><em>context</em></strong>. The context gives the partial template access to all the variables the page has access to.</p><p>A common mistake is forgetting to pass in the context to a partial. Let’s see this in practice. Change your header.html to look like this:</p><pre>&lt;header&gt;</pre><pre>  &lt;h1&gt;{{ .Site.Title }}&lt;/h1&gt;</pre><pre>&lt;/header&gt;</pre><p>Then remove the “.” from the partial for the header.</p><pre>&lt;body&gt;</pre><pre>{{ partial &quot;header.html&quot; }} &lt;!-- missing context --&gt;</pre><pre>{{ partial &quot;footer.html&quot; . }}</pre><pre>&lt;/body&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/426/1*zbb0MrSZeup6iv9TCvoClw.png" /><figcaption>Blank header due to missing context</figcaption></figure><p>Now we see the header is blank because we are not passing in the context to it. By default, partials do not have access to anything outside of their own scope. So if they need to reference any variables, they need to be passed the context.</p><p>Put the context back in the call to the header partial, and you should see it render correctly:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/447/1*WBsB0gnXIAn843atNjgn7g.png" /><figcaption>home page after fixing the missing context</figcaption></figure><p>So now we know how to access site variables, and how to create partials and use them. In the next part of the series, we will look at creating some more pages for the site and generate a menu to navigate to them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f713aa6ecf5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hugo From the Ground Up (Part 1)]]></title>
            <link>https://medium.com/@the.agent/hugo-from-the-ground-up-part-1-a6136ed50464?source=rss-4c4965dbdc64------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6136ed50464</guid>
            <category><![CDATA[hugo]]></category>
            <category><![CDATA[basics]]></category>
            <category><![CDATA[simple]]></category>
            <category><![CDATA[static-site-generator]]></category>
            <dc:creator><![CDATA[Mike Harrison]]></dc:creator>
            <pubDate>Mon, 06 Jan 2020 06:21:45 GMT</pubDate>
            <atom:updated>2020-01-06T06:21:45.129Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jVHrZUYPjpCkdgSi" /><figcaption>Photo by <a href="https://unsplash.com/@jontyson?utm_source=medium&amp;utm_medium=referral">Jon Tyson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This is the start of a series on Hugo, and how to use it to develop static websites. You can see my <a href="https://www.agent-blog.com/post/why-you-should-use-hugo-for-your-blog-in-2020/">previous article</a> on Hugo for some reasons why you might want to use it.</p><p>The normal hugo up and running type tutorial starts with installing a theme and deploying a site. You may have seen tutorials like “Get your Hugo site up and running in 5 minutes” or something like that. I have done those tutorials, but I find that they did not explain how Hugo works at all, and I am left scratching my head at how it’s somehow magically generating the site from the theme folder.</p><p>So what this series is aiming to do is to explore creating a simple Hugo site without any theme. This will allow us to better understand what exactly Hugo is doing when it generates the site.</p><h3>Installing Hugo</h3><p>The first step is we need to install Hugo. The instructions differ depending if you are on Mac or Windows. The Hugo website has done a great job of making an article on how to install it, so please follow that article <a href="https://gohugo.io/getting-started/installing/">here</a>.</p><h3>Create Your First Site</h3><p>Now that you have Hugo installed, open up a command line and navigate to your Hugo sites folder (C:\Hugo\Sites on Windows, for example) and issue the command to create a hugo site:</p><pre>hugo new site hello-hugo</pre><p>This will create a new hugo site, and it will create a folder with the same name as the last part of the command, in this case, “hello-hugo”.</p><p>Open up the site’s folder in VS Code or your favorite code editor.</p><p>We can see that Hugo created some folders for us, and some files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/141/1*P6Io7kSCBYz0wL0irKxc1w.png" /></figure><p>It created 6 folders and 2 files for us.</p><p>The folders are:</p><ul><li><strong>archetypes </strong>—how you configure your default front matter for posts</li><li><strong>content</strong> — where you store your website pages and blog posts</li><li><strong>data — </strong>you can store static data files here such as json, we won’t use this in this article</li><li><strong>layouts —</strong> this is where your HTML templates will go</li><li><strong>static —</strong> this is where you will store images, JavaScript, and CSS files</li><li><strong>themes — </strong>this is where you would download a theme to, but we will not be using themes at this point</li></ul><p>And the 2 files created are the config.toml and the archetypes/default.md. The default.md controls what front matter fields we will see when you use hugo to create markdown files.</p><p>The config.toml is where you put your configuration variables. The default config.toml is:</p><pre>baseURL = &quot;http://example.org/&quot;<br>languageCode = &quot;en-us&quot;<br>title = &quot;My New Hugo Site&quot;</pre><p>The baseURL is only used once you deploy your site. It is not used by the local Hugo server.</p><p>These are all just variables that we can access from our templates. The title will not automatically show up as the title of the website, it’s just a variable called .Site.Title</p><p>So let’s see what happens when we run the local hugo server. Open up a terminal window and type:</p><pre>hugo server -D</pre><p>We get this output:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2UoTVKSgrZyseqwvEdVFeg.png" /></figure><p>Notice that it says there is a web server running on port 1313 at <a href="http://localhost:1313/">http://localhost:1313</a>/. Open your web browser and go to that link.</p><p>This is what you should see:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QZAUJUqK6ltMwFn9b6aUzg.png" /></figure><p>An empty browser is what we get. And it’s no surprise since the Hugo folders are all empty except for the config files. So Hugo has generated the site and the web server is running, but it’s empty. There’s no content.</p><p>So we need at least one HTML page for Hugo to render. So, create index.html in the layouts folder. If you are using Visual Studio Code, you can type <strong>html:5 </strong>as a shortcut and it will generate some default HTML. Then change the title and put in an H1 tag.</p><pre>&lt;!DOCTYPE html&gt;<br>&lt;html lang=”en”&gt;<br> &lt;head&gt;<br>   &lt;meta charset=”UTF-8&quot;&gt;<br>   &lt;meta name=”viewport” content=”width=device-width, initial-scale=1.0&quot;&gt;<br>   &lt;meta http-equiv=”X-UA-Compatible” content=”ie=edge”&gt;<br>   &lt;title&gt;Hello Hugo&lt;/title&gt;<br> &lt;/head&gt;<br> &lt;body&gt;<br>   &lt;h1&gt;Hello, Hugo!&lt;/h1&gt;<br> &lt;/body&gt;<br>&lt;/html&gt;</pre><p>Once you save it, if you left your hugo server running, it will regenerate the site. Once you refresh your browser, you should see this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mg3qkNlYY2M0ZDmRg1EP5w.png" /></figure><p>So Hugo has seen the index.html in the layouts, and generated the static site from that. Hugo knows that when you place an index.html in the root of the layouts folder, that it should use that as the home page of the site.</p><p>But what use is this? We could use Hugo as just a web server, but it’s so much more powerful than that, so in the next part of this series, we will explore some of those features, and continue towards building a simple no-theme Markdown blog.</p><p>In the next part we will see how to use the “title” variable from the config.toml in our home page using the Go template language, and also how to set up partials for a site header and footer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6136ed50464" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create your own shortcodes in Hugo]]></title>
            <link>https://medium.com/@the.agent/how-to-create-your-own-shortcodes-in-hugo-72b48454c47e?source=rss-4c4965dbdc64------2</link>
            <guid isPermaLink="false">https://medium.com/p/72b48454c47e</guid>
            <category><![CDATA[hugo]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[static-site-generator]]></category>
            <category><![CDATA[shortcode]]></category>
            <dc:creator><![CDATA[Mike Harrison]]></dc:creator>
            <pubDate>Sun, 05 Jan 2020 05:21:44 GMT</pubDate>
            <atom:updated>2020-01-05T05:21:44.526Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NRppAxvGYUMps43E" /><figcaption>Photo by <a href="https://unsplash.com/@kellysikkema?utm_source=medium&amp;utm_medium=referral">Kelly Sikkema</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In Hugo, shortcodes are a way of inserting a snippet of HTML into a page from your markdown. Hugo comes with some <a href="https://gohugo.io/content-management/shortcodes/#use-hugos-built-in-shortcodes">built-in shortcodes</a> that you can use to embed videos, images, tweets, etc.</p><p>First let’s look at how to embed a YouTube video into a blog post using a shortcode:</p><pre>---</pre><pre>title: &quot;Embed a Youtube video&quot;</pre><pre>date: 2020-01-01T14:17:03-05:00</pre><pre>draft: false</pre><pre>---</pre><pre>{{&lt; youtube w7Ft2ymGmfc &gt;}}</pre><p>So in the body of the post, all we have to do is surround our shortcode with {{ }}, and put the shortcode and any parameters inside the &lt; &gt; .</p><p>So in our example, this will cause the HTML to embed the YouTube video to be inserted into the page. This prevents us from having to insert HTML directly into the markdown content.</p><p>This HTML is what gets inserted into the page by the shortcode:</p><pre>&lt;div style=”position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;”&gt; <br>   &lt;iframe src=”<a href="https://www.youtube.com/embed/w7Ft2ymGmfc">https://www.youtube.com/embed/w7Ft2ymGmfc</a>&quot; style=”position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;” allowfullscreen title=”YouTube Video”&gt;<br>   &lt;/iframe&gt;<br>&lt;/div&gt;</pre><p>This is what the post looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*KKGTN4IwpBbjXV5s8A5SOg.png" /></figure><h3>How to create a custom shortcode</h3><p>So how do we create our own custom shortcode? It’s fairly easy. All we have to do is create a shortcodes folder under the layouts folder, and put the HTML file that we want the shortcode to insert in the folder. The name of the HTML file (without the .html extension) will be the name of the custom shortcode.</p><p>For example, we want to create a contact page shortcode. This is my HTML file called form-contact.html, place it in the layouts/shortcodes folder of your Hugo project:</p><pre>&lt;form class=”contact-form-wrapper” accept-charset=”UTF-8&quot; action=”{{ .Get “action” }}” method=”POST” role=”form”&gt;</pre><pre>&lt;label for=”name”&gt;Name&lt;/label&gt;</pre><pre>&lt;input type=”text” id=”name” name=”name” required placeholder=”Your Name” aria-labelledby=”name”/&gt;</pre><pre>&lt;br&gt;</pre><pre>&lt;label for=”email”&gt;Email Address&lt;/label&gt;</pre><pre>&lt;input type=”email” id=”email” name=”email” required placeholder=”Email” aria-labelledby=”email”/&gt;</pre><pre>&lt;br&gt;</pre><pre>&lt;label for=”message”&gt;Message&lt;/label&gt;</pre><pre>&lt;textarea id=”message” name=”message” aria-labelledby=”message”&gt;&lt;/textarea&gt;</pre><pre>&lt;br&gt;</pre><pre>&lt;input type=”submit” value=”Send”/&gt;</pre><pre>&lt;/form&gt;</pre><p>Notice the action=”{{ .Get “action” }}” in the first line. This is how we pass parameters to our shortcode. Hugo will execute the .Get command and place the parameter you pass in the action attribute.</p><p>Then in the contact.md file in the content folder, we call the shortcode:</p><pre>---</pre><pre>title: &quot;Contact&quot;</pre><pre>draft: false</pre><pre>---</pre><pre>Please send me feedback using the contact form below:</pre><pre>{{&lt; form-contact action=”your website here&quot; &gt;}}</pre><p>You just put the website that is processing your form submission in the “your website here”. For example, it could be a link to wherever your forms processor is. I’m using <a href="http://formspree.io/">formspree.io</a> to process my contact form.</p><p>We probably want some CSS to format the contact form. We can put custom css in the static folder. This may vary by theme, the Terminal theme looks for static/style.css for custom CSS styles. Check your theme documentation to see what your theme expects.</p><p>The CSS for my form:</p><pre>.contact-form-wrapper {</pre><pre>width: 75%;</pre><pre>padding: 30px;</pre><pre>background: grey;</pre><pre>}</pre><pre>.contact-form-wrapper input[type=text], input[type=email], textarea {</pre><pre>width: 100%;</pre><pre>margin-bottom: 15px;</pre><pre>padding: 5px;</pre><pre>}</pre><pre>.contact-form-wrapper textarea {</pre><pre>height: 20vh;</pre><pre>}</pre><pre>input[type=submit] {</pre><pre>font-family: Fira Code,Monaco,Consolas,Ubuntu Mono,monospace;</pre><pre>font-size: 1.25em;</pre><pre>width: 20%;</pre><pre>padding: 10px;</pre><pre>}</pre><pre>input[type=submit]:hover {</pre><pre>background-color: orange;</pre><pre>}</pre><p>And when the page is rendered by Hugo, it looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/1*78FM4ZxA8QkjcFP9F-kB7Q.png" /></figure><h3>Summary</h3><p>This is just the simplest method of using shortcodes, there are more advanced features, so please see the Hugo documentation below for more details on all the ways you can use them.</p><h3>Hugo Shortcodes Reference:</h3><ul><li><a href="https://gohugo.io/content-management/shortcodes/">Using Shortcodes</a></li><li><a href="https://gohugo.io/content-management/shortcodes/#use-hugos-built-in-shortcodes">Built-in Shortcodes</a></li><li><a href="https://gohugo.io/templates/shortcode-templates/">Create Custom Shortcodes</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72b48454c47e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 5 Books to Learn JAMStack Development in 2020]]></title>
            <link>https://medium.com/@the.agent/top-5-books-to-learn-jamstack-development-in-2020-deceded6024c?source=rss-4c4965dbdc64------2</link>
            <guid isPermaLink="false">https://medium.com/p/deceded6024c</guid>
            <category><![CDATA[hugo]]></category>
            <category><![CDATA[jamstack]]></category>
            <category><![CDATA[static-site-generator]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[books]]></category>
            <dc:creator><![CDATA[Mike Harrison]]></dc:creator>
            <pubDate>Sat, 04 Jan 2020 03:26:26 GMT</pubDate>
            <atom:updated>2020-01-04T03:26:26.597Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aq3ivGIHGxoh0vzH" /><figcaption>Photo by <a href="https://unsplash.com/@micheile?utm_source=medium&amp;utm_medium=referral">Micheile Henderson @micheile010 // Visual Stories [nl]</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>JAMStack</h3><p>The <a href="https://jamstack.org/">JAMStack</a> stands for “JavaScript, APIs, and Markup”. Sites built with static site generators such as Jekyll, Gatsby and Hugo and hosted on S3 buckets or Netlify are what the typical JAMStack site is built with. They generally use markdown to format their content, and HTML, CSS, and JavaScript to develop the site. Hugo has its own templating language, and Gatsby uses React.</p><p>But JAMStack sites need not just be confined to static site generators. Any site built with the basics of HTML, CSS and JavaScript qualifies as a JAMStack project.</p><p>To quote the official JAMStack website, “ The thing that they all have in common is that they don’t depend on a web server.” JAMStack sites can be hosted on serverless environments such as S3 buckets.</p><p>So with that in mind, here are my top 5 books to get you started on the JAMStack.</p><h3>Top 5 Books</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/303/1*f4WHTdtDj9Gzp6ew_Z3JAQ.jpeg" /></figure><p><a href="https://www.netlify.com/oreilly-jamstack/"><strong>Modern Web Development on the JAMStack</strong></a> by Mathias Biilmann &amp; Phil Hawksworth, O’Reilly</p><p>This is an e-book available for free, click the link above to get your copy. It gives an overview of the JAMStack, provides advice for setting up your project, gives you the best practices for developing JAMStack sites, and includes a case study of a site that was converted to Hugo from a monolithic (PHP/Ruby) backend. The case study gives a detailed account of the design decisions that were made and how they went about converting the site. This book is a must read.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*KSqO0ZanGGagfjK7mw3rhQ.jpeg" /></figure><p><a href="https://www.manning.com/books/serverless-applications-with-node-js"><strong>Serverless Applications with Node.js</strong></a> by Slobodan Stojanović and Aleksandar Simović, Manning</p><p>This book covers the API part of the JAMStack. It covers how to develop serverless APIs using Node.js on AWS Lambda using <a href="https://claudiajs.com/">Claudia.js</a>. This book is great, it has 15 chapters that goes through the process of setting up a pizza delivery API. Claudia is an amazing tool that allows you to deploy Node.js Express services to AWS Lambda, and it makes it very easy, it does all the hard work of setting up everything on AWS, all you have to do is invoke simple commands from the command line. The book gives an overview of Lambda, how it works, and how Claudia.js works with it. There is a chapter on JavaScript promises, as Claudia works with promises. It shows you how to do user authentication, connecting to backend services such as MongoDB and DynamoDB, using payment services, developing chat bots, migrating existing applications to Claudia, and ends with 2 case studies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*AvZu9KYakNUCgGwjTGe1fQ.jpeg" /></figure><p><a href="https://www.manning.com/books/css-in-depth"><strong>CSS in Depth</strong></a> by Keith J. Grant, Manning</p><p>This book is a massive, almost 500 page tome on everything CSS. It steps you through the basics of CSS, responsive design, flexbox, grid layout, and advanced topics such as transitions, animations. It also has an appendix with a reference of CSS Selectors and an appendix on using CSS processors Sass and PostCSS. This book is a valuable reference, you can use it to look up the answer for all of your CSS needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*UWrGjBzg-_keK4SbQJV2Mg.jpeg" /></figure><p><a href="https://www.manning.com/books/web-design-playground"><strong>Web Design Playground</strong></a> by Paul McFedries, Manning</p><p>This book is good for getting started learning HTML and CSS, it covers all the basics of web development, structuring your HTML, styling with CSS, designing responsive sites, typography and polishing your site so it looks good. It includes 4 chapters that have projects you can follow along with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*JO7S3dDI30WpjBP8BGSsew.jpeg" /></figure><p><a href="https://www.manning.com/books/hugo-in-action"><strong>Hugo in Action</strong></a> by Atishay Jain, Manning</p><p>There’s a caveat on this one. This book is not done yet, it’s one of Manning’s MEAP’s, which means it’s still in development but you can purchase early access to the book. The book teaches you how to develop static sites with Hugo. There are only 5 chapters available at this time, which cover the beginning basics of how to use Hugo and the Go template language. Future chapters will cover creating your own Hugo themes, using JavaScript, using APIs and building your own APIs. The full book is supposed to be available spring 2020, it is looking promising as a good Hugo resource.</p><h3>Summary</h3><p>The JAMStack is an exciting new way to develop websites that are secure, fast, and easy to maintain. With these books you are sure to be able to become proficient developing any type of website you want.</p><p>Let me know your favorite resources for JAMStack development in the comments below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=deceded6024c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why you should use Hugo for your blog in 2020]]></title>
            <link>https://medium.com/@the.agent/why-you-should-use-hugo-for-your-blog-in-2020-2756b9cf50c4?source=rss-4c4965dbdc64------2</link>
            <guid isPermaLink="false">https://medium.com/p/2756b9cf50c4</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[netlify]]></category>
            <category><![CDATA[static-site]]></category>
            <category><![CDATA[jamstack]]></category>
            <category><![CDATA[hugo]]></category>
            <dc:creator><![CDATA[Mike Harrison]]></dc:creator>
            <pubDate>Thu, 02 Jan 2020 23:58:23 GMT</pubDate>
            <atom:updated>2020-01-02T23:58:23.870Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RrrkGryuobs9vPwx" /><figcaption>Photo by <a href="https://unsplash.com/@24ameer?utm_source=medium&amp;utm_medium=referral">Ameer Basheer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Yesterday I achieved my first goal of 2020. I got my blog site up and running on Hugo. Check it out <a href="https://www.agent-blog.com/">here</a>.</p><p>It is hosted on Netlify, deployment is from a private Github repository and I am using <a href="http://forestry.io/">Forestry </a>as my CMS (content management system). The cost? $12 for the domain name from Namecheap.com and thats it! Netlify and Forestry both have free tiers.</p><p><a href="http://gohugo.io/">Hugo </a>is a static site generator that has a wide variety of templates available, similar to Wordpress. It is not as user friendly as Wordpress, though, and requires some basic knowledge of how to use it and how it works. To be fully capable of modifying themes to add functionality, you should know basic HTML, CSS, JavaScript and the Hugo templating language. Fortunately there is a <a href="https://www.youtube.com/watch?v=qtIqKaDlqXo&amp;list=PLLAZ4kZ9dFpOnyRlyS-liKL5ReHDcj4G3">great series</a> on YouTube by Mike Dane about Hugo and it is a 23 part series of short videos that starts from scratch and by the end you will have enough knowledge to build your Hugo site.</p><p>For this site I am using the <a href="https://themes.gohugo.io/hugo-theme-terminal/">Terminal </a>theme. The functionality I added that didn’t come with the theme is a contact page that I copied out of the <a href="https://themes.gohugo.io/gohugo-theme-ananke/">Ananke </a>theme to make a custom shortcode template. The other customization I did was to add a new front matter variable called showcomments which will control if the comments should show up on a page or not. This required just a basic Hugo If statement around the comments partial template and adding the variable to the default archetype markdown file. I wanted comments to ahow on only blog posts and not on the about or contact pages. By default the comments were showing on every page.</p><p>And the last thing I did was set up Google analytics, by creating a partial that uses Hugo’s internal template for Google analytics and adding that to the “baseof.html” template, which is the base HTML for the entire site.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hMDDY6Tm8VuuFtmn" /><figcaption>Photo by <a href="https://unsplash.com/@emilymorter?utm_source=medium&amp;utm_medium=referral">Emily Morter</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Why Hugo?</h3><p>So why use Hugo, why not just use Wordpress and set up a site in 5 minutes with zero coding?</p><p>Well, the answer is, Wordpress may seem easy to use at first, but you’ve got to keep it updated, and there are hackers trying to break into your site, and there is malware targeted at it, and sometimes you get weird errors like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/1*3DqKTOO67mWEmYO62_ZIxA.png" /></figure><p>And you may not even realize your site is giving people that error, it may seem fine to you, the site owner, who logs in as the admin. And who knows how to fix it? Not me.</p><p>And Wordpress is overkill for a simple blog. Way overkill. And they can be slow, because they have a backend of MySQL and PHP that need to run on a server.</p><p>And I’m kind of sick of the Wordpress ecosystem where it seems everyone is always trying to sell you a premium theme or plugin.</p><p>In contrast, Hugo sites are static, which means they are fast. Lightning fast. And there is zero backend, so all you need is a webserver to host it. And they can even be hosted on Amazon S3 storage for a fully “serverless” site.</p><p>And you can write your own “plugins” by using HTML, CSS, JavaScript and the Hugo template language. You can use JavaScript to call APIs if you need backend services.</p><p>And with a headless CMS such as <a href="http://forestry.io/">Forestry.io</a>, you can get a user-friendly front end to update the content on your website. Once you get it set up, you can simply add new pages and blog posts in Forestry, click Save, and it automatically re-deploys to Netlify to rebuild the site.</p><p>And Hugo sites are more secure, there is no backend server to break into. And with today’s security issues, it’s a relief to not have to worry about someone hacking into your blog.</p><p>In future posts, I will go through step by step what’s involved in setting up a Hugo site.</p><h3>List of Resources for Hugo</h3><ul><li><a href="https://gohugo.io/documentation/">Hugo documentation</a></li><li><a href="https://www.youtube.com/watch?v=qtIqKaDlqXo&amp;list=PLLAZ4kZ9dFpOnyRlyS-liKL5ReHDcj4G3">Mike Dane’s Hugo tutorial</a></li><li><a href="http://forestry.io/">forestry.io</a></li><li><a href="https://jamstack.org/">JAMStack</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2756b9cf50c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Make 2020 the year of blogging!]]></title>
            <link>https://medium.com/@the.agent/make-2020-the-year-of-blogging-d80c68eb1c7a?source=rss-4c4965dbdc64------2</link>
            <guid isPermaLink="false">https://medium.com/p/d80c68eb1c7a</guid>
            <category><![CDATA[blogging]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[oracle-cloud]]></category>
            <dc:creator><![CDATA[Mike Harrison]]></dc:creator>
            <pubDate>Wed, 01 Jan 2020 17:38:39 GMT</pubDate>
            <atom:updated>2020-01-01T17:38:39.125Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9rbGTv0CtqvksT3v" /><figcaption>Photo by <a href="https://unsplash.com/@emmamatthews?utm_source=medium&amp;utm_medium=referral">Emma Matthews Digital Content Production</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A goal I have had was to start a blog, but I never seem to get around to it. So this year, my goal is to post one blog article per day, so that at the end of the year, I will have 365 articles posted. I am posting first on Medium, because there is zero work required to start a blog, simply to have an account. I have had this account for a while, but not used it to post articles.</p><p>My goals for this year:</p><ul><li>365 blog articles on Medium, no minimum length.</li><li>create a website with Hugo, the static site generator. I will mirror my articles there, as Hugo is designed around creating a blog.</li></ul><h3>Topics</h3><p>I will post on any topic that interests me, mostly on tech and web development, but I reserve the right to go way off topic. I might post book reviews, or recommend articles or websites.</p><p>One reason for writing a blog is to use it to catalog things you have learned, so that when you forget what you’ve done, you can look back and see how you solved that problem.</p><p>Here’s a list of possibilities:</p><ul><li><a href="https://www.oracle.com/ca-en/middleware/application-integration/">Oracle Integration Cloud</a> (an amazing platform to create web services, but geared toward large companies due to it’s exorbitant pricing)</li><li><a href="https://gohugo.io/">Hugo</a>, the static site generator. How I use it, and what I’ve learned about it, as I learn it.</li><li><a href="https://developer.mozilla.org/en-US/docs/Learn/JavaScript">JavaScript </a>— using it to enhance your web pages</li><li><a href="https://nodejs.org/en/">Node.js </a>— Creating your own API</li><li>Front end frameworks, eg. <a href="https://reactjs.org/">React </a>(the only one I know right now)</li><li><a href="https://unity.com/">Unity </a>— the game engine that makes it easy to create your own video games</li><li>Homeschooling — we homeschool our daughter using the <a href="https://www.robinsoncurriculum.com/rc/homeschool-curriculum-excellence/">Robinson Curriculum</a></li></ul><h3>Why I Am Anonymous</h3><p>The company I work for does not want me to write about anything I work on. They want me only to blog internally to the company and not share my knowledge with anyone outside. This would be an extremely limited audience for the topics I write about.</p><p>This goes against what I believe in, I believe knowledge should be freely shared with all, it’s not something to be hoarded for the benefit of just one company.</p><p>So I have set this account with an anonymous name, so I can write freely on any topic.</p><p>So who’s with me? Give me your comments, what are your goals on Medium this year or just goal in general? Let’s make 2020 the year of blogging!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d80c68eb1c7a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>