I decided to avoid modals and toasts entirely in #telesink. Everything is rendered inline with Turbo Frames. The goal is ultimate simplicity and speed. In the video below: signing up and sending the first event.

Quick glimpse of #telesink that I'm actively building. ✅ Every event your app sends lands in a sink ✅ Dashboard columns: slice, organize & group events (in the future) ✅ Click any event for full details

Events in #telesink will be grouped into sinks and displayed as columns. You’ll be able to add as many columns as you like. Each column will filter a sink based on your own criteria. P.S. This is the goal. I'm still very early in development.

CSS clamp() is straight-up MAGIC. I’m having an absolute BLAST building this buttery-smooth fluid layout for #telesink. Going full unconventional with the experience, but honestly, clamp() was made for dense, information-rich UIs like this. Feels like cheating (in the best way).

For #telesink, I went with a fluid, text-first design. Entire UI built on text. The design is its absence. Your feeds elegantly fill the whitespace, making every view uniquely yours.

I’m going all-in on #telesink again (the open-source real-time event tracking dashboard of my dreams). Kicked it off about a month ago, but poor planning + some bad luck meant I barely touched it since. Starting today, I’m in full Telesink mode (while staying on standby for Telebugs support tickets).

Laying the first brick for #telesink 🧱 github.com/telesink/telesink

Publish "The real-time event tracker I want" #telesink telesink.com/blog/the-real-ti…