Documenting code, one commit at a time.
Building a personal portfolio is often the first real test of a developer's ability to maintain a codebase that is both scalable and readable. In the recent development of the Ryuu-no-Mi/my-portfolio project, I focused on refactoring the existing architecture to better accommodate new features and content.
When we start a new project, we
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
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.
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.
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 Inmotech Frontend project, enhancing user experience often involves making data easily discoverable. A recent feature focused on implementing robust search and filtering capabilities, addressing the common challenge of navigating large datasets efficiently within a web application.
Imagine sifting through a library where all books are simply piled together.
In the Inmotech-Frontend project, which facilitates the management and creation of property listings, a recent update focused on enhancing data integrity and user experience during property submission. This change was primarily driven by new backend requirements that mandate specific fields for all new properties.
Previously, the
On the Inmotech Frontend project, we recently tackled a common challenge in API communication: inconsistent URL query parameter serialization. This often arises when integrating with backend services that expect a specific format for array parameters, differing from the default behavior of popular HTTP clients like Axios.
Ever found yourself debugging an API request only to realize the backend
In the fast-paced world of web applications, friction in user authentication can be a deal-breaker. A complex signup process often translates directly into lost users. This is why simplifying access, like integrating social logins, becomes a critical enhancement. Our Inmotech-Frontend project recently embraced this philosophy by integrating Google OAuth2, offering users a quick and secure way
