diff options
Diffstat (limited to 'posts')
| -rw-r--r-- | posts/berg.md | 4 | ||||
| -rw-r--r-- | posts/dump.md | 2 | ||||
| -rw-r--r-- | posts/html-dark-mode.md | 6 | ||||
| -rw-r--r-- | posts/openring.md | 2 | ||||
| -rw-r--r-- | posts/pblog.md | 4 | ||||
| -rw-r--r-- | posts/rss-click.md | 4 | ||||
| -rw-r--r-- | posts/rss-hacks.md | 4 | ||||
| -rw-r--r-- | posts/seven-years.md | 8 | ||||
| -rw-r--r-- | posts/shinobi-website.md | 4 | ||||
| -rw-r--r-- | posts/slabtop.md | 2 | ||||
| -rw-r--r-- | posts/srht2.md | 6 | ||||
| -rw-r--r-- | posts/use-text-not-icons.md | 2 |
12 files changed, 24 insertions, 24 deletions
diff --git a/posts/berg.md b/posts/berg.md index d87cea3..88c9e00 100644 --- a/posts/berg.md +++ b/posts/berg.md @@ -2,13 +2,13 @@ 2022-07-29 -I recently switched the [pblog](https://pblog.bt.ht) project repo over from Sourcehut to Codeberg (mostly for UX reasons) and it got me looking into [Codeberg Pages](https://codeberg.page). It seemed like a cleaner approach to host my personal blog on the same platform I planned to also share the source code. +I recently switched the [pblog](https://pblog.btxx.org) project repo over from Sourcehut to Codeberg (mostly for UX reasons) and it got me looking into [Codeberg Pages](https://codeberg.page). It seemed like a cleaner approach to host my personal blog on the same platform I planned to also share the source code. I decided to share the setup process here since I couldn't find a straightforward guide explaining everything required to get going. So, let's dig in. ## Create the Repos -**Disclaimer**: My personal blog uses [pblog](https://pblog.bt.ht), so although these instructions will be catered towards that SSG the same concept *should* apply for any other generator (Jekyll, Hugo, Next, etc.). +**Disclaimer**: My personal blog uses [pblog](https://pblog.btxx.org), so although these instructions will be catered towards that SSG the same concept *should* apply for any other generator (Jekyll, Hugo, Next, etc.). The first step is to create the main repo that would house the core files of `pblog`. Then we need to make a separate repo simply called `pages`. This second project is where all the generated "static" files get rendered. diff --git a/posts/dump.md b/posts/dump.md index 4a3dd13..fc44040 100644 --- a/posts/dump.md +++ b/posts/dump.md @@ -76,7 +76,7 @@ This very website you're reading is built and run off of [SourceHut Pages](https - Customizable build settings - Support open source software! -**Sidenote:** If you're interested in setting up a SSG (such as Jekyll or Hugo) through SourceHut, feel free to [fork this very website as a starting point](https://git.sr.ht/~bt/bt.ht). I also wrote up how to publish/build a Jekyll site on SourceHut in a [separate post](/srht) if you wish to see all the nitty-gritty details. +**Sidenote:** If you're interested in setting up a SSG (such as Jekyll or Hugo) through SourceHut, feel free to [fork this very website as a starting point](https://git.sr.ht/~bt/btxx.org). I also wrote up how to publish/build a Jekyll site on SourceHut in a [separate post](/srht) if you wish to see all the nitty-gritty details. #### WordPress diff --git a/posts/html-dark-mode.md b/posts/html-dark-mode.md index 0d94def..f5a25b6 100644 --- a/posts/html-dark-mode.md +++ b/posts/html-dark-mode.md @@ -3,7 +3,7 @@ 2023-04-11 I wrote an article back in 2021 called [The Lazy Developer's Dark -Mode](https://bt.ht/lazy-dev-dark-mode/) where I explained how to implement +Mode](https://btxx.org/posts/lazy-dev-dark-mode/) where I explained how to implement a very basic "dark mode" by using the `prefers-color-scheme` CSS attribute. This stills works perfectly fine, and in fact there is a cleaner variation of this created by *jacksonchen666*: [These 3 Lines of CSS Will Give You Dark Mode for Free](https://jacksonchen666.com/posts/2023-04-09/13-47-16/). @@ -20,10 +20,10 @@ Add that line inside the `head` tags on your HTML files and you're good to go. ## Minor Caveat I mentioned this same issue on the official [barf blog -post](https://barf.bt.ht/dark-mode/) but it doesn't hurt to repeat it here. +post](https://barf.btxx.org/dark-mode/) but it doesn't hurt to repeat it here. Safari still has minor ahref / link color issue when defaulting to browser dark mode. If supporting that browser is a deal-breaker for you, I suggest looking -at my [hacky solution](https://bt.ht/safari-default-dark-mode/). +at my [hacky solution](https://btxx.org/posts/safari-default-dark-mode/). Hopefully this helps others to add dark mode to their existing websites and projects with minimal effort! diff --git a/posts/openring.md b/posts/openring.md index cbb6c3e..2af4a2a 100644 --- a/posts/openring.md +++ b/posts/openring.md @@ -121,7 +121,7 @@ Now you just need to decide where you want your `openring` feed outputs to rende This next step is only for those using [SourceHut Pages](https://srht.site) to build and host their websites. If you use a different platform (ie Netlify, Vercel, GitHub Pages) the concept should be similar but will most likely require more tweaking on your end. Just a fair warning. -I won't go into great detail about build script for SourceHut Pages, but feel free to take a look at my [very own build file for this website](https://git.sr.ht/~bt/bt.ht/tree/master/item/.build.yml). That *should* work out-of-the-box for most standard Jekyll websites. (Just be sure to edit with your own details!) +I won't go into great detail about build script for SourceHut Pages, but feel free to take a look at my [very own build file for this website](https://git.sr.ht/~bt/btxx.orgtree/master/item/.build.yml). That *should* work out-of-the-box for most standard Jekyll websites. (Just be sure to edit with your own details!) **That's it**. You now have links to blogs you enjoy that will update with each build. Of course, the "latest" blog posts shown will become out-of-date if you don't blog (or at least re-build your website) on a regular basis. But for me, I see this as a good motivator to keep pushing out content! diff --git a/posts/pblog.md b/posts/pblog.md index 7deedbe..9e7e895 100644 --- a/posts/pblog.md +++ b/posts/pblog.md @@ -4,13 +4,13 @@ If you're an RSS subscriber, I've probably blown up your feed reader (again). This seems to be an on-going theme with this blog. I can't help it. -This website now uses my *new* Pandoc-based static blog generator: [pblog](https://pblog.bt.ht). I won't go into great detail about it's features (or lack thereof) - if you're interested in that, check out the ["Introducing pblog" article](https://pblog.bt.ht/blog/pblog-intro.html). +This website now uses my *new* Pandoc-based static blog generator: [pblog](https://pblog.btxx.org). I won't go into great detail about it's features (or lack thereof) - if you're interested in that, check out the ["Introducing pblog" article](https://pblog.btxx.org/blog/pblog-intro.html). The bigger question is, "Why the change?" ## Where's the Love for "Shinobi"? -Switching over to `pblog` wasn't caused by a dislike of using [Shinobi](https://shinobi.bt.ht). In fact, I still really enjoy the work flow that that plain-text focused SSG provides. The main issues that popped up for my own blog was *accessibility* and *poor user experience*. +Switching over to `pblog` wasn't caused by a dislike of using [Shinobi](https://shinobi.btxx.org). In fact, I still really enjoy the work flow that that plain-text focused SSG provides. The main issues that popped up for my own blog was *accessibility* and *poor user experience*. I had multiple readers reach out and mention poor rendering of content in their RSS reader of choice. That's kind of a **big deal**. I test that project as best I can with my limited access to all available RSS readers - but I can only test so much. It became one of those "Well, it works on my machine!" meme. So instead of spending an untold amount of time debugging every RSS reader known to man, I figured my best bet was to render things as `HTML`. diff --git a/posts/rss-click.md b/posts/rss-click.md index d63fa79..ff41300 100644 --- a/posts/rss-click.md +++ b/posts/rss-click.md @@ -36,8 +36,8 @@ In the instance above I am rendering the entry title as a clickable element whic ## Live Example -In a supported browser, you can see the code in action here: https://pblog.bt.ht/feed.xml +In a supported browser, you can see the code in action here: https://pblog.btxx.org/feed.xml That's really all there is to it. -[^1]: https://shinobi.bt.ht/posts/patch-3.txt +[^1]: https://shinobi.btxx.org/posts/patch-3.txt diff --git a/posts/rss-hacks.md b/posts/rss-hacks.md index 31e9631..3d1890c 100644 --- a/posts/rss-hacks.md +++ b/posts/rss-hacks.md @@ -47,7 +47,7 @@ Everything worked perfectly and the RSS was still valid! I've ported these changes over to this blog to perform some "in the wild" testing. You can see the custom feed list in your supported browser by visiting: -[https://pblog.bt.ht/feed.xml](https://pblog.bt.ht/feed.xml) +[https://pblog.btxx.org/feed.xml](https://pblog.btxx.org/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[^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. @@ -55,7 +55,7 @@ As for the shinobi project itself, I have not merged these updates into the main If you're interested in more updates and details about the shinobi project itself, feel free to sub to that specific feed below. This post was more focused on hacking RSS parameters that happened to involve shinobi, but in the future all updates specific to the project will be posted there: -[https://shinobi.bt.ht/feed.xml](https://shinobi.bt.ht/feed.xml) +[https://shinobi.btxx.org/feed.xml](https://shinobi.btxx.org/feed.xml) [^1]: https://shinobi.website/ [^2]: https://shinobi.website/posts/patch-1.txt diff --git a/posts/seven-years.md b/posts/seven-years.md index f1c67ca..ea5ebf8 100644 --- a/posts/seven-years.md +++ b/posts/seven-years.md @@ -16,10 +16,10 @@ I originally started blogging on `bradleytaunt.com` using WordPress, but since t - Hugo - Blot - Static HTML/CSS -- [PHPetite](https://phpetite.bt.ht) -- [Shinobi](https://shinobi.bt.ht) -- [pblog](https://pblog.bt.ht) -- [barf](https://barf.bt.ht) *Currently using!* +- [PHPetite](https://phpetite.btxx.org) +- [Shinobi](https://shinobi.btxx.org) +- [pblog](https://pblog.btxx.org) +- [barf](https://barf.btxx.org) *Currently using!* **Personal:** diff --git a/posts/shinobi-website.md b/posts/shinobi-website.md index 6b377d6..646013c 100644 --- a/posts/shinobi-website.md +++ b/posts/shinobi-website.md @@ -2,7 +2,7 @@ 2022-05-13 -**Update 2023**: this website is now built with [barf](https://barf.bt.ht) +**Update 2024**: this website is now built with [wruby](https://wruby.btxx.org) - - - @@ -14,7 +14,7 @@ But before we get into greater details about the switch, let me first introduce Instead of repeating myself in this post, feel free to read up about the project at the official site: -[https://shinobi.bt.ht](https://shinobi.bt.ht) +[https://shinobi.btxx.org](https://shinobi.btxx.org) 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] diff --git a/posts/slabtop.md b/posts/slabtop.md index 9fa035b..dc7032e 100644 --- a/posts/slabtop.md +++ b/posts/slabtop.md @@ -28,7 +28,7 @@ Removing the entire top lid was easier than I initially thought it would be. The ## Ditching Alpine for Debian -I love Alpine Linux. It's normally my [go-to distro](https://as.bt.ht) (paired with dwm) for most of my laptop devices. Unfortunately, I find tiling window managers a slight pain to use on larger, 4K displays. I also wanted this slabtop to "just work", instead of needing to fiddle around with WiFi, `xrandr`, audio etc. Not to mention that Debian is rock solid stable. Defaulting to the XFCE DE was a no-brainer as well since this device is somewhat *old*. +I love Alpine Linux. It's normally my go-to distro (paired with dwm) for most of my laptop devices. Unfortunately, I find tiling window managers a slight pain to use on larger, 4K displays. I also wanted this slabtop to "just work", instead of needing to fiddle around with WiFi, `xrandr`, audio etc. Not to mention that Debian is rock solid stable. Defaulting to the XFCE DE was a no-brainer as well since this device is somewhat *old*.  diff --git a/posts/srht2.md b/posts/srht2.md index b894970..2c48296 100644 --- a/posts/srht2.md +++ b/posts/srht2.md @@ -8,9 +8,9 @@ It has taken a little bit longer than I anticipated, but I have finally started - [Vanilla CSS](https://vanillacss.com) - [The 1MB Club](https://1mb.club) -- [pblog](https://pblog.bt.ht) -- [shinobi](https://shinobi.bt.ht) -- [Web Audit](https://audit.bt.ht) +- [pblog](https://pblog.btxx.org) +- [shinobi](https://shinobi.btxx.org) +- [Web Audit](https://audit.btxx.org) ## Still WIP diff --git a/posts/use-text-not-icons.md b/posts/use-text-not-icons.md index 1e52750..0a745f8 100644 --- a/posts/use-text-not-icons.md +++ b/posts/use-text-not-icons.md @@ -38,7 +38,7 @@ Normally, the inclusion of a hamburger menu is indicative of an overly complex a New features are great, but stop dumping so much of it behind hidden, unintuitive sub-navigation. This design is such a "quick fix" and plagues far too many software apps[^3]. Both desktop computers and mobile devices allow users to *scroll*, let them. -I've discussed this in further detail here: [Using Hamburger Menus? Try Sausage Links](https://bt.ht/hamburger-menu-alternative/) +I've discussed this in further detail here: [Using Hamburger Menus? Try Sausage Links](https://btxx.org/posts/hamburger-menu-alternative/) ## But what of the "advanced" users? |