Building robust and scalable applications often involves modular design principles. In the Reimpact/platform project, we've been focusing on enhancing our Filament resource implementations to streamline development and improve maintainability across various modules.

Streamlining Module Development with Filament

Filament provides a powerful way to create admin panels for Laravel applications.

The Reimpact platform is undergoing a significant architectural shift, moving from a MySQL row-level multi-tenancy model to a more robust PostgreSQL schema-per-tenant setup. This post dives into the key considerations and steps involved in this migration, leveraging Laravel and Filament.

The Motivation for Schema-Based Tenancy

Row-level multi-tenancy in MySQL, while initially simpler to

The platform project is undergoing a series of updates to enhance its architecture and developer experience.

Streamlining Panel Providers

Component registration is now more organized. The PackagingPanelProvider has been registered, ensuring that necessary components are readily available throughout the application. This centralizes the management of UI elements, improving maintainability.

Introduction

In the development of Breniapp, a key focus is delivering a seamless and intuitive user experience. Recent enhancements concentrate on improving how users interact with subscription plans and purchase additional credits.

Dynamic Plan Rendering

Previously, the display of available subscription plans in the upgrade modal was static, leading to potential inconsistencies and

Introduction

Row-level filtering is common for multi-tenancy, but what if you need stronger isolation? At Reimpact's platform, we're migrating towards PostgreSQL schemas to achieve true tenant separation, leveraging Laravel, Filament, and the middleware pattern.

This post details our approach to dynamically setting the PostgreSQL search_path for each tenant, ensuring data isolation and

Introduction

Have you ever wanted to add a unique touch to your Filament admin panels? A simple way to do this is by customizing the favicon. This post will guide you through how the Reimpact platform is streamlining this process using a shared branding trait.

The Problem: Consistent Branding

Maintaining consistent branding across multiple Filament panels can be challenging.

The Reimpact platform is undergoing a transition of its module URLs from Nova to Filament. This post details how we fixed a login redirect issue that arose during this migration.

The Problem

After migrating the Packaging module to Filament, users were experiencing redirect issues upon login when the MODULE_SELECTOR_SYSTEM feature flag was enabled.

Sometimes, the most effective UI changes are the ones that make things less noticeable. Consider a 'reset chat' button. Initially, it might seem intuitive to style it with a prominent color like red, signaling a potentially destructive action. However, in practice, this can create unnecessary visual noise and even user anxiety.

The Problem with Red

Red is often associated with errors,

This post explores the recent efforts to unify the visual style of chat components within the Breniapp/brenia project, focusing on creating a consistent onboarding experience for users.

The Goal

The primary objective was to standardize the look and feel of various chat components, including Brand Assistant, Brand Section, Skeleton Section, and QA chats.

Introduction

In the Breniapp/brenia project, we're continuously working to improve the user interface and overall user experience. One recent focus has been on optimizing the layout of Filament admin panel pages, particularly in scenarios where a more compact design is desired.

The Challenge: Vertical Space Optimization

Filament, a PHP-based admin panel, offers a flexible and