Introduction

Effective communication is the cornerstone of any long-term software project. Whether you are working on open-source initiatives or internal tools like Ryuu-no-Mi, keeping your documentation in sync with your development progress is essential for onboarding new contributors and maintaining project velocity.

The Role of Documentation

Documentation acts as the "north star" for

Designing a scalable data layer is a foundational challenge in any growing application. As we continue to develop the Ryuu-no-Mi marketplace, we are shifting our focus toward a more robust architectural approach by implementing the Repository Pattern to decouple our business logic from database-specific implementation details.

The Challenge: Coupling Logic to Storage

Directly querying

Our Refactoring Journey

Recently, the team at Ryuu-no-Mi/marketplace embarked on a mission to improve our core service architecture. As our marketplace grew, we noticed that our business logic was becoming tightly coupled with our infrastructure, making it increasingly difficult to test and maintain.

Improving Asset Resolution

In our latest update to Ryuu-no-Mi/my-portfolio, we focused on refining how the application handles image assets across the Hero component and our centralized content management data. Maintaining consistent paths for visual assets is critical for a smooth user experience, especially in a portfolio environment where visual fidelity is paramount.

The Challenge of

Starting the Foundation

I have recently started working on the Ryuu-no-Mi/marketplace project, an initiative aimed at building a scalable digital marketplace. A critical first step in any data-driven application is defining the relational structure that will serve as the backbone of the entire system.

Designing the Schema

To ensure type safety and ease of maintenance, I have chosen to

Every fleet management system requires a solid entry point. In the Ryuu-no-Mi/Gestion-de-flotas project, the focus shifted this week to establishing a secure and clean interface for user access. Building a login view is more than just creating a form; it is about establishing the first layer of trust between the user and the platform.

The Challenge: Structuring Access

When we started

In our current work on the Ryuu-no-Mi/Master-Spring-Boot-3-web-apps project, we have been focusing on hardening the backend services that handle our product catalog. While utility classes and basic CRUD operations often seem trivial, keeping them clean is essential for long-term project health.

The Challenge of Growing Services

As a project scales, the ProductService layer often becomes a

Introduction

In the Ryuu-no-Mi/Master-Spring-Boot-3-web-apps project, I have been focusing on strengthening our application security. Specifically, I recently worked on implementing a robust JSON Web Token (JWT) authentication flow to manage user sessions effectively.

The Challenge: Moving Beyond State

Traditional session management stores state on the server, which can become a

Introduction

Building an e-commerce platform requires a robust foundation for managing inventory. In our work on the Ryuu-no-Mi/ecommerce_happymami project, we recently focused on implementing the core Create, Read, Update, and Delete (CRUD) operations for products. This is the fundamental engine that drives product catalog management.

The Anatomy of CRUD

CRUD represents the four basic

Documentation is often treated as an afterthought in software development, frequently relegated to the end of a project cycle. However, in the Ryuu-no-Mi project, we recently focused on refreshing our primary repository documentation as a means to align team expectations and project direction.