ce7673e40ced16b8bfe252372cd20c2bd9baa355
commit ce7673e40ced16b8bfe252372cd20c2bd9baa355
Author: Simon Watson <spw01@protonmail.com>
Date: Fri Jan 21 16:27:02 2022 -0500

Blog workflow post

diff --git a/2022-01-21-blog-workflow.html b/2022-01-21-blog-workflow.html
new file mode 100644
index 0000000..1137519
--- /dev/null
+++ b/2022-01-21-blog-workflow.html
@@ -0,0 +1,358 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
+<head>
+<!-- 2022-01-21 Fri 16:24 -->
+<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<title>‎</title>
+<meta name="generator" content="Org mode" />
+<style type="text/css">
+ <!--/*--><![CDATA[/*><!--*/
+ .title { text-align: center;
+ margin-bottom: .2em; }
+ .subtitle { text-align: center;
+ font-size: medium;
+ font-weight: bold;
+ margin-top:0; }
+ .todo { font-family: monospace; color: red; }
+ .done { font-family: monospace; color: green; }
+ .priority { font-family: monospace; color: orange; }
+ .tag { background-color: #eee; font-family: monospace;
+ padding: 2px; font-size: 80%; font-weight: normal; }
+ .timestamp { color: #bebebe; }
+ .timestamp-kwd { color: #5f9ea0; }
+ .org-right { margin-left: auto; margin-right: 0px; text-align: right; }
+ .org-left { margin-left: 0px; margin-right: auto; text-align: left; }
+ .org-center { margin-left: auto; margin-right: auto; text-align: center; }
+ .underline { text-decoration: underline; }
+ #postamble p, #preamble p { font-size: 90%; margin: .2em; }
+ p.verse { margin-left: 3%; }
+ pre {
+ border: 1px solid #ccc;
+ box-shadow: 3px 3px 3px #eee;
+ padding: 8pt;
+ font-family: monospace;
+ overflow: auto;
+ margin: 1.2em;
+ }
+ pre.src {
+ position: relative;
+ overflow: auto;
+ padding-top: 1.2em;
+ }
+ pre.src:before {
+ display: none;
+ position: absolute;
+ background-color: white;
+ top: -10px;
+ right: 10px;
+ padding: 3px;
+ border: 1px solid black;
+ }
+ pre.src:hover:before { display: inline; margin-top: 14px;}
+ /* Languages per Org manual */
+ pre.src-asymptote:before { content: 'Asymptote'; }
+ pre.src-awk:before { content: 'Awk'; }
+ pre.src-C:before { content: 'C'; }
+ /* pre.src-C++ doesn't work in CSS */
+ pre.src-clojure:before { content: 'Clojure'; }
+ pre.src-css:before { content: 'CSS'; }
+ pre.src-D:before { content: 'D'; }
+ pre.src-ditaa:before { content: 'ditaa'; }
+ pre.src-dot:before { content: 'Graphviz'; }
+ pre.src-calc:before { content: 'Emacs Calc'; }
+ pre.src-emacs-lisp:before { content: 'Emacs Lisp'; }
+ pre.src-fortran:before { content: 'Fortran'; }
+ pre.src-gnuplot:before { content: 'gnuplot'; }
+ pre.src-haskell:before { content: 'Haskell'; }
+ pre.src-hledger:before { content: 'hledger'; }
+ pre.src-java:before { content: 'Java'; }
+ pre.src-js:before { content: 'Javascript'; }
+ pre.src-latex:before { content: 'LaTeX'; }
+ pre.src-ledger:before { content: 'Ledger'; }
+ pre.src-lisp:before { content: 'Lisp'; }
+ pre.src-lilypond:before { content: 'Lilypond'; }
+ pre.src-lua:before { content: 'Lua'; }
+ pre.src-matlab:before { content: 'MATLAB'; }
+ pre.src-mscgen:before { content: 'Mscgen'; }
+ pre.src-ocaml:before { content: 'Objective Caml'; }
+ pre.src-octave:before { content: 'Octave'; }
+ pre.src-org:before { content: 'Org mode'; }
+ pre.src-oz:before { content: 'OZ'; }
+ pre.src-plantuml:before { content: 'Plantuml'; }
+ pre.src-processing:before { content: 'Processing.js'; }
+ pre.src-python:before { content: 'Python'; }
+ pre.src-R:before { content: 'R'; }
+ pre.src-ruby:before { content: 'Ruby'; }
+ pre.src-sass:before { content: 'Sass'; }
+ pre.src-scheme:before { content: 'Scheme'; }
+ pre.src-screen:before { content: 'Gnu Screen'; }
+ pre.src-sed:before { content: 'Sed'; }
+ pre.src-sh:before { content: 'shell'; }
+ pre.src-sql:before { content: 'SQL'; }
+ pre.src-sqlite:before { content: 'SQLite'; }
+ /* additional languages in org.el's org-babel-load-languages alist */
+ pre.src-forth:before { content: 'Forth'; }
+ pre.src-io:before { content: 'IO'; }
+ pre.src-J:before { content: 'J'; }
+ pre.src-makefile:before { content: 'Makefile'; }
+ pre.src-maxima:before { content: 'Maxima'; }
+ pre.src-perl:before { content: 'Perl'; }
+ pre.src-picolisp:before { content: 'Pico Lisp'; }
+ pre.src-scala:before { content: 'Scala'; }
+ pre.src-shell:before { content: 'Shell Script'; }
+ pre.src-ebnf2ps:before { content: 'ebfn2ps'; }
+ /* additional language identifiers per "defun org-babel-execute"
+ in ob-*.el */
+ pre.src-cpp:before { content: 'C++'; }
+ pre.src-abc:before { content: 'ABC'; }
+ pre.src-coq:before { content: 'Coq'; }
+ pre.src-groovy:before { content: 'Groovy'; }
+ /* additional language identifiers from org-babel-shell-names in
+ ob-shell.el: ob-shell is the only babel language using a lambda to put
+ the execution function name together. */
+ pre.src-bash:before { content: 'bash'; }
+ pre.src-csh:before { content: 'csh'; }
+ pre.src-ash:before { content: 'ash'; }
+ pre.src-dash:before { content: 'dash'; }
+ pre.src-ksh:before { content: 'ksh'; }
+ pre.src-mksh:before { content: 'mksh'; }
+ pre.src-posh:before { content: 'posh'; }
+ /* Additional Emacs modes also supported by the LaTeX listings package */
+ pre.src-ada:before { content: 'Ada'; }
+ pre.src-asm:before { content: 'Assembler'; }
+ pre.src-caml:before { content: 'Caml'; }
+ pre.src-delphi:before { content: 'Delphi'; }
+ pre.src-html:before { content: 'HTML'; }
+ pre.src-idl:before { content: 'IDL'; }
+ pre.src-mercury:before { content: 'Mercury'; }
+ pre.src-metapost:before { content: 'MetaPost'; }
+ pre.src-modula-2:before { content: 'Modula-2'; }
+ pre.src-pascal:before { content: 'Pascal'; }
+ pre.src-ps:before { content: 'PostScript'; }
+ pre.src-prolog:before { content: 'Prolog'; }
+ pre.src-simula:before { content: 'Simula'; }
+ pre.src-tcl:before { content: 'tcl'; }
+ pre.src-tex:before { content: 'TeX'; }
+ pre.src-plain-tex:before { content: 'Plain TeX'; }
+ pre.src-verilog:before { content: 'Verilog'; }
+ pre.src-vhdl:before { content: 'VHDL'; }
+ pre.src-xml:before { content: 'XML'; }
+ pre.src-nxml:before { content: 'XML'; }
+ /* add a generic configuration mode; LaTeX export needs an additional
+ (add-to-list 'org-latex-listings-langs '(conf " ")) in .emacs */
+ pre.src-conf:before { content: 'Configuration File'; }
+
+ table { border-collapse:collapse; }
+ caption.t-above { caption-side: top; }
+ caption.t-bottom { caption-side: bottom; }
+ td, th { vertical-align:top; }
+ th.org-right { text-align: center; }
+ th.org-left { text-align: center; }
+ th.org-center { text-align: center; }
+ td.org-right { text-align: right; }
+ td.org-left { text-align: left; }
+ td.org-center { text-align: center; }
+ dt { font-weight: bold; }
+ .footpara { display: inline; }
+ .footdef { margin-bottom: 1em; }
+ .figure { padding: 1em; }
+ .figure p { text-align: center; }
+ .equation-container {
+ display: table;
+ text-align: center;
+ width: 100%;
+ }
+ .equation {
+ vertical-align: middle;
+ }
+ .equation-label {
+ display: table-cell;
+ text-align: right;
+ vertical-align: middle;
+ }
+ .inlinetask {
+ padding: 10px;
+ border: 2px solid gray;
+ margin: 10px;
+ background: #ffffcc;
+ }
+ #org-div-home-and-up
+ { text-align: right; font-size: 70%; white-space: nowrap; }
+ textarea { overflow-x: auto; }
+ .linenr { font-size: smaller }
+ .code-highlighted { background-color: #ffff00; }
+ .org-info-js_info-navigation { border-style: none; }
+ #org-info-js_console-label
+ { font-size: 10px; font-weight: bold; white-space: nowrap; }
+ .org-info-js_search-highlight
+ { background-color: #ffff00; color: #000000; font-weight: bold; }
+ .org-svg { width: 90%; }
+ /*]]>*/-->
+</style>
+<script type="text/javascript">
+// @license magnet:?xt=urn:btih:e95b018ef3580986a04669f1b5879592219e2a7a&dn=public-domain.txt Public Domain
+<!--/*--><![CDATA[/*><!--*/
+ function CodeHighlightOn(elem, id)
+ {
+ var target = document.getElementById(id);
+ if(null != target) {
+ elem.classList.add("code-highlighted");
+ target.classList.add("code-highlighted");
+ }
+ }
+ function CodeHighlightOff(elem, id)
+ {
+ var target = document.getElementById(id);
+ if(null != target) {
+ elem.classList.remove("code-highlighted");
+ target.classList.remove("code-highlighted");
+ }
+ }
+ /*]]>*///-->
+// @license-end
+</script>
+</head>
+<body>
+<div id="content">
+<div id="table-of-contents">
+<h2>Table of Contents</h2>
+<div id="text-table-of-contents">
+<ul>
+<li><a href="#org48501fe">1. My Blog/Phlog Workflow</a></li>
+</ul>
+</div>
+</div>
+<div id="outline-container-org48501fe" class="outline-2">
+<h2 id="org48501fe"><span class="section-number-2">1</span> My Blog/Phlog Workflow</h2>
+<div class="outline-text-2" id="text-1">
+<p>
+I only started really writing anything down with intention for myself
+in the past few months. I'm slowly trying to ramp up and write a bit more.
+</p>
+
+<p>
+I'm a very talking oriented person if that makes sense, and I find it
+difficult to write things that I think are coherent. I also tend to be
+a rambler in person who constantly over-explains. This also doesn't
+translate well to writing.
+</p>
+
+<p>
+To that point, I think part of why I talk so much is because it helps
+me organize my thoughts. They rattle around in my head in an incoherent
+jumbled mess and spewing them out helps me to hear what they actually are.
+</p>
+
+<p>
+However, it's not always easy to talk to people. Maybe people aren't around,
+maybe they don't want to talk, maybe they do but not about what you want
+to talk about, etc etc.
+</p>
+
+<p>
+To that end I figured I should try and write more things, even if no one
+ever reads them, just so I can practice that act of thoughtfulness and
+trying to codify my thoughts.
+</p>
+
+<p>
+Preamble aside, I figured I'd write something about my blog posting
+infrastructure which may be of some interest. I have two places I
+post my blogs:
+</p>
+
+<ul class="org-ul">
+<li><a href="https://spwbk.site">https://spwbk.site</a></li>
+<li><a href="gopher://chate.io">gopher://chate.io</a></li>
+</ul>
+
+<p>
+Because the files that represent the blog posts for these platforms
+are pretty different, I needed a way to be able to write a post in a
+comfortable, ergonomic way and then "deploy" it to the various places
+I want it to be visible from. Here's what I came up with:
+</p>
+
+<p>
+I write my blog posts in Emacs, in org-mode. I like org-mode and use it
+for other stuff, and it's an environment I'm comfortable with. Additionally,
+I can export org mode documents as HTML, which helps a lot.
+</p>
+
+<p>
+So after I'm done writing my post, I save my .org file, and then export it
+to HTML.
+</p>
+
+<p>
+From there I do some minor edits on the HTML manually. This is just to update
+some <style> tags for the HTML version so that it's not so utiltarian. If
+I understand correctly, there should be a way to configure org so that it
+puts my <style> values in, but I'm not sure how to do that yet. Something
+to look into later.
+</p>
+
+<p>
+After I tweak the HTML file, I now have 2 files:
+</p>
+<ul class="org-ul">
+<li>blog<sub>post.org</sub></li>
+<li>blog<sub>post.pretty.html</sub></li>
+</ul>
+
+<p>
+Typically I still have both of these open in buffers in Emacs, so I
+wrote a little elisp shell wrapper to shell out to rclone, which posts
+the file in the buffer to a bucket in BackBlaze B2.
+</p>
+
+<p>
+Every few minutes on my respective servers, a little script runs that
+gets any new blog posts.
+</p>
+
+<p>
+On the HTTP server it grabs the .pretty.html file, and on the gopher
+server it grabs the .org file, and places them in their respective places.
+</p>
+
+<p>
+Once this is done, the script uses <a href="https://ntfy.sh">https://ntfy.sh</a> to send me a notification
+that the files have been deployed.
+</p>
+
+<p>
+To review, the process essentially looks like this:
+</p>
+
+<p>
+Write in emacs -> save as .org file -> export .org as .html -> modify
+html <style> -> upload to B2 -> wait a few minutes.
+</p>
+
+<p>
+I can do all of my blogging from Emacs without ever having to touch anything
+else, and I get a notification on my phone to confirm that the blogs have
+been uploaded successfully!
+</p>
+
+<p>
+I really like this system, and because it feels easy to use for myself,
+I find myself blogging more and more!
+</p>
+
+<p>
+Thanks for reading!
+</p>
+</div>
+</div>
+</div>
+<div id="postamble" class="status">
+<p class="date">Created: 2022-01-21 Fri 16:24</p>
+<p class="validation"><a href="https://validator.w3.org/check?uri=referer">Validate</a></p>
+</div>
+</body>
+</html>
diff --git a/2022-01-21-blog-workflow.org b/2022-01-21-blog-workflow.org
new file mode 100644
index 0000000..0fa17f3
--- /dev/null
+++ b/2022-01-21-blog-workflow.org
@@ -0,0 +1,77 @@
+* My Blog/Phlog Workflow
+
+ I only started really writing anything down with intention for myself
+ in the past few months. I'm slowly trying to ramp up and write a bit more.
+
+ I'm a very talking oriented person if that makes sense, and I find it
+ difficult to write things that I think are coherent. I also tend to be
+ a rambler in person who constantly over-explains. This also doesn't
+ translate well to writing.
+
+ To that point, I think part of why I talk so much is because it helps
+ me organize my thoughts. They rattle around in my head in an incoherent
+ jumbled mess and spewing them out helps me to hear what they actually are.
+
+ However, it's not always easy to talk to people. Maybe people aren't around,
+ maybe they don't want to talk, maybe they do but not about what you want
+ to talk about, etc etc.
+
+ To that end I figured I should try and write more things, even if no one
+ ever reads them, just so I can practice that act of thoughtfulness and
+ trying to codify my thoughts.
+
+ Preamble aside, I figured I'd write something about my blog posting
+ infrastructure which may be of some interest. I have two places I
+ post my blogs:
+
+ - https://spwbk.site
+ - gopher://chate.io
+
+ Because the files that represent the blog posts for these platforms
+ are pretty different, I needed a way to be able to write a post in a
+ comfortable, ergonomic way and then "deploy" it to the various places
+ I want it to be visible from. Here's what I came up with:
+
+ I write my blog posts in Emacs, in org-mode. I like org-mode and use it
+ for other stuff, and it's an environment I'm comfortable with. Additionally,
+ I can export org mode documents as HTML, which helps a lot.
+
+ So after I'm done writing my post, I save my .org file, and then export it
+ to HTML.
+
+ From there I do some minor edits on the HTML manually. This is just to update
+ some <style> tags for the HTML version so that it's not so utiltarian. If
+ I understand correctly, there should be a way to configure org so that it
+ puts my <style> values in, but I'm not sure how to do that yet. Something
+ to look into later.
+
+ After I tweak the HTML file, I now have 2 files:
+ - blog_post.org
+ - blog_post.pretty.html
+
+ Typically I still have both of these open in buffers in Emacs, so I
+ wrote a little elisp shell wrapper to shell out to rclone, which posts
+ the file in the buffer to a bucket in BackBlaze B2.
+
+ Every few minutes on my respective servers, a little script runs that
+ gets any new blog posts.
+
+ On the HTTP server it grabs the .pretty.html file, and on the gopher
+ server it grabs the .org file, and places them in their respective places.
+
+ Once this is done, the script uses https://ntfy.sh to send me a notification
+ that the files have been deployed.
+
+ To review, the process essentially looks like this:
+
+ Write in emacs -> save as .org file -> export .org as .html -> modify
+ html <style> -> upload to B2 -> wait a few minutes.
+
+ I can do all of my blogging from Emacs without ever having to touch anything
+ else, and I get a notification on my phone to confirm that the blogs have
+ been uploaded successfully!
+
+ I really like this system, and because it feels easy to use for myself,
+ I find myself blogging more and more!
+
+ Thanks for reading!
diff --git a/2022-01-21-blog-workflow.pretty.html b/2022-01-21-blog-workflow.pretty.html
new file mode 100644
index 0000000..392f9fa
--- /dev/null
+++ b/2022-01-21-blog-workflow.pretty.html
@@ -0,0 +1,176 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
+<head>
+<!-- 2022-01-21 Fri 16:24 -->
+<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<title>‎</title>
+<meta name="generator" content="Org mode" />
+<style type="text/css">body{margin:40px
+auto;max-width:900px;line-height:1.6;font-size:18px;color:#444;padding:0
+10px}h1,h2,h3{line-height:1.2}</style>
+<script type="text/javascript">
+// @license magnet:?xt=urn:btih:e95b018ef3580986a04669f1b5879592219e2a7a&dn=public-domain.txt Public Domain
+<!--/*--><![CDATA[/*><!--*/
+ function CodeHighlightOn(elem, id)
+ {
+ var target = document.getElementById(id);
+ if(null != target) {
+ elem.classList.add("code-highlighted");
+ target.classList.add("code-highlighted");
+ }
+ }
+ function CodeHighlightOff(elem, id)
+ {
+ var target = document.getElementById(id);
+ if(null != target) {
+ elem.classList.remove("code-highlighted");
+ target.classList.remove("code-highlighted");
+ }
+ }
+ /*]]>*///-->
+// @license-end
+</script>
+</head>
+<body>
+<div id="content">
+<div id="table-of-contents">
+<h2>Table of Contents</h2>
+<div id="text-table-of-contents">
+<ul>
+<li><a href="#org48501fe">1. My Blog/Phlog Workflow</a></li>
+</ul>
+</div>
+</div>
+<div id="outline-container-org48501fe" class="outline-2">
+<h2 id="org48501fe"><span class="section-number-2">1</span> My Blog/Phlog Workflow</h2>
+<div class="outline-text-2" id="text-1">
+<p>
+I only started really writing anything down with intention for myself
+in the past few months. I'm slowly trying to ramp up and write a bit more.
+</p>
+
+<p>
+I'm a very talking oriented person if that makes sense, and I find it
+difficult to write things that I think are coherent. I also tend to be
+a rambler in person who constantly over-explains. This also doesn't
+translate well to writing.
+</p>
+
+<p>
+To that point, I think part of why I talk so much is because it helps
+me organize my thoughts. They rattle around in my head in an incoherent
+jumbled mess and spewing them out helps me to hear what they actually are.
+</p>
+
+<p>
+However, it's not always easy to talk to people. Maybe people aren't around,
+maybe they don't want to talk, maybe they do but not about what you want
+to talk about, etc etc.
+</p>
+
+<p>
+To that end I figured I should try and write more things, even if no one
+ever reads them, just so I can practice that act of thoughtfulness and
+trying to codify my thoughts.
+</p>
+
+<p>
+Preamble aside, I figured I'd write something about my blog posting
+infrastructure which may be of some interest. I have two places I
+post my blogs:
+</p>
+
+<ul class="org-ul">
+<li><a href="https://spwbk.site">https://spwbk.site</a></li>
+<li><a href="gopher://chate.io">gopher://chate.io</a></li>
+</ul>
+
+<p>
+Because the files that represent the blog posts for these platforms
+are pretty different, I needed a way to be able to write a post in a
+comfortable, ergonomic way and then "deploy" it to the various places
+I want it to be visible from. Here's what I came up with:
+</p>
+
+<p>
+I write my blog posts in Emacs, in org-mode. I like org-mode and use it
+for other stuff, and it's an environment I'm comfortable with. Additionally,
+I can export org mode documents as HTML, which helps a lot.
+</p>
+
+<p>
+So after I'm done writing my post, I save my .org file, and then export it
+to HTML.
+</p>
+
+<p>
+From there I do some minor edits on the HTML manually. This is just to update
+some <style> tags for the HTML version so that it's not so utiltarian. If
+I understand correctly, there should be a way to configure org so that it
+puts my <style> values in, but I'm not sure how to do that yet. Something
+to look into later.
+</p>
+
+<p>
+After I tweak the HTML file, I now have 2 files:
+</p>
+<ul class="org-ul">
+<li>blog<sub>post.org</sub></li>
+<li>blog<sub>post.pretty.html</sub></li>
+</ul>
+
+<p>
+Typically I still have both of these open in buffers in Emacs, so I
+wrote a little elisp shell wrapper to shell out to rclone, which posts
+the file in the buffer to a bucket in BackBlaze B2.
+</p>
+
+<p>
+Every few minutes on my respective servers, a little script runs that
+gets any new blog posts.
+</p>
+
+<p>
+On the HTTP server it grabs the .pretty.html file, and on the gopher
+server it grabs the .org file, and places them in their respective places.
+</p>
+
+<p>
+Once this is done, the script uses <a href="https://ntfy.sh">https://ntfy.sh</a> to send me a notification
+that the files have been deployed.
+</p>
+
+<p>
+To review, the process essentially looks like this:
+</p>
+
+<p>
+Write in emacs -> save as .org file -> export .org as .html -> modify
+html <style> -> upload to B2 -> wait a few minutes.
+</p>
+
+<p>
+I can do all of my blogging from Emacs without ever having to touch anything
+else, and I get a notification on my phone to confirm that the blogs have
+been uploaded successfully!
+</p>
+
+<p>
+I really like this system, and because it feels easy to use for myself,
+I find myself blogging more and more!
+</p>
+
+<p>
+Thanks for reading!
+</p>
+</div>
+</div>
+</div>
+<div id="postamble" class="status">
+<p class="date">Created: 2022-01-21 Fri 16:24</p>
+</div>
+</body>
+</html>