Introduction

The landing project serves as a central hub for showcasing user portfolios and capabilities. A key aspect of this is guiding new users through the platform's features to ensure a smooth onboarding experience.

The Enhancement

Recent updates focused on enhancing the portfolio tour, specifically highlighting the platform's AI-powered post generation capabilities. This involves:

Introduction

Attracting entry-level developers requires a focused approach to SEO and messaging. Many companies struggle to effectively target this demographic on their landing pages. This post outlines recent improvements to the landing page to better resonate with junior developers seeking their first tech job.

Key Updates

Targeted SEO

The meta descriptions and keywords have been

The Problem

In multi-tenant applications built with Filament, ensuring the correct tenant context is crucial for data isolation and application functionality. A common issue arises when middleware responsible for setting the tenant context runs before Filament resolves the tenant from the URL.

In the Reimpact/platform project, a recent update addresses an issue where Livewire update requests were being incorrectly blocked by a custom middleware. This post details the problem and the solution implemented.

The Problem

The ValidationUserMiddleware was designed to handle user authentication and validation for incoming requests. However, it was inadvertently blocking unauthenticated

The Problem

In a Laravel application, particularly when using Livewire, maintaining consistent authentication behavior across different types of requests can be tricky. A common issue arises when Livewire requests, which often send Content-Type: application/json, are not correctly handled by authentication middleware, leading to unexpected 401 errors instead of redirects to the login page.

Introduction

Experiencing a 401 Unauthorized error immediately after a successful login can be a frustrating issue in Laravel applications. This often stems from incorrect redirection targets or misconfigured middleware. Let's explore how to diagnose and resolve such problems, specifically within the context of projects using middleware for access control.

Understanding the Problem

Context: Breniapp

The Breniapp project focuses on [description]. Recent efforts have centered on improving the documentation, specifically regarding mobile responsiveness.

Mobile Responsiveness Guidelines

A key area of focus has been the addition of mobile responsiveness guidelines to the CLAUDE.md documentation file. Ensuring applications are accessible and user-friendly across

Introduction

In web applications, handling images from different origins can be a recurring challenge due to Cross-Origin Resource Sharing (CORS) restrictions. These restrictions often lead to unexpected failures, especially when trying to manipulate images using technologies like html2canvas to capture screenshots with overlays.

The Problem

When capturing web page screenshots using

Introduction

This post details a fix implemented in Breniapp/brenia to improve how canvas images are handled, specifically addressing issues with html2canvas when capturing overlays. The core problem was that the crossorigin="anonymous" attribute on canvas images was causing html2canvas to fail in certain scenarios.

The Problem: CORS and html2canvas

The crossorigin="anonymous"

The Breniapp project focuses on streamlining internal business processes. Recently, we tackled an issue with how media assets were being handled, specifically in the content library.

The Problem

The asset() helper function was generating incorrect URLs for files stored in the public disk, leading to broken links and display issues.