Nuxt Plugins

Since 2022, my focus has shifted from web development with Kirby CMS to Nuxt. Since the alpha phase of Nuxt 3, I’ve been actively following the meta-framework on GitHub. Over time, I’ve created several open source projects for use in my own projects, which I’ve been maintaining ever since:

• unlazy: 🪧 Universal lazy loading library for placeholder images leveraging native browser APIs
• @nuxtjs/plausible: 🎟️ Plausible Analytics integration for Nuxt
• nuxt-api-party: 🐬 Securely connect to any API with a server proxy and generated composables
• nuxt-prepare: 🦎 Build actions for Nuxt
• nuxt-vitalizer: 🪿 Instantly better LCP scores in Google Lighthouse
• nuxt-kirby: 🫧 Kirby CMS integration for Nuxt with KQL support
• nuxt-gtag: 🔸 Google Analytics & Google Ads integration made easy

Usage of My Plugins

After years of developing and maintaining my Nuxt modules, I got curious: Who might actually be using my plugins? I managed to identify a handful of projects that use my packages:

Nuxt Plausible

From a UX perspective, cookie banners are a thorn in my side. That’s why I rely on Plausible, a tracking solution that complies with GDPR and doesn’t obstruct the user’s clicking around on a website.

For a side project (Dachsbau) I wrote a module to connect Nuxt with Plausible as easily as possible. I later extracted the initially internal plugin as a Nuxt module. Unexpectedly, I was offered to make the module available as an official Nuxt module. Sure!

What makes me most happy is that Nuxt.com uses it itself.

Nuxt Kirby

I now only use Kirby CMS as a headless CMS in my projects. Front-end development with meta frameworks such as Nuxt can be deployed universally across different providers, and in my opinion it offers a more pleasant developer experience than traditional Kirby websites.

However, when it comes to content editing, no other CMS comes close to the flexibility of the Kirby Panel – despite one or two systems claiming to be tailor-made for the headless approach. This is why I continue to use Kirby and customise panels depending on the scope and use case.

There were a few npm packages that provided Kirby integration for Nuxt. However, they were all only compatible with outdated Nuxt versions. To meet my own needs, I set out to create the perfect solution. It was my first Nuxt module and it was a steep learning curve. With steady enthusiasm, I created a holistic module that is also used by larger commercial websites.