Google Tag Manager (Gtag) is a staple for tracking and analytics, but implementing it incorrectly can lead to significant main-thread blocking, negatively impacting your site's Lighthouse scores and user experience. In our project 'rifasvelez-web', we recently revisited our Gtag implementation to ensure that analytics gathering doesn't come at the cost of page responsiveness.

The Performance Bottleneck

When loading external scripts like Gtag, browsers often prioritize these network

Improving Data Tracking

In our project, rifasvelez-web, we recently focused on refining our analytics integration. As we scale our web presence, ensuring that user interaction data is captured accurately and efficiently is critical for our growth metrics.

The Challenge

Our existing analytics implementation required maintenance to ensure better tracking reliability. Additionally, as we evolved our content structure, the underlying data schema needed minor adjustments to stay

The Performance Bottleneck

Third-party scripts like Google Tag Manager (GTM) are notorious for slowing down the initial page load. When scripts execute on the main thread, they compete for resources, often delaying vital tasks like hydration or interactivity. In the rifasvelez-web project, we wanted to ensure our tracking didn't come at the cost of user experience.

The Solution: Offloading with Partytown

Partytown allows you to offload resource-intensive third-party scripts to a web

The Challenge: Stale Visuals

Working on the rifasvelez-web project, which utilizes the Astro framework, we recently encountered an issue where the image gallery was failing to pull the latest updates. Users were seeing cached versions of media rather than the newly uploaded assets, leading to a disconnect between the repository content and the live web experience.

The Solution: Versioning Strategy

To ensure our static site generation consistently fetches the most recent media, we

Even the most carefully crafted applications can encounter unexpected issues, especially when relying on external data sources. For the rifasvelez-web project, we recently tackled a crucial area often overlooked: robust error handling and user-friendly fallback UIs for our image gallery, powered by Cloudinary.

The Situation

Previously, our image gallery component directly fetched data from Cloudinary. While this worked flawlessly most of the time, any hiccup – be it a network issue, an

In web development, reliable asset delivery is crucial. For the rifasvelez-web project, which relies on Cloudinary for image hosting, we recently addressed a subtle but impactful issue related to how image URLs were constructed. The challenge was ensuring that images consistently loaded, even when expected metadata, like a version segment, was missing or malformed.

The Problem: Fragile URL Generation

Cloudinary URLs often include a 'version' segment (e.g., v1234567890) after the host

In dynamic web applications, content evolves constantly. Features are added, data is updated, and sometimes, entire sections need to be gracefully retired. This ongoing process of managing content lifecycle is crucial for maintaining a clean, performant, and user-friendly experience.

Recently, on the rifasvelez-web project – a web application built with Astro – we tackled two specific content management tasks: the complete removal of a raffle entry and the addition of dynamic details to the

As web applications evolve, the need for new features like managing "new raffles" becomes paramount. The rifasvelez-web project recently saw an update to facilitate this, specifically targeting the /sorteos route. The core challenge here isn't just to build the feature, but to integrate it in a way that remains scalable, testable, and maintainable without turning the codebase into a tangled mess.

Introducing new features into an existing web application can often be a complex dance between frontend presentation, business logic, and data persistence. In our recent work on the rifasvelez-web project, we tackled this challenge by enhancing our raffle management system to support new raffles, focusing on maintainability and scalability through a well-defined architecture.

The Situation: Expanding Raffle Capabilities

Our rifasvelez-web application needed to evolve beyond its

Project Context

The pqrs project focuses on managing various types of requests or cases, often called 'radicados'. Our goal was to improve the usability of the dashboard, making it easier for users to quickly filter and view radicados based on their status.

The Challenge

Previously, the pqrs dashboard presented a clear overview of radicados through various statistical cards (e.g., "pending", "completed", "overdue"). However, interacting with this data required users to manually