Documenting code, one commit at a time.
In the Ryuu-no-Mi/Master-Spring-Boot-3-web-apps project, we recently focused on enhancing the frontend layer to better handle product data. Specifically, I implemented the findAll retrieval logic within our Angular product component, ensuring our view layer stays synchronized with the backend state.
Previously, our product component lacked a dedicated mechanism to fetch the
As our portfolio project grew, our component structure became increasingly tangled. We were managing static content within primary layout files, making it difficult to maintain and hindering our ability to implement internationalization (i18n) effectively. The lack of a modular approach was slowing down updates.
We initiated a refactor to decouple logic from the
Building scalable web applications often starts with a simple goal: get the data on the screen. While working on Ryuu-no-Mi/Master-Spring-Boot-3-web-apps, I found myself refactoring the frontend layer to move away from bloated controller-driven views toward a more maintainable, component-based architecture.
Initially, my approach involved bundling business
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, 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.
