Documenting code, one commit at a time.
Working on the Harry Potter app has been an exercise in balancing thematic design with maintainable styling. Recently, I focused on refining our CSS implementation to ensure a more cohesive look across the board, specifically targeting layout spacing and component responsiveness.
As our project grew, our styling started to feel like a collection of patches.
For many developers, the journey into web development starts with a single index.html and a growing collection of scripts. That is exactly where I found myself with the tercera-pre-entrega-js project—a milestone dedicated to consolidating core functionality and refining the user interaction layer.
When a project grows from a simple prototype to a functional
Every large-scale application begins with a single line of code. Whether you are building a complex cross-platform application or a simple utility, the foundation you lay in your initial commit sets the tone for your development workflow. Recently, I began working on the Naty-Arevalo/app-react-native project, leveraging the modern standard for mobile development to ensure a smooth transition from
Working on the FutbolFem project, a platform built with React, Next.js, and Bootstrap, taught us that technical debt isn't just about functionality—it's about how efficiently your codebase evolves. Recently, we focused on a comprehensive refactoring effort to clean up our component logic and optimize performance.
As our components grew in
Starting a new project often feels like standing before a blank canvas. Recently, I began working on the Entrega-final-reactjs-arevalo project, a web-based application designed to integrate modern frontend practices with a robust component architecture. The initial phase focused on setting up a performant environment using Vite for fast builds and React for declarative UI
In the Naty-Arevalo/FutbolFem project, maintaining visual consistency is as important as the underlying logic. A recent issue regarding incorrect shield icons (escudos) highlighted a common pitfall: how we manage static assets within a component-based architecture.
When working with team logos or crests in React, it is easy to fall into the trap of using hardcoded relative paths
When building the FutbolFem project, a key objective was to create a visually engaging interface to showcase sports photography. We needed a layout that was not only aesthetically pleasing but also robust across various device sizes. The initial implementation lacked a structured way to display a collection of images, leading to inconsistent spacing and layout overflows on
Every great project begins with a single commit. The FutbolFem project has officially been initialized, marking the start of a new codebase dedicated to the world of women's soccer. This initial setup establishes the repository architecture, laying the groundwork for a modern web application.
By leveraging the React and Next.js ecosystem, the
Communication is the bridge between a community and its platform. In the FutbolFem project, we recently identified a persistent issue where the contact form was failing to process user submissions reliably. When a form breaks, it acts like a locked door for your users—frustrating and invisible until you try to use it.
Our investigation focused on the event
Maintaining a React application often involves iterative refinement of state management and component logic. In our recent work on the Naty-Arevalo/Entrega-final-reactjs-arevalo project, we focused on cleaning up component logic to ensure a more predictable UI lifecycle.
Often, small adjustments to how data flows through your components have the largest impact