i believe this is something that needs to be said over and over:
immigration is a very good thing, and we should be facilitating it on a massive scale.
this isn't going to be a thoroughly revised piece of writing; it's going to be fairly
stream-of-consciousness. i intend to come back to this topic multiple times, and there is a lot to discuss
within it. but at the core of it, to me, is one fundamental stance:
immigration is a very good thing, and we should be facilitating it on a massive scale.
as everything is interconnected, expanding on that stance leads me right into the topics of housing and
the housing crisis. pretty much every one of our cities is not building enough housing -- certainly not
enough near jobs.
immigration should be facilitated on a massive scale, and this necessarily means we need a lot of new
housing. we need a lot of new housing even if there is very little immigration, so we should be
facilitating the development of housing on a massive scale as well.
from there we can branch off into so many topics, like ways to facilitate the development of housing, or
how we could and perhaps should build lots of housing collectively, and urbanist principles... like how
we should try to put lots of new housing near and amongst employment, how walkability and bikeability
and reliable public transit support liberation and opportunity...
i'll leave it there for now. there are some topics i think i'll want to write about multiple times as i
refine my thoughts; this is one of them.
it's saturday. iu hosts kennessaw state today at noon eastern, i'm gonna browse some neocities sites, and
i'll spend some time outside in the great weather. hell yeah
regarding my site - i might work on the blog backend to have links to the previous & next entry
auto-populate in each blog page. then expanding on that, i'd like to make it so that, in the main "blog"
page, the prev/next post links just jump to the heading of that post within the same page, while the
ones in the individual blog post pages will go to other individual blog post pages. as of right now, the
individual blog post pages aren't serving much purpose because nothing really links to them.
actually, i'm gonna go through and make the heading of each blog post a link to the post's page,
like, right now
and now that has me thinking, since there's sort of a boilerplate for the blog posts, maybe i ought to
make a blog template and have it fill in the heading w/ link and prev&next links.
i still might want to be able to use the different card colors in blog posts, so i guess i could
use another variable to change the div class from "card" to "card-green" or "card-blue" or whatever
it also just occurred to me that i can nest the cards as much as i want. idk why i hadn't thought of
that until now.
quite happy to see iu blow out a team they're supposed to blow out
archived box score
I wrote in yesterday's blog post about having created my minimum viable version of
a site builder program written in Go -- in my case a static site generator, though it's not far off from more
dynamic examples like j3s's site, which was a key inspiration for doing this.
Today I'm writing more pages for the site, and I'll push this big site overhaul to Neocities today. I'm also
going to "archive" the old blog posts, maybe with an additional note about how they're outdated / referring to
previous ways the site was configured.
I've been wanting to update my neocities site more, but I just wasn't. And I think a big reason why I
wasn't updating it is because I didn't like the workflow, at least not for blogging. I was going the "completely
raw html" route, and the clunkiness of manually working with templates and having to propogate changes across
all the site's files definitely hindered any inspiration to blog or design or whatever.
But I still wanted to have an entirely HTML-based site, partially due to ignorance regarding using ~frameworks~
for web development and partially due to an I don't need no dang
framework, just fucking use html mentality. So I just needed a workflow that I would actually use.
To be clear, do what works for you. If you like a certain framework, have at it.
I came across j3s.sh, specifically their blog post
"my website is one binary,"
and it started me on a journey of figuring out just enough Go to build something
similar for my neocities site.
Since I won't be running the binary on the server, I just needed to design a program to build HTML files
from some kind of template & content files. I have basically no experience with Go, though, so over the past few
days I've learned what I need to make this. It takes an html template and a stylesheet in a "templates" directory
and page body content html files in a "content" folder as well as "content/blog". The files in the "blog"
subfolder get their own pages and appear in a blog page
containing all of the blog posts
So far, it's kinda the minimum viable version. I want to add some more functionality, like
Anyway my thoughts are a lil scrambled right now, but I'll find better ways to write about it and give it a standalone page on here!!
happy new year! I've decided to make a blog page on this here neocities site and think about other things to do with the site. I like the idea of starting a
digital garden, but I think I'd maybe rather do that in dokuwiki as a self-hosting experiment. But I could certainly link to that and write about it on this
site, too :)
anyway I felt like I needed to make a new post given the new page for the blog
P.S. (2025-09-05) ~
This blog post is "archived" from before started using my homebrewed static site
generator. But it is still true that the blog has its own page, and it's even
better in this new workflow!
The blog posts from December 14 and 15, 2024, contained "embed" tags that are now broken.
I've solved the workflow issues I was discussing here, but I want to leave these old blog posts to show how I was
thinking about the problem as I figured it out.
~wharf 2025-09-05
The blog posts from December 14 and 15, 2024, contained "embed" tags that are now broken.
I've solved the workflow issues I was discussing here, but I want to leave these old blog posts to show how I was
thinking about the problem as I figured it out.
~wharf 2025-09-05
In thinking about ways to structure my neocities site, I've been thinking about how I want to handle blog posts. For now, I'm just doing this reverse
chronological stack of "cards" on the homepage (which is for now the only page, lol), but that means I have to write the posts directly in the HTML.
That's kinda fine for the very barebones situation of neocities, but it had me thinking about ways to store the posts on external files and embed them.
This brought me to the <embed> tag, so I figured I'd test it out, which gives us:
I recently installed Rocky Linux on a Dell Latitude E7470
that was left in my possession by a client (who never asked for it back and did not provide instructions on returning it). It's essentially the
continuation of CentOS and more-or-less an open-source clone of Red Hat Enterprise Linux. I plan
to use it on some headless laptops for homelab stuff, so I figured I'll do some testing with this laptop.
So far, Rocky Linux has been a lot smoother on this laptop (with a 6th-generation Intel i7 -- outdated yet quite applicable for homelab uses) than Ubuntu
was, and now I'm feeling like it's actually a pretty good desktop experience right out of the box.
I think the next step is to start checking out NextCloud, and testing self-hosted DokuWiki
(which I use to document the Minecraft Realm I play on with some friends). And I guess I might as well install a no-GUI version of Rocky Linux on the
headless laptops that will be my servers.
I've been writing this site basically from scratch, using some snippets and such but otherwise not relying on some layout.
Before, I was using a layout that looked like Notepad in like Windows XP, and it was really neat, but ultimately I wanted to start using the
layout and design for self-expression, too, not just the page content.
I now have a functional layout and some ideas for what to do next, as well as some design decisions that I'll table for later.
The laptop on which I'm writing this is dying, so I'm gonna get this update published and go play Minecraft.
P.S. 2025-09-05 ~
This post was kinda the start of a journey that led to a big re-working of my neocities workflow, which I
wrote about on 4 September 2025.
~wharf