Documenting code, one commit at a time.
We have officially kicked off the development of the dona-ana-backend project. Our goal is to create a robust and maintainable API service that can grow alongside our requirements. To achieve this, we have decided to utilize Strapi as our content management foundation, wrapped in a Hexagonal Architecture pattern.
Starting a new project often brings the
At dona-ana-backend, we manage the infrastructure for our "Menú Digital Doña Ana" project. As the system grows to include more sophisticated data management using Strapi and the Repository Pattern, the need for clear documentation has become critical.
While our REST API allows for clean communication between services, new team members faced a steep learning
In the ongoing development of the dona-ana-backend project, we recently focused on strengthening our Cross-Origin Resource Sharing (CORS) configurations. As our application grows and interacts with various frontend interfaces, ensuring that only trusted domains can communicate with our API is critical for security.
CORS is a security feature implemented by
When managing assets like images in a headless CMS architecture, environment parity is key. Recently, while working on the dona-ana-frontend project, we addressed an issue where image URLs were incorrectly resolving in production, leading to broken visual assets.
In local development, assets often live at relative paths or within a local server root.
Every project begins with a vision, but that vision often remains trapped in the developer's head until it is codified. Recently, I shifted my focus toward the dona-ana-frontend project to ensure that the architecture and purpose of the codebase are clearly defined for anyone who might contribute in the future.
When working with modern stacks like Tailwind CSS for
Waiting is an inevitable part of the web experience, but how an application handles that wait defines the perceived performance. In the dona-ana-frontend project, we focused on refining the user interaction model by introducing visual feedback during data fetching and implementing local caching for the navigation menu.
Working on the dona-ana-frontend project involves keeping a clean separation between data management and UI rendering. When maintaining a project that utilizes a headless CMS like Strapi alongside a modern styling framework like Tailwind CSS, the primary goal is to ensure the codebase remains maintainable as new features are added.
Starting a new project often feels like standing before a blank canvas. With the initialization of the dona-ana-frontend project, I have begun laying the foundation for a responsive, high-performance web interface. Choosing the right architectural components from day one is the difference between a scalable application and one that becomes a burden to maintain.
Building and maintaining a personal portfolio like joel-rodriguez-portafolio involves balancing code, design, and content. While feature development often takes center stage, it is crucial not to overlook the administrative side of asset management. Recently, I focused on standardizing the documentation for personal assets by explicitly adding copyright notices.