_  _ _    _        _              _     _
| \| (_)__| |_  ___| |__ _ ___  _ | |___| |_  _ _  ___ ___ _ _
| .` | / _| ' \/ _ \ / _` (_-< | || / _ \ ' \| ' \(_-</ _ \ ' \
|_|\_|_\__|_||_\___/_\__,_/__/  \__/\___/_||_|_||_/__/\___/_||_|

🔗 Return to homepage

📆 February 25, 2023 | ⏱️ 2 minute read | 🏷️ journal updates

Journal Update 023

What's New

A lot of progress has been made on my journal theme. Let's start with the most exciting stuff, the new features:

• Added inline link support¹ for HTML without breaking Gemini. Inline links are important for getting the most out of both Gemini and the Web.
• Implemented taxonomies² and implemented taxonomy Atom feeds³.
• Implemented terms⁴ and implemented term Atom feeds⁵. This allows for tagging entries. Given the volume of content on my journal and its diversity of subject, tags were becoming necessary for organizational purposes.
• Added quote styling.⁶
• Started versioning the Hugo theme⁷ using Semantic Versioning⁸.

I also made a few major improvements and fixed lots of bugs. Here are the highlights:

• Stopped formatting preformatted text for Gemini.⁹ It sounds trivial, but Hugo templates only support regex for text-manipulation. So the number of efficient solutions was probably limited to just the one chunk-parsing algorithm I designed and implemented.
• Overhauled the CSS¹⁰, making it BEM-compliant.
• Fixed bold/italics removal logic for Gemini.¹¹

The journal itself has seen some important changes:

• Added back I2P support.¹² Since the Tor network has been under a constant DDoS attack for the past few months¹³, it makes sense to mirror everything on I2P in case v3 onions become unreachable.
• Expanded files subdomain access to Gemini.¹⁴
• Painstakingly converted all entry links to inline links. It was tedious, but it needed to be done. It makes Web links look much better.

I think my writing itself has also improved. I think it's become more focused. I often want to put lots of extra details in my journal entries, but I've learned that I need to exclude details to make entries more enjoyable to read. I've learned to take the reader into consideration more while writing.

Future Plans

All the features I wanted to implement in my journal theme have been implemented, except for internationalization. After I implement that, I'll just need to polish up and document the code and it'll be ready for the first official release.

So far I've added a few tags to group entries by topic. I plan to be conservative about adding new tags. Most entries are still untagged and I still need to decide which new tags to add. If anyone has any advice or experience with that, please share it with me¹⁵.

References

🔗 [1]: Added inline link support (https://git.nicholasjohnson.ch)
🔗 [2]: Implemented taxonomies (https://git.nicholasjohnson.ch)
🔗 [3]: implemented taxonomy Atom feeds (https://git.nicholasjohnson.ch)
🔗 [4]: Implemented terms (https://git.nicholasjohnson.ch)
🔗 [5]: implemented term Atom feeds (https://git.nicholasjohnson.ch)
🔗 [6]: Added quote styling. (https://git.nicholasjohnson.ch)
🔗 [7]: Started versioning the Hugo theme (https://git.nicholasjohnson.ch)
🔗 [8]: Semantic Versioning (https://semver.org)
🔗 [9]: Stopped formatting preformatted text for Gemini. (https://git.nicholasjohnson.ch)
🔗 [10]: Overhauled the CSS (https://git.nicholasjohnson.ch)
🔗 [11]: Fixed bold/italics removal logic for Gemini. (https://git.nicholasjohnson.ch)
🔗 [12]: Added back I2P support. (https://git.nicholasjohnson.ch)
🔗 [13]: the Tor network has been under a constant DDoS attack for the past few months
🔗 [14]: Expanded files subdomain access to Gemini. (https://git.nicholasjohnson.ch)
🔗 [15]: share it with me

Copyright © 2020-2024 Nicholas Johnson. CC BY-SA 4.0.