Introduction

The rifasvelez-web project recently underwent a significant architectural shift with its "V2" update. This overhaul wasn't just about new features; it was a fundamental re-evaluation of how we build and maintain our application, ensuring it remains robust and adaptable for future growth. The core of this modernization involved adopting Hexagonal Architecture to separate concerns and enhance modularity.

The Problem

In many evolving web applications, initial rapid

In the rifasvelez-web project, delivering a lightning-fast user experience is paramount, especially for critical visual content. We recently undertook a significant refactor aimed at optimizing images and enhancing preloading strategies to achieve a better Largest Contentful Paint (LCP). LCP is a crucial metric that measures when the largest content element in the viewport is rendered, directly impacting a user's perception of load speed.

What Worked: Strategic Image Optimization and

The Project Context

Our rifasvelez-web project, built with Astro, is dedicated to providing a fast and modern web experience. A crucial aspect of any public-facing website is its discoverability and presentation in search engine results. This led us to address a key area: Search Engine Optimization (SEO), specifically structured data schema.

The Problem: Incomplete or Incorrect SEO Schema

Effective SEO goes beyond just keywords; it involves helping search engines understand the

On our rifasvelez-web project, which serves as a platform for various raffles, keeping the user interface updated with the latest event information is crucial. Recently, we undertook an effort to refine how the "Next Raffle" section is displayed, aiming for a more dynamic and maintainable approach.

The Challenge: Dynamic Content on a Static Site

The "Next Raffle" section presents information about the upcoming event – its name, date, and time. This content is inherently dynamic, changing

Introduction

The rifasvelez-web project, a platform for managing raffles, recently received an important update focused on improving how users interact with upcoming events. A key enhancement involved revamping the "next raffle" section to provide more dynamic and up-to-date information.

The Challenge

For web applications displaying frequently changing information, like the details of an upcoming raffle, maintaining content freshness while ensuring optimal performance can be a

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

The Problem

In our pqrs project, a system for managing various internal records presented as 'cards,' we identified an issue with the existing filtering mechanism. Users reported inconsistencies where certain cards were either erroneously included in filtered results or, more critically, excluded when they should have been visible. This led to user frustration, inaccurate data representation, and a general lack of confidence in the system's ability to retrieve precise information.

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

Is your dashboard a static display of numbers, leaving users to manually search for the underlying data? In the pqrs project, we recently tackled this common frustration by transforming our dashboard's summary statistics into interactive filtering tools. This enhancement significantly streamlines the process of drilling down into specific datasets, making the dashboard not just informative, but also highly functional.

The Interactive Solution: Filtering Records by Status