commit 2dbde701ab7a54426869374a005083ddece09206
parent e7130ba3d3b1225fda91a3924ea86af740a13000
Author: Jake Bauer <jbauer@paritybit.ca>
Date: Mon, 30 Dec 2019 02:05:27 -0500
Publish new blog post
Diffstat:
5 files changed, 133 insertions(+), 2 deletions(-)
diff --git a/pages/blog.md b/pages/blog.md
@@ -18,6 +18,7 @@ Below you can find links to things that I have posted:
### 2019
<ul>
+ <li>2019-12-30 <a href="blog/automating-publishing">Automating the Publishing of Articles</a></li>
<li>2019-12-21 <a href="blog/arguing-effectively">How to Argue
Effectively</a></li>
<li>2019-12-20 <a href="blog/difficulty-of-privacy-education">The
diff --git a/pages/blog/automating-publishing.md b/pages/blog/automating-publishing.md
@@ -0,0 +1,42 @@
+## Automating the Publishing of Articles
+
+[//]: # "There was too much manual work involved in publishing things to my website so I decided to automate it. Read on to learn how."
+
+[//]: # "base.min.css"
+
+[//]: #
+
+<b>Written By:</b> Jake Bauer |
+ <b>Posted:</b> 2019-12-30 |
+ <b>Last Updated:</b> 2019-12-30
+
+If you're seeing this, it means my automation script worked perfectly.
+
+There was too much manual work involved in publishing things to my website.
+
+In order to publish a blog post, guide, or project to my site I had to:
+
+* Write the RSS feed entry manually.
+* Copy the RSS feed entry from the sitewide feed to the relevant other feed
+ (blog-, project-, or guide-specific feeds).
+* Manually add an entry under the What's New heading on the [home page](/)
+ and delete the oldest entry.
+* Manually add an entry under the relevant category page (i.e. [/blog](/blog),
+ [/guides](/guides), or [/projects](/projects)).
+* Manually compile and upload each of these pages.
+
+Since all of that is relatively easy to automate, I went ahead and wrote [a
+script](https://git.sr.ht/~jbauer/paritybit.ca/tree/master/publish) to do all of
+that for me. All I have to do now is call `./publish <type> <file>` and
+everything listed above is done for me.
+
+Not only does this get rid of a lot of potential for error in the process, it
+also makes it a lot easier for me to post things which will enable me to post
+more frequently without having to worry about all the work that came along with
+posting something new.
+
+The script took me about 3-4 hours to brainstorm, write, realise that I was
+doing things inefficiently, look some stuff up on Stackoverflow, rewrite,
+realise that I wanted it to do more than just make RSS feeds (which is all I
+planned to automate at first), brainstorm some more, look some more stuff up on
+Stackoverflow, write some more, and then test and tweak.
diff --git a/pages/home.md b/pages/home.md
@@ -21,6 +21,8 @@ projects on the site.
src="/img/feed-icon.png" width="15" height="15" alt="Click for RSS"/>
</a>
</div>
+2019-12-30 <a href="blog/automating-publishing">New Blog Post: Automating the Publishing of Articles</a>
+
2019-12-21 <a href="blog/arguing-effectively">New Blog Post: How to Argue Effectively</a>
@@ -30,8 +32,6 @@ projects on the site.
2019-11-26 <a href="guides/using-rm-with-trash">New Guide: Using the "rm" Command with Trash</a>
-2019-11-23 <a href="blog/china">New Blog Post: China</a>
-
### What is a Parity Bit?
It is a bit (in the 1's and 0's sense) used in checking for errors in digital
diff --git a/public/feeds/blog-feed.xml b/public/feeds/blog-feed.xml
@@ -7,6 +7,50 @@
<description>The latest blog posts from paritybit.ca.
</description>
<item>
+ <title>New Blog Post: Automating the Publishing of Articles</title>
+ <link>https://www.paritybit.ca/blog/automating-publishing</link>
+ <guid>https://www.paritybit.ca/blog/automating-publishing</guid>
+ <pubDate>Mon, 30 Dec 2019 02:01:37 -0500</pubDate>
+ <description><![CDATA[<h2>Automating the Publishing of Articles</h2>
+
+<p><b>Written By:</b> Jake Bauer |
+ <b>Posted:</b> 2019-12-30 |
+ <b>Last Updated:</b> 2019-12-30</p>
+
+<p>If you're seeing this, it means my automation script worked perfectly.</p>
+
+<p>There was too much manual work involved in publishing things to my website.</p>
+
+<p>In order to publish a blog post, guide, or project to my site I had to:</p>
+
+<ul>
+<li>Write the RSS feed entry manually.</li>
+<li>Copy the RSS feed entry from the sitewide feed to the relevant other feed
+(blog-, project-, or guide-specific feeds).</li>
+<li>Manually add an entry under the What's New heading on the <a href="/">home page</a>
+and delete the oldest entry.</li>
+<li>Manually add an entry under the relevant category page (i.e. <a href="/blog">/blog</a>,
+<a href="/guides">/guides</a>, or <a href="/projects">/projects</a>).</li>
+<li>Manually compile and upload each of these pages.</li>
+</ul>
+
+<p>Since all of that is relatively easy to automate, I went ahead and wrote <a href="https://git.sr.ht/~jbauer/paritybit.ca/tree/master/publish">a
+script</a> to do all of
+that for me. All I have to do now is call <code>./publish <type> <file></code> and
+everything listed above is done for me.</p>
+
+<p>Not only does this get rid of a lot of potential for error in the process, it
+also makes it a lot easier for me to post things which will enable me to post
+more frequently without having to worry about all the work that came along with
+posting something new.</p>
+
+<p>The script took me about 3-4 hours to brainstorm, write, realise that I was
+doing things inefficiently, look some stuff up on Stackoverflow, rewrite,
+realise that I wanted it to do more than just make RSS feeds (which is all I
+planned to automate at first), brainstorm some more, look some more stuff up on
+Stackoverflow, write some more, and then test and tweak.</p>]]></description>
+</item>
+<item>
<title>New Blog Post: How to Argue Effectively</title>
<link>https://www.paritybit.ca/blog/arguing-effectively</link>
<guid>https://www.paritybit.ca/blog/arguing-effectively</guid>
diff --git a/public/feeds/sitewide-feed.xml b/public/feeds/sitewide-feed.xml
@@ -7,6 +7,50 @@
<description>The feed that covers all notable additions, updates, announcements,
and other changes for the entire paritybit.ca website.</description>
<item>
+ <title>New Blog Post: Automating the Publishing of Articles</title>
+ <link>https://www.paritybit.ca/blog/automating-publishing</link>
+ <guid>https://www.paritybit.ca/blog/automating-publishing</guid>
+ <pubDate>Mon, 30 Dec 2019 02:01:37 -0500</pubDate>
+ <description><![CDATA[<h2>Automating the Publishing of Articles</h2>
+
+<p><b>Written By:</b> Jake Bauer |
+ <b>Posted:</b> 2019-12-30 |
+ <b>Last Updated:</b> 2019-12-30</p>
+
+<p>If you're seeing this, it means my automation script worked perfectly.</p>
+
+<p>There was too much manual work involved in publishing things to my website.</p>
+
+<p>In order to publish a blog post, guide, or project to my site I had to:</p>
+
+<ul>
+<li>Write the RSS feed entry manually.</li>
+<li>Copy the RSS feed entry from the sitewide feed to the relevant other feed
+(blog-, project-, or guide-specific feeds).</li>
+<li>Manually add an entry under the What's New heading on the <a href="/">home page</a>
+and delete the oldest entry.</li>
+<li>Manually add an entry under the relevant category page (i.e. <a href="/blog">/blog</a>,
+<a href="/guides">/guides</a>, or <a href="/projects">/projects</a>).</li>
+<li>Manually compile and upload each of these pages.</li>
+</ul>
+
+<p>Since all of that is relatively easy to automate, I went ahead and wrote <a href="https://git.sr.ht/~jbauer/paritybit.ca/tree/master/publish">a
+script</a> to do all of
+that for me. All I have to do now is call <code>./publish <type> <file></code> and
+everything listed above is done for me.</p>
+
+<p>Not only does this get rid of a lot of potential for error in the process, it
+also makes it a lot easier for me to post things which will enable me to post
+more frequently without having to worry about all the work that came along with
+posting something new.</p>
+
+<p>The script took me about 3-4 hours to brainstorm, write, realise that I was
+doing things inefficiently, look some stuff up on Stackoverflow, rewrite,
+realise that I wanted it to do more than just make RSS feeds (which is all I
+planned to automate at first), brainstorm some more, look some more stuff up on
+Stackoverflow, write some more, and then test and tweak.</p>]]></description>
+</item>
+<item>
<title>New Blog Post: How to Argue Effectively</title>
<link>https://www.paritybit.ca/blog/arguing-effectively</link>
<guid>https://www.paritybit.ca/blog/arguing-effectively</guid>
