Introduction

Maintaining a consistent brand identity across multiple admin panels can be a challenge. In the Reimpact platform, we faced this issue with our eight Filament panels, each serving different modules. The goal was to ensure a unified look and feel while streamlining maintenance and updates.

The Problem

Previously, each Filament panel had its own branding configuration, leading

Collecting user feedback is crucial for iterative improvement in any application. However, the timing and method of prompting users for feedback can significantly impact their experience. In the Breniapp application, a new approach balances proactive engagement with user comfort.

The Feature: Just-in-Time Feedback Prompts

A Livewire component has been introduced to present users with a

Ever had a loading indicator that flashes annoyingly, appearing and disappearing seemingly at random? We did, in the Reimpact/platform project. A previously implemented wire:loading approach for our charts was causing more frustration than help.

The Problem

The original implementation relied on wire:loading which, while convenient, proved unreliable for complex interactions.

When managing multi-tenant applications, ensuring data integrity across all tenants is crucial. Recently, while working on the Reimpact/platform, we encountered an issue during tenant migrations related to non-nullable columns. Here’s how we addressed it.

The Problem

In a multi-tenant architecture, each tenant often has its own database schema. During migrations, these schemas need to be

The Reimpact platform benefits from a well-organized and efficient admin dashboard. Recently, work has focused on refining the Packaging dashboard's filter system to improve both its appearance and initial data loading performance.

The Problem: Styling Inconsistencies and Delayed Data

Previously, the dashboard filters suffered from inconsistent styling, making the interface feel disjointed.

Introduction

Imagine a scenario: a user switches between different brands within an application, expecting all relevant components to reflect the change immediately. However, child components, especially those using Livewire, might retain stale data, leading to a confusing user experience.

Introduction

In the Breniapp/brenia project, we recently encountered an issue where certain actions within our Livewire components were being triggered multiple times unintentionally. This manifested as duplicate image downloads on a content generation page. The root cause was traced to Livewire 3's @script block, which re-executes on every component update, leading to an accumulation of

When developing widgets in Reimpact/platform, efficiency is key. A recent update addresses an issue with Filament's default sorting behavior in subqueries, specifically within the TopExceptionsWidget. Let's explore the problem and the solution.

The Problem

Filament, a PHP framework, automatically applies ORDER BY model.id when using HasRecords. This default behavior becomes problematic

Introduction

The Reimpact/platform project is undergoing improvements to its testing infrastructure, specifically focusing on Filament resources. The goal is to ensure comprehensive test coverage for CRUD operations across various resources, while also addressing tenant-specific data handling.

The Challenge

Previously, testing Filament resources lacked sufficient coverage, especially

En el proyecto Breniapp/brenia, se han realizado mejoras significativas centradas en la persistencia de datos y la optimización de la interfaz de usuario. Estas actualizaciones buscan mejorar la experiencia del usuario, asegurando que la información se conserve entre sesiones y que la interfaz sea más intuitiva y agradable.

Persistencia del Estado del Chat con Sesiones

Uno de los puntos