I've been an avid user of this website for years, but I've never committed to writing anything on this platform. Until now.

Recently, I've decided to revamp my portfolio website in an effort to boost my online visibility and connect with clients and colleagues. One of the biggest goals of my portfolio is maintaining a blog where I discuss some of my recent work and share my opinion on the latest web technologies and other interesting trends in software development I've had experience with over the years.

After testing several CMS platforms like WordPress and Strapi, I wasn't convinced that a CMS would be necessary for my portfolio. I ultimately decided to build my website with Nuxt and Vue. Although hosting a CMS is pretty cheap, I didn't want to commit to a monthly cost. Deploying a static site to Netlify made the process simple and free.

Utilizing @nuxt/content, managing website content was a breeze. When I started adding blog articles as markdown files in the codebase, things started to get messy. This is where I started to doubt my decision of not using a CMS. I'm a stickler for organization and maintaining a separation of concerns so having all of these markdown files embedded in the codebase was starting to drive me insane. This led me to start searching for a better way.

I've read many articles on this website over the years and coincidentally, I came across an article on how to use the dev.to API. I found a way to manage blog content without adding clutter to the codebase. Now I'm able to focus on my writing quality content without worrying about the inner workings of the codebase and save a few dollars in the process.

I just wanted to share some insight on my decision making in this process. If you're interested in learning more about me or my experience as a software engineer, just click here. My website is still in active development so some things are still in flux.