Documenting code, one commit at a time.
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.
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.
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.
This post highlights recent enhancements to the Breniapp interface, focusing on visual refinements and improved user interactions within the application.
A subtle but important fix addresses a visual artifact in the sidebar. When the sidebar collapses, the separator line now transitions smoothly using Filament's CSS variables.
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
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.
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.
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.
Red is often associated with errors,
The Breniapp project has been undergoing UI modernization efforts, focusing on both the overall aesthetics and specific elements like the chat interface. This post will cover the key changes and their impact.
One of the primary goals was to refine the existing design system. This included subtle but impactful changes such as:
Breniapp is undergoing continuous improvements, and a recent update focused on refining the visual aesthetics of the application's headers. This seemingly small adjustment plays a crucial role in enhancing the overall user experience by creating a more polished and professional interface.
The primary goal was to tighten the header spacing, specifically bringing the subtitle
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 primary objective was to standardize the look and feel of various chat components, including Brand Assistant, Brand Section, Skeleton Section, and QA chats.
