The landing project received a facelift, focusing on aesthetic improvements to the retro theme. The goal was to reduce the overwhelming use of a single color and introduce more visual diversity across different elements.

The Challenge

The initial retro theme relied heavily on yellow, which, while visually striking, became monotonous when applied to all elements like badges, project

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 using Laravel Horizon, a queue monitoring tool, you might encounter issues with Content Security Policy (CSP) blocking inline scripts. Here's how to address it.

The Problem

Horizon serves its JavaScript and CSS inline using Horizon::js() and Horizon::css(). Without a proper nonce for CSP, browsers can block these inline scripts, even though Horizon's own authentication gate

Introduction

In Breniapp, we recently tackled an issue where downloaded images were not reflecting the complete visual output displayed on screen. Specifically, text and logo overlays, which were rendered using HTML and CSS, were missing from the downloaded image, resulting in users receiving only the base image.

The Problem

The original download implementation was simply fetching the

Introduction

This post details recent improvements to the calendar user experience in the Breniapp project. The focus was on refining text sizes, padding, modal presentation, and content titles for a more intuitive and visually appealing interface.

Height Calculation and Grid Adjustments

The calendar height calculation was adjusted to better fill the viewport, ensuring a more consistent

The Breniapp project focuses on providing streamlined solutions. A recent effort has centered on enhancing the content calendar feature, aiming for a more intuitive and visually appealing user experience.

The Goal: A More Intuitive Calendar

The primary objective was to revamp the existing content calendar to improve usability and visual clarity. This involved rethinking the layout,

In the Reimpact platform, we're always striving to optimize performance and ensure smooth operation. Recently, we encountered an interesting issue with the TopExceptionsWidget model that highlights the importance of correctly defining primary keys, especially when dealing with subqueries.

The Problem

Filament, our admin panel framework, relies on $record->id to uniquely identify rows in

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 is undergoing continuous improvements to enhance its monitoring and reporting capabilities. Recent updates focus on refining how exceptions are tracked and how data is presented to users, ensuring a more informative and user-friendly experience.

Addressing Query Builder Compatibility

One of the key updates involves resolving a compatibility issue within

The Reimpact/platform project is focused on [description]. Recent development efforts have concentrated on improving the way DPR (Data Protection Report) data is presented and managed within the platform. This involved transitioning from a static HTML table to a dynamic Filament TableWidget, offering enhanced features such as pagination, search, filtering, and translation support.