Documenting code, one commit at a time.
On the devlog-ist/landing project, we recently implemented a comprehensive weekly newsletter digest system designed to keep users engaged with fresh content. The goal was to build a robust, configurable, and secure system capable of handling subscriptions, content delivery, and user management efficiently.
Developing a newsletter system
The devlog-ist/landing project, a foundational platform, recently underwent a significant upgrade to its billing infrastructure. Our goal was to introduce a robust and flexible subscription management system, moving beyond basic one-time payments to support recurring plans. This involved integrating Paddle as our primary payment gateway, alongside building a comprehensive administration
Our landing project recently focused on enhancing user experience by providing more robust third-party integration options directly within their settings. The goal was to expand beyond existing integrations like LinkedIn and introduce Google OAuth, all while creating a unified management dashboard.
As applications grow, so does the demand for seamless connections with other
Developing for the landing project often involves managing various cross-cutting concerns, such as authentication, logging, and data validation, for incoming requests. As applications grow, these concerns can clutter core business logic, making the codebase harder to maintain and extend. This is where patterns like Middleware become invaluable.
This post discusses how we addressed a rendering issue in the Breniapp project related to dynamically updating canvas aspect ratios. The problem stemmed from using Alpine.js to manage the aspect ratio of a canvas element within a Blade template that conditionally rendered based on Livewire state.
Initially, Alpine.js was used to dynamically update the aspect ratio of a canvas
Maintaining a consistent code style is crucial for any project, especially when multiple developers are contributing. This post delves into how the Breniapp/brenia project enforces code style using php-cs-fixer, focusing on Livewire dispatch calls.
Consistent code style improves readability, reduces cognitive load, and minimizes merge
The Breniapp project aims to streamline [description]. Recently, we tackled an issue with the locale switcher that was causing inconsistencies in how user locales were being handled.
Previously, the locale selected by a user was only being saved in the session and a cookie. This approach relied on a two-step redirect chain through a LocaleController.
In the landing project, we've been focusing on improving the reliability of background jobs, especially when dealing with rate limiting and throttling exceptions. Previously, we used a fixed number of retry attempts, but this approach proved to be problematic.
When jobs are released back to the queue due to rate limiting or throttling middleware, each release counted towards the
This post details a recent optimization in the landing project, focusing on how we transitioned file downloads from a Livewire AJAX implementation to a more robust HTTP route. This change addresses issues with file corruption and improves overall reliability.
Initially, we used a Livewire method, downloadCv(), to serve dynamically generated DOCX files.
In the landing project, we encountered a subtle but significant security issue related to how data was being passed from PHP to JavaScript within our Blade templates. Specifically, when using Livewire and Alpine.js, values containing special characters (like apostrophes in names such as "O'Brien") could break the JavaScript context, leading to unexpected behavior or, worse,
