From bf359e1412ff8a39c411a9ab5e13e7cc17987e6b Mon Sep 17 00:00:00 2001 From: Bradley Taunt Date: Wed, 3 Jul 2024 11:28:53 -0400 Subject: More footnote cleanup --- posts/My_Text_Editor_Is_Not_Open_Source.md | 1 - posts/jekyll-sourcehut.md | 59 ++++++++++++++++-------------- posts/minor-website-changes.md | 2 +- posts/paid-mac-apps.md | 2 +- posts/rss-hacks.md | 8 ++-- posts/schools.md | 8 ++-- posts/self-hosted-blogs.md | 4 +- posts/shinobi-website.md | 6 +-- 8 files changed, 45 insertions(+), 45 deletions(-) diff --git a/posts/My_Text_Editor_Is_Not_Open_Source.md b/posts/My_Text_Editor_Is_Not_Open_Source.md index 76b05f0..497cfa3 100644 --- a/posts/My_Text_Editor_Is_Not_Open_Source.md +++ b/posts/My_Text_Editor_Is_Not_Open_Source.md @@ -55,5 +55,4 @@ I should be very clear about something: this post *is not an advertisement*. I h BTW if anyone from SublimeHQ happens to come across this post: PLEASE look into building a "native" version of Sublime Text for FreeBSD/OpenBSD. I (and many others) would be forever grateful! [^1]: Sublime does mention copyright since 2006... - [^2]: Not the pre-packaged Microsoft version diff --git a/posts/jekyll-sourcehut.md b/posts/jekyll-sourcehut.md index 8485324..5ae7196 100644 --- a/posts/jekyll-sourcehut.md +++ b/posts/jekyll-sourcehut.md @@ -38,28 +38,29 @@ In order to have your Jekyll site build and push the correct files live, you wil To make things easier, you can copy the build file below (remember to use your *own* information for usernames, git repo naming etc): - - image: debian/stable - oauth: pages.sr.ht/PAGES:RW - packages: - - ruby-full - - ruby-dev - environment: - site: yourusername.srht.site - sources: - - https://git.sr.ht/~yourusername/your-repo-name - tasks: - - install-bundler: | - sudo gem install bundler - - build: | - cd your-repo-name - bundle install - bundle exec jekyll build - - package: | - cd your-repo-name/_site - tar -cvz . > ../../site.tar.gz - - upload: | - acurl -f https://pages.sr.ht/publish/$site -Fcontent=@site.tar.gz +~~~sh +image: debian/stable +oauth: pages.sr.ht/PAGES:RW +packages: +- ruby-full +- ruby-dev +environment: +site: yourusername.srht.site +sources: +- https://git.sr.ht/~yourusername/your-repo-name +tasks: +- install-bundler: | + sudo gem install bundler +- build: | + cd your-repo-name + bundle install + bundle exec jekyll build +- package: | + cd your-repo-name/_site + tar -cvz . > ../../site.tar.gz +- upload: | + acurl -f https://pages.sr.ht/publish/$site -Fcontent=@site.tar.gz +~~~ Save this file as `.build.yml` and place it in the root directory of your Jekyll source code. @@ -72,15 +73,17 @@ If you're like me and want to use your own custom domain - have no fear! This pr First, add a new A Record through your domain provider: - - @ IN A 173.195.146.139 +~~~sh +@ IN A 173.195.146.139 +~~~ Then change the following `environment` parameter inside your existing `.build.yml` file: - - environment: - site: yourcustomdomain.com +~~~sh +environment: +site: yourcustomdomain.com +~~~ And that's it - custom domain set! If you run into any issues check out the [official documentation on custom domains](https://srht.site/custom-domains). @@ -91,6 +94,6 @@ Hopefully this helps to streamline the process for others to host their static s Even low-effort support for open-source products (like where you host your static site or FOSS projects) can go a long way. Just some food for thought. -
+--- [^1]: Thanks to [McSinyx](https://cnx.srht.site/) for pointing out that the repo used for creating your website can be named anything (instead of defaulting to your sourcehut username) diff --git a/posts/minor-website-changes.md b/posts/minor-website-changes.md index cb3d7d0..49922ed 100644 --- a/posts/minor-website-changes.md +++ b/posts/minor-website-changes.md @@ -16,7 +16,7 @@ But overtime I came to somewhat dislike[^1] it and set out to change it. I explain this on my updated [about page](/about) but I will mention it again here: -**tdarb**[^2] is simply my first name and last initial spelt backwards – Brad T. Mind blowing, right? +tdarb[^2] is simply my first name and last initial spelt backwards – Brad T. Mind blowing, right? I've switched over to this naming convention to avoid having such a random "phrase" domain name while at the same time having a little more fun than just *mylegalname.com*. I also am a sucker for `.org` TLDs (although I don't know why). diff --git a/posts/paid-mac-apps.md b/posts/paid-mac-apps.md index 2b0eaae..3f0b1c5 100644 --- a/posts/paid-mac-apps.md +++ b/posts/paid-mac-apps.md @@ -46,6 +46,6 @@ URL: [https://panic.com/transmit/](https://panic.com/transmit/) I know this list only includes 3 applications, but that's truly all the ones I've spent money on. If in the future I happen to purchase any others I will be sure to update this post accordingly. -[^1]: Free & open source software +[^1]: Free and open source software diff --git a/posts/rss-hacks.md b/posts/rss-hacks.md index a5d354d..31e9631 100644 --- a/posts/rss-hacks.md +++ b/posts/rss-hacks.md @@ -2,9 +2,9 @@ 2022-05-23 -In my spare time I've been further tinkering (hopefully for the better) with my humble Shinobi Website[^0] script. The most recent update in `patch-1` came with a solid amount of QoL improvements. If you're interested, I wrote about it on the official Shinobi blog[^1]. +In my spare time I've been further tinkering (hopefully for the better) with my humble Shinobi Website[^1] script. The most recent update in `patch-1` came with a solid amount of QoL improvements. If you're interested, I wrote about it on the official Shinobi blog[^2]. -The next feature I wanted to tackle was designing a custom layout for the XML files directly in the browser. I was greatly inspired to create something similar to Len Falken's main directory listing[^2], since that blog was one of the original inspirations for Shinobi. I'm not able to copy what's there though, since our feed builds are quite a bit different. +The next feature I wanted to tackle was designing a custom layout for the XML files directly in the browser. I was greatly inspired to create something similar to Len Falken's main directory listing[^3], since that blog was one of the original inspirations for Shinobi. I'm not able to copy what's there though, since our feed builds are quite a bit different. I then proceeded to fall down the XSLT rabbit hole. @@ -19,7 +19,7 @@ My first attempt was to use the available `sort` parameter (in XSL version 1.1+) -This did not work as intended. RSS 2.0 requires that the `pubDate` content is set to comply with the RFC-822 date-time[^3], which shinobi handles perfectly fine. The issue came from the XSL `sort` parameter not honoring this setting across all dates. My best guess is that it struggles to properly organize posts from their "month" parameter, so it sets the posts in order of date in what I refer to as "monthly sections". +This did not work as intended. RSS 2.0 requires that the `pubDate` content is set to comply with the RFC-822 date-time[^4], which shinobi handles perfectly fine. The issue came from the XSL `sort` parameter not honoring this setting across all dates. My best guess is that it struggles to properly organize posts from their "month" parameter, so it sets the posts in order of date in what I refer to as "monthly sections". If anyone knows why this failed to consistently order the posts via `pubDate`, please let me know using the comment link below. I'm far from an XSLT expert and might have overlooked something painfully obvious! @@ -49,7 +49,7 @@ I've ported these changes over to this blog to perform some "in the wild" testin [https://pblog.bt.ht/feed.xml](https://pblog.bt.ht/feed.xml) -As for the shinobi project itself, I have not merged these updates into the main master branch (at the time of publishing this article). They can be found sitting on patch-2[^4]. My plan is to get this merged ASAP once a little more real-world testing is finished and I can include a better "setup/install" section for newcomers. +As for the shinobi project itself, I have not merged these updates into the main master branch (at the time of publishing this article). They can be found sitting on patch-2[^5]. My plan is to get this merged ASAP once a little more real-world testing is finished and I can include a better "setup/install" section for newcomers. ## Shinobi Updates diff --git a/posts/schools.md b/posts/schools.md index 0ea46f9..c16db4c 100644 --- a/posts/schools.md +++ b/posts/schools.md @@ -33,11 +33,11 @@ Heck, you could even have a fleet of Raspberry Pi devices as your main student " ## Security -I briefly mentioned user and network security above but figured it deserved its own section. A great deal of push-back comes from stubborn IT professionals[^0] determined to keep things running on Windows - since this is mostly what they are familiar with. +I briefly mentioned user and network security above but figured it deserved its own section. A great deal of push-back comes from stubborn IT professionals[^1] determined to keep things running on Windows - since this is mostly what they are familiar with. My mother-in-law was an "at-risk" educator for most of her career. She explained to me that their IT department did a major switch over to use BRAND NEW Apple laptops for all the students just before her retirement. I can't even begin to imagine the cost associated with this change. Not to mention the cost of repair for any of these devices when (not if) damaged. -Who the hell is making these decisions? Even worse, who is approving them?! The school board had the opportunity to switch away from Windows devices and decided on Apple? Education reform is greatly needed[^1]. +Who the hell is making these decisions? Even worse, who is approving them?! The school board had the opportunity to switch away from Windows devices and decided on Apple? Education reform is greatly needed[^2]. ## What About The "Job Market" @@ -56,13 +56,13 @@ Another bonus in using fully open source software is the ability for the student So what are these "open source" alternatives? Check out my simple suggestions below: -MS Office Suite ==> LibreOffice Suite[^2] +MS Office Suite ==> LibreOffice Suite[^3] Photoshop ==> GIMP Illustrator ==> Inkscape -IE/Edge ==> Firefox[^3] +IE/Edge ==> Firefox[^4] Coding IDE (optional) ===> vim diff --git a/posts/self-hosted-blogs.md b/posts/self-hosted-blogs.md index ca7ebdd..0a7fbdd 100644 --- a/posts/self-hosted-blogs.md +++ b/posts/self-hosted-blogs.md @@ -21,11 +21,9 @@ These custom self-hosted blogs inspired other developers and designers to create I also believe this inspired people to write better content instead of opting for clickbait garbage in order to get "featured" or boosted promotion on the main blogging platform. But I don't even think that's the worst to come of this mass-migration to a singular blogging platform. -**All[^2] blogs look identical now.** I'm not sure if that was Medium's intention, but either way I personally think it's horrible. The individual personality of most design and development blogs has been completely stripped away. +All[^2] blogs look identical now. I'm not sure if that was Medium's intention, but either way I personally think it's horrible. The individual personality of most design and development blogs has been completely stripped away. Maybe I'm just a salty designer with a narrow-minded, pessimistic view on where our blogging communities seem to be heading - or maybe I just have higher standards. -## Refs - [^1]: the design world of the internet [^2]: by "All" I mean the majority diff --git a/posts/shinobi-website.md b/posts/shinobi-website.md index d95bb91..6b377d6 100644 --- a/posts/shinobi-website.md +++ b/posts/shinobi-website.md @@ -16,11 +16,11 @@ Instead of repeating myself in this post, feel free to read up about the project [https://shinobi.bt.ht](https://shinobi.bt.ht) -To summarize: by using a simple `shell` script I'm able to render all my plain text files (which is now how I solely write my articles) into a structured RSS 2.0 `xml` file. Subscribers can now consume my posts directly in their RSS reader of choice without the need to directly visit the article's URL.[^0] +To summarize: by using a simple `shell` script I'm able to render all my plain text files (which is now how I solely write my articles) into a structured RSS 2.0 `xml` file. Subscribers can now consume my posts directly in their RSS reader of choice without the need to directly visit the article's URL.[^1] ## Why the Change? -I'm a hardcore minimalist at heart and have a tendency to make my own personal projects _leaner_ all the time. I also have been trying my best to find the most refined writing workflow to keep myself posting consistently (and hopefully keeping the quality high). My first iteration towards this step was switching over to hand-coding everything via HTML & CSS[^1]. That worked well - for a very brief time. +I'm a hardcore minimalist at heart and have a tendency to make my own personal projects _leaner_ all the time. I also have been trying my best to find the most refined writing workflow to keep myself posting consistently (and hopefully keeping the quality high). My first iteration towards this step was switching over to hand-coding everything via HTML & CSS[^2]. That worked well - for a very brief time. After recently launching the Shinobi project, I kept toying with the idea of switching my personal website over to use the same format. There was a heavy internal debate about ditching HTML in favour of plain text. What kind of impact would this have on both my site and audience? Would people be pissed about yet _another_ radical change? @@ -48,7 +48,7 @@ Feel free to comment below if you have any suggestions! Preferably one that resp ## Speaking of Comments... -Since the old commenting system[^2] required me to manually add each comment individually, I assumed I would just do the same here. Then I got a hack-y idea. What if I used a mailing list linked through this website's sourcehut project? +Since the old commenting system[^3] required me to manually add each comment individually, I assumed I would just do the same here. Then I got a hack-y idea. What if I used a mailing list linked through this website's sourcehut project? It might not be the most user friendly or sustainable but I think it could be an interesting experiment at the very least! -- cgit v1.2.3-54-g00ecf