ttntm.me - Blog

Earlier this week, I ported my “simple landing page” template to Astro.

I recently published a template/starter intended to showcase how I’m using Preact for SPAs in buildless environments.

The opening paragraph of the last article published on this site already gave it away: I’m going to be writing about Preact a little more.

Working for friends and family is always quite a bit of an extra challenge, as “no” generally doesn’t count.

“Building something with Preact…” is probably going to sound like an unusual topic if you look at my other articles, but let me explain: I consider it a very powerful yet lightweight tool for building stateful/interactive experiences when going buildless…

Having a sitemap might not be an immediate priority when working on a small side project.

2nd entry in this series that I’ve decided to call “About the Past Year” from now on. 2022 wasn’t an easy year: we lost a family member to ALS (about 18 months after the diagnosis) and had to cope with loss, an international move and a lot of other things…

The feature request that got me looking into the use case mentioned in the title popped up as a “convenience feature” when re-writing my family recipes app last year.

Coincidences sometimes happen, and last night was one such occasion.

Despite living with a global pandemic (i.e.

Serverless functions are great - they provide instant superpowers to front end focused developers and they’re also quite addictive once you’ve gotten into using them.

It’s been about 6 months since I built and launched WATCH3R, an open source movie journal that’s using Fauna as its database.

I used Vite to build aitrack.work about 2 months ago and it left me with a really solid experience.

Why?

When Vue 3 was released in September, I started brainstorming for something new and useful I could build with it - in my opinion, real life use cases are often the best approach for getting acquainted with shiny new toys.

Nothing fancy, just a small announcement for an app I recently built - WATCH3R is a free service that provides basic information about movies and TV shows.

Introduction I had already heard of client-serverless architectures and read a bunch of articles about the subject when I came up with the idea of creating a personal use recipes app earlier this year - I hadn’t done anything like that before though.

My Vue app needed user uploaded images; storing Base64 encoded images inside FaunaDB was my first idea, but that proved both slow and resource heavy (which is probably why Fauna’s docs advise against doing that…).

This article was written a long time ago.

This article is about Vue.js, but it is not going to be a Vue.js tutorial.

So far, I’ve used the combination of Hugo and Tailwind CSS for more than 5 different projects.

When adding a search function to your Hugo site, one thing that’s required is a JSON index of the respective site’s content.

Why?

According to their docs, “Tailwind is a utility-first CSS framework for rapidly building custom user interfaces.”

There’s probably a lot of good tutorials on building a store locator out there, but I couldn’t find one matching my client’s requirements 100%.

Judging by the silence here, I must have been busy… The christmas holiday brought along Rockstar’s Red Dead Redemption 2, some well deserved relaxation and good company of family and friends.

I spent quite some time working on a friend’s portfolio website recently.

When this site was put together initially, it was basically a prototype for some kind of blog/portfolio kind of thing.

CSS variables make working with stylesheets easier, no doubt about that.

Data in Hugo Hugo comes with the possibility of storing structured content in a data file where it can be pulled from by the template placing it on the site.

I’ve had a lot of websites over the years, ranging from more or less official business endeavors like a small record label to more private things like a website for my wedding a while ago.