Just three short months after rebuilding my website with Astro, I rebuilt it again. This time, I am using Bridgetown as a site generator. It’s written in Ruby (which I’ve been looking for an excuse to learn) and strives to optimize for developer happiness and provide everything needed to build a great website. This is how I built my great website and what I learned.

Applying a face lift

The visual design is the biggest, most obvious change that I am most excited about. No more monochrome! I was reminded in the last rebuild that I’m not much of a designer. I’ve always liked and wanted to do a “neobrutalist” site design but quickly got overwhelmed with picking colors, border widths, and box shadow thickness.

To solve this, I used Open Props to load in a bunch of useful and well-thought variables. Instead of creating my own CSS variables and design system, I can just write var(--purple-4) to get the right shade of purple that I want. If I want it lighter, I lower the number and if I want it darker, I increase the number. As frictionless and simple as that. If I wanted to do the same thing by scratch I’d have to go to some color picker website, hope I choose the right shade of purple that will look good, and paste the hex code into the CSS file.

This same principle applies to font sizes, spacing sizes, borders, and more. It really took the overwhelm of choosing the right variable names and colors out of the equation and let me quickly experiment. It’s like Tailwind but you don’t combine your HTML and CSS. Each short keyword maps to a longer CSS variable:

I combined Open Props with the power of SCSS to randomly choose some colors. For the landing pages that list content (like posts, weeknotes, or book notes), each item in the list gets a random color. The following SCSS code colors list items randomly while keeping the tag buttons and title that sit on top of it the same color, just two shades lighter.

$colors: red, orange, yellow, cyan, indigo, pink;
$repeat: 20;

@for $i from 1 through $repeat {
  $color: nth($colors, random(length($colors)));

  .list-item:nth-child(#{length($colors)}n+#{$i}) {
	background: var(--#{$color}-4);

	.list-item__title {
      background: var(--#{$color}-2);
	}

    .list-item__tag {
      background: var(--#{$color}-2);
    }
  }
}

For the cherry on top, I made heavy use of :hover() and transform CSS features so that elements pop out a little when you hover over them. Basically every panel, button, and link do this. It makes the website a bit more squishy and fun to use.

A huge thank-you goes to Alessandro Muraro for the design inspiration. Check out their website, it’s a thing of beauty.

Redesigning the home page

I’ve never really known what to put on the front page of my website. Taking inspiration from Alessandro Muraro again, I have the following sections on my home page, arranged using CSS grid which I’ve never used before as a bit of a flexbox fanboy:

Combined, these sections do a pretty good job of giving the user a good idea about who I am while also letting them immediately start clicking and exploring.

Creating a tag system

Tags are something I’ve never really taken advantage of. I prefer folders and collections to group my content, using tags for just a few very specific cases. Now, tags are first-class citizens on my website.

Using tags makes jumping around my website easier and more enjoyable while making the whole thing feel like a more cohesive, interconnected entity. This does require thoughtful and consistent use of tags, though, which I’m not quite good at yet. I’ll be thinking about how to do this better in the future.

Each tag has its own page at /t/<tag-name>/ that lists all posts from across my site that have that tag. These pages are generated automatically via a plugin that was surprisingly easy to write. In just a few lines, I had a plugin that pulls all the tags I’ve used and generates a page for each of them:

all_tags = site.tags
all_tags.each do |tag, resources|
  add_resource :pages, "t/#{tag}.md" do
    layout "page"
    title "tag: #{tag}"
    template_engine "erb"
    content "<% resources = site.tags['#{tag}'] %>\n<%= render Shared::List.new(collection: resources) %>"
  end
end

Pulling in content automatically

Bridgetown and Ruby make it really easy to manipulate, gather, add, or convert content. In my past websites, I’ve used a script that pulls in notes from my Obsidian vault and converts all the wikilinks to a format specific to the framework.

This time, thanks to Ruby, Thor, and a simpler algorithm, it was much cleaner. I can definitely see why people who like Ruby really like Ruby. I thoroughly enjoyed learning and writing it. Watch out, Python.

My new script walks my Obsidian vault and looks for notes with a tag in the front matter called copy_path. If that tag exists, it copies the note to the path given. The title of the note and the path that it was copied to are stored for later when converting the links.

After all notes are copied, the script scans each one and finds wikilinks based on a regex and parses them out into the linked note and the text to display. The linked note gets looked up to check if it was copied over according to the information that was stored earlier. If so, it gets converted end plugged into following helper, specific to Bridgetown: <%= link_to "text to display", "linked-note.md" %> Otherwise, just the text to display is written without a link. This lets me link to anything in Obsidian and only what is published gets linked to in Bridgetown.

Images that are linked are not automatically copied over. The script spits out a list of images that were linked to and asks you to manually copy them over to the /src/assets/ folder.

Lastly, my Kindle highlights are stored alongside my book notes under a Highlights header. The last step of the script is to lop these off so my messy highlights don’t get displayed.

Redesigning the URLs

I’ve wanted shorter, cleaner links for a while. They are easier to look at, type, copy, write, and say. They weren’t really long to begin with but compare these:

Much cleaner. The /writing/ path is a vestige from the very beginning when I didn’t want to call my blog a blog. Here are all of my current content URLs:

Many blogs include the date or year in the link (e.g. example.com/2024/a-blog-post/) to make the posting date quickly evident or to avoid naming conflicts from two pages being titled the same thing. I chose not to do that because it lengthens the URL without really adding any value. The posting date and last modified date are in the post itself so it doesn’t need to be in the URL too. I’m not worried about naming conflicts; if Derek Sivers who uses just a few characters in his URLs doesn’t have that problem, I certainly won’t.

Yes, I committed a cardinal sin and broke some links. I think it was worth it, though, to get shorter, more intuitive, and more sustainable URLs. To prevent too much link rot, I switched hosting providers from GitHub Pages to Netlify.

With Netlify, you can specify server-side redirects to redirect users from one URL to another. If someone visits an old link that goes to wwinks.com/books/upgrade/, they will now be redirected to wwinks.com/b/upgrade. Same with all of the above changes. I will likely change /peace-corps/ to /pc/ in the future but wanted to test out the redirect functionality first. These posts are very important to me and I want to guarantee that anyone trying to read them will be able to.

“Is there some kind of competition or something?”

What’s the point? Why did I put in all this time and energy and stay up too late some nights just to make my website look cooler?

Besides learning so much, as that is always worth the effort to me, I love my website again.

It makes me smile. I’m proud of my site and I’m excited to show it off. I know exactly what’s on every page, yet I still enjoy looking, browsing, and clicking around. I really like the tooling, much more than my last site, and I’m looking forward to the next time I can hack on the underlying code to implement more features. It’s my site and it represents me well.

Created:

Last modified:

Written by Human, Not by AI

Like my writing?

Say thanks by buying me a coffee or send me an email with your thoughts.

Email me

Keep Reading

Wellbeing Tools or, A Long Overdue Apology
ruby coding tech