Documenting code, one commit at a time.
At Ryuu-no-Mi, we have been focusing on the Gestion-de-flotas project to refine our administrative dashboards. As our vehicle inventory grows, managing data effectively requires more than just displaying lists; it requires precise control and safe interaction patterns.
Initially, our dashboard was a simple read-only list.
In our Ryuu-no-Mi/Master-Spring-Boot-3-web-apps project, we recently focused on hardening our application's perimeter by refining our security configuration. As our project grows, moving beyond basic defaults toward a more structured, granular security model has become essential.
With the expansion of our API endpoints, we faced the classic
Starting a new project is always an exercise in balancing structure with momentum. For the Ryuu-no-Mi online store, the initial push was focused on establishing the core technical scaffolding that will support the application as it scales.
When laying the groundwork for a new web project, the primary challenge is deciding which files to define first.
Maintaining a clean separation of concerns is the difference between a project that evolves gracefully and one that becomes a tangled web of dependencies. Working on the Ryuu-no-Mi/marketplace project, we recently underwent a significant refactor to transition the codebase toward a formal Hexagonal Architecture (Ports and Adapters).
In the recent development of the Ryuu-no-Mi/davantedent-gestion-citas project, we focused on establishing the core HTML architecture. A clean, semantic base is critical for any management application, as it dictates how data is organized and how the user interacts with the system.
When starting a new project, we often prioritize speed, but
Maintaining a clean, professional appearance is vital for project documentation sites. Recently, I focused on refining the visual presentation of the Ryuu-no-Mi project by updating its underlying theme configuration.
When working with static site generators, the theme serves as the backbone of both layout and typography.
At Ryuu-no-Mi, the Gestion-de-flotas project focuses on modernizing our fleet management ecosystem. A critical component of this effort is ensuring secure and reliable access for our team. We recently completed a significant update to our authentication flow, transitioning to a robust token-based system to handle user sessions more effectively across our Vue.js-based frontend.
In the Ryuu-no-Mi/Master-Spring-Boot-3-web-apps project, maintaining clean data access logic is essential for application reliability. Recently, I focused on addressing inconsistencies in how we verify user existence within our data layer, specifically refining our usage of repository patterns.
When building web applications, a common requirement is checking
Licensing your project is often the step developers forget, but it is the single most important action for determining how others can interact with your work. Recently, I focused on the Ryuu-no-Mi/VisitALO-Control-de-presencia project, an attendance tracking system, to ensure that the intellectual property and usage rights were clearly defined from the start.
Authentication is the gateway to any application. If the front door is broken, the entire experience falls apart before it even begins. I have been working on the Ryuu-no-Mi/visitALO_Front project, where the primary objective was to establish a solid foundation for user access through clean, scalable components.
When implementing login and registration,
