summaryrefslogtreecommitdiff
path: root/posts/hello.html
diff options
context:
space:
mode:
authorMatthew Kosarek <matt.kosarek@canonical.com>2025-06-08 15:35:46 -0400
committerMatthew Kosarek <matt.kosarek@canonical.com>2025-06-08 15:35:46 -0400
commitcc42af143f76b2ed8f8c488dfc6c6b4a1bf28c5c (patch)
treed04f322a0c7a8afe41af4feb117153ed944af5be /posts/hello.html
parent8ef7ef367b5865796dd9d01c24170479545248ec (diff)
June 2025 updateHEADmaster
Diffstat (limited to 'posts/hello.html')
-rw-r--r--posts/hello.html74
1 files changed, 37 insertions, 37 deletions
diff --git a/posts/hello.html b/posts/hello.html
index 7a62e80..ec10db2 100644
--- a/posts/hello.html
+++ b/posts/hello.html
@@ -26,9 +26,9 @@
</div>
</div>
<div id="content" class="content">
-<div id="outline-container-orgc6f1d20" class="outline-2">
-<h2 id="orgc6f1d20">TLDR</h2>
-<div class="outline-text-2" id="text-orgc6f1d20">
+<div id="outline-container-orgbec5765" class="outline-2">
+<h2 id="orgbec5765">TLDR</h2>
+<div class="outline-text-2" id="text-orgbec5765">
<ul class="org-ul">
<li>Create a new folder</li>
<li>Put <a href="https://raw.githubusercontent.com/mattkae/matthewkosarek-xyz/master/index.css">index.css</a>, <a href="https://raw.githubusercontent.com/mattkae/matthewkosarek-xyz/master/publish.el">publish.el</a>, and <a href="https://github.com/mattkae/matthewkosarek-xyz/blob/master/publish.sh">publish.sh</a> in the folder</li>
@@ -42,9 +42,9 @@
</ul>
</div>
</div>
-<div id="outline-container-orgf0fd8f0" class="outline-2">
-<h2 id="orgf0fd8f0">Introduction</h2>
-<div class="outline-text-2" id="text-orgf0fd8f0">
+<div id="outline-container-orgb717615" class="outline-2">
+<h2 id="orgb717615">Introduction</h2>
+<div class="outline-text-2" id="text-orgb717615">
<p>
I've recently fallen in love with <code>org-mode</code>, specifically when I use it with <a href="https://www.orgroam.com/">org-roam</a>. I find the whole workflow of creating, tagging, and - later on - searching for information on my computer to be very elegant. On top of that, now that I have the time, I want to begin writing blog posts to better work out my thoughts. With both of these things in mind, I am again turning to the universal tool for human prospering: <code>org-mode</code>. This time, I want to see how it can help me turn a simple org file into a blog post on my website. My requirements are:
</p>
@@ -67,9 +67,9 @@ And that's pretty much it for now. Without further ado, let's jump into getting
</p>
</div>
</div>
-<div id="outline-container-orgc203944" class="outline-2">
-<h2 id="orgc203944">Basic HTML File</h2>
-<div class="outline-text-2" id="text-orgc203944">
+<div id="outline-container-org1ccbbae" class="outline-2">
+<h2 id="org1ccbbae">Basic HTML File</h2>
+<div class="outline-text-2" id="text-org1ccbbae">
<p>
As a pilot, we are going to use this org file that I am currently writing (<code>hello.org</code>) as our guinea pig. The goal is to have this org file be our very first blog post.
</p>
@@ -109,9 +109,9 @@ We then do a <code>chmod +x publish.sh</code> to make it an executable and run i
</p>
</div>
</div>
-<div id="outline-container-orgb5be820" class="outline-2">
-<h2 id="orgb5be820">Disabling features that we don't want</h2>
-<div class="outline-text-2" id="text-orgb5be820">
+<div id="outline-container-orga8b7149" class="outline-2">
+<h2 id="orga8b7149">Disabling features that we don't want</h2>
+<div class="outline-text-2" id="text-orga8b7149">
<p>
The next thing will be to remove some of the generated items that I didn't ask for, namely the table of contents, author, section numbers, creation time stamp, and the validation link.
</p>
@@ -140,9 +140,9 @@ The next thing will be to remove some of the generated items that I didn't ask f
</div>
</div>
</div>
-<div id="outline-container-org8316009" class="outline-2">
-<h2 id="org8316009">Styling &amp; Code Highlighting</h2>
-<div class="outline-text-2" id="text-org8316009">
+<div id="outline-container-org0d2b040" class="outline-2">
+<h2 id="org0d2b040">Styling &amp; Code Highlighting</h2>
+<div class="outline-text-2" id="text-org0d2b040">
<p>
Next thing on our list is custom styling. This can be achieved by first installing the <code>htmlize</code> package from <code>melpa</code> / <code>elpa</code>. The EmacsWiki describes this as "a package for exporting the contents of an Emacs buffer to HTML while respecting display properties such as colors, fonts, underlining, invisibility, etc" (<a href="https://www.emacswiki.org/emacs/Htmlize">reference</a>). If used "out-of-the-box", the buffer will be exported to HTML with all of the styles inlined (e.g. if you underline something in your org file, you will generate a <code>&lt;span style="text-decoration: underline"&gt;...&lt;/span&gt;</code>). However, we are more interested in styling everything by ourselves: we don't want <code>htmlize</code> making assumptions about what underlining means to us! Luckily, <code>htmlize</code> gives us the option to export with class names instead of inline styles so that we can specify each style for ourselves.
</p>
@@ -312,9 +312,9 @@ If we run the publish again, we can see that we have full styling on our code sn
</p>
</div>
</div>
-<div id="outline-container-org227c647" class="outline-2">
-<h2 id="org227c647">Images</h2>
-<div class="outline-text-2" id="text-org227c647">
+<div id="outline-container-org338b6ac" class="outline-2">
+<h2 id="org338b6ac">Images</h2>
+<div class="outline-text-2" id="text-org338b6ac">
<p>
Our first two criteria have been met! Next on the list is solving images. As an example, let's use this <a href="file:///_posts/assets/squirrel.jpg">squirrel image</a> that I found online with an open source license. The ideal situation would be:
</p>
@@ -359,16 +359,16 @@ So what's the fix here? Well, we have two options, but I am going to go with the
That's all there is to it! There are simpler ways as well, but that should do it:
</p>
-<div id="org567fa83" class="figure">
+<div id="org70c1fa6" class="figure">
<p><img src="/_posts/assets/squirrel.jpg" alt="squirrel.jpg" width="300" />
</p>
<p><span class="figure-number">Figure 1: </span>A Cute Squirrel</p>
</div>
</div>
</div>
-<div id="outline-container-orgf513ceb" class="outline-2">
-<h2 id="orgf513ceb">Creation Date</h2>
-<div class="outline-text-2" id="text-orgf513ceb">
+<div id="outline-container-org396f39b" class="outline-2">
+<h2 id="org396f39b">Creation Date</h2>
+<div class="outline-text-2" id="text-org396f39b">
<p>
Let's add the creation date below the title next. To start, we will modify the publish command to remove the title (<code>:with-title nil</code>) and, in its place, show a preamble bit of HTML that contains a formatted <code>div</code> with the title and the "last modified" span.z
</p>
@@ -427,9 +427,9 @@ Note that the downside of this is that the created date will change whenever you
</p>
</div>
</div>
-<div id="outline-container-org9eb5e7e" class="outline-2">
-<h2 id="org9eb5e7e">Generating the Directory</h2>
-<div class="outline-text-2" id="text-org9eb5e7e">
+<div id="outline-container-orgb732174" class="outline-2">
+<h2 id="orgb732174">Generating the Directory</h2>
+<div class="outline-text-2" id="text-orgb732174">
<p>
For every org file in my <code>_posts</code> folder, I would like to create a link to the generated HTML file at the <code>/posts.html</code> page of my website. You can think of this as the "directory" of all posts. My criteria is:
</p>
@@ -489,9 +489,9 @@ If you open the <code>sitemap.html</code> file in your browser, you will see a b
From here, you may customize it however you like. The following are my customizations.
</p>
</div>
-<div id="outline-container-org17e71ed" class="outline-3">
-<h3 id="org17e71ed">Sitemap Title</h3>
-<div class="outline-text-3" id="text-org17e71ed">
+<div id="outline-container-org7ed3bbf" class="outline-3">
+<h3 id="org7ed3bbf">Sitemap Title</h3>
+<div class="outline-text-3" id="text-org7ed3bbf">
<p>
I changed the title to "Matthew's Blog Posts".
</p>
@@ -513,9 +513,9 @@ I changed the title to "Matthew's Blog Posts".
</div>
</div>
</div>
-<div id="outline-container-orgc81a45b" class="outline-3">
-<h3 id="orgc81a45b">Format blog entries in the list</h3>
-<div class="outline-text-3" id="text-orgc81a45b">
+<div id="outline-container-org5647f3c" class="outline-3">
+<h3 id="org5647f3c">Format blog entries in the list</h3>
+<div class="outline-text-3" id="text-org5647f3c">
<p>
I like to include the creation date on the blog posts. To do this, we can use <code>org-publish-find-property</code> to find the date property of the org file. Afterward, we can format a string that includes our formatted timestamp and the <code>org-publish-sitemap-default-entry</code>, which is just a link with the title of the post.
</p>
@@ -536,9 +536,9 @@ I like to include the creation date on the blog posts. To do this, we can use <c
</div>
</div>
</div>
-<div id="outline-container-org1c07067" class="outline-2">
-<h2 id="org1c07067">Tags &amp; Filtering</h2>
-<div class="outline-text-2" id="text-org1c07067">
+<div id="outline-container-org10b4190" class="outline-2">
+<h2 id="org10b4190">Tags &amp; Filtering</h2>
+<div class="outline-text-2" id="text-org10b4190">
<p>
I use <a href="https://www.orgroam.com/">Org-roam</a> for all of my note-taking and, in the next blog post, I plan to demonstrate how I will hook up my Org-roam note-taking workflow to my blogging. In the meantime, just know that we can add tags to the top of our org files like this:
</p>
@@ -758,9 +758,9 @@ Finally, let's append the following to <code>posts/posts.css</code> so that our
</div>
</div>
</div>
-<div id="outline-container-org8a7a547" class="outline-2">
-<h2 id="org8a7a547">Conclusion</h2>
-<div class="outline-text-2" id="text-org8a7a547">
+<div id="outline-container-org32ee7b9" class="outline-2">
+<h2 id="org32ee7b9">Conclusion</h2>
+<div class="outline-text-2" id="text-org32ee7b9">
<p>
There are many more customizations that I plan to do on this system in the future, but I plan to leave this for now so that I can actually get to some blogging. I will proofread and fix my mistakes as time goes on, but this should be a good jumping off point for anyone interested in using org for their own blogging system.
</p>