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,

This post discusses recent enhancements to the report generation process within the Reimpact/platform project, focusing on storing and displaying the generated report data.

The Feature

The primary goal of these changes is to persist generated report data and provide flexible views for different report types. This involves adding a report_data column to the packaging_generated_reports

In the Reimpact/platform project, we encountered a tricky issue with queue deserialization in our multi-tenant environment. This post details the problem, our investigation, and the solution we implemented.

The Problem

Our application uses a queue to generate reports. A GenerateReportJob is dispatched, serializing the GeneratedReport model.

The Reimpact platform is focused on streamlining various business processes. A recent enhancement focuses on providing users with more immediate feedback on long-running report generation tasks.

The Problem: Lack of Immediate Feedback

Previously, users initiating report generation had to manually check back later to see if the report was complete.

Introduction

In the Reimpact platform, we recently addressed an issue related to how database table names were being handled during migration seeding. Specifically, the system wasn't accurately extracting table names from migration files, leading to discrepancies and potential errors.

The Problem

Previously, the migrationTableAlreadyCreated method relied on parsing table names directly