Weekly Update: A New Direction
A lot of changes before the end of the week, read below to learn about the latest updates.
What Was Accomplished
This week, I spent significant time addressing long-standing issues on my website, JorgeIglesias.com. The site was initially created earlier this year, and while it served its purpose, I hadn’t revisited it since getting it up and running. As I worked through the updates, it became clear that the original implementation, which relied solely on React, wasn’t ideal for a multi-page site. This realization, coupled with the opportunity to upgrade to Strapi 5, led me to a new decision: to rebuild the site from scratch as JorgeIglesias.com V2.
Here’s a quick rundown of what was resolved:
* Fixed Matomo integration for better analytics tracking.
* Refactored API calls for the Header and Hero sections to improve performance and maintainability.
* Addressed blog-related issues:
* Fixed blog post page layout.
* Resolved sorting issues for blog posts.
* Adjusted BlogCard size and added attributes for better presentation.
* Fixed a 404 error on footer links and resolved a link issue within the footer.
* Improved blog heading placement for a cleaner design.
* Refactored the footer structure for consistency.
* Created a new `README.md` file to document updates for V2.
* Set up Strapi configurations, including S3 storage, and added a social component for authors.
* Improved the deployment process for smoother updates and scalability.
What’s In Progress
As I worked through these fixes, I began laying the groundwork for the next iteration of the site. Currently, the following tasks are in progress:
* Migrating to Next.js and Strapi V5: The migration to Next.js allows for server-side rendering and better performance for multi-page applications. Pairing this with Strapi V5 will provide more flexibility for managing content.
* Configuring CORS for the API: This is critical for ensuring secure and seamless communication between the frontend and backend.
What’s Next
Moving forward, my focus will shift to implementing rate limiting for API requests. This is an essential feature to protect the site from abuse and maintain reliability as I continue to build out V2.
Leave a Reply