Behind the Build: Launching PMTheTechGuy.com
June 12, 2025 · 3 min read
Welcome to PMTheTechGuy.com, a platform that has evolved from a simple class project into a dynamic space showcasing my work and insights.
Why did I build This Site?
As someone still exploring the world of automation, IT support, and developer tools, I wanted to create something beyond a traditional portfolio. I wanted to create a central hub that serves as a log of my journey, as well as a repository for all the content I've made, including projects, tutorials, blog posts, and tools. My goal is to build something that is more than just a résumé, but a platform that reflects my journey in technology.
The Stack
Building PMTheTechGuy.com from the ground up, I tried to prioritize modern tools and performance. To achieve this,
the core of the site is built on Next.js, which was chosen for its robust server-side rendering, API routes, and
flexible file-system-based routing that ensures a fast and SEO-friendly foundation.
For styling, I integrated Tailwind CSS, allowing for rapid UI development with a utility-first approach and resulting
in highly customizable, responsive designs. To bring the site to life with smooth, delightful animations, I'm currently
leveraging Framer Motion, inspired by techniques I picked up from Sam Selikoff's insightful videos.
Outside the core functionality, my blog content is powered by MDX, which enables me to seamlessly embed React components
directly within Markdown for dynamic and interactive posts.
For hosting and essential analytics, Vercel was the clear choice, providing easy deployment and important
performance-tracking tools. Every technology decision was aligned with my goals of achieving speed, simplicity,
and extensibility.
Challenges and Wins
When building this platform, I encountered a few hydration errors that sometimes stalled my progress. I had to carefully manage the server-side rendering of components, which should help me avoid misusing dynamic behaviors.
Another challenge I face was generating the Metadata. It took me several iterations to ensure blog posts had proper SEO metadata and as well as a fallback OG image.
Initially, my Markdown blog content seemed plain with no package installed. However, after I created MDXComponents,
which maps everything from headers to image tags, the content now feels cohesive and visually more appealing.
This approach allowed for more customization compared to simply using the @next/mdx package out of the box.
What's Coming Next
This site is just getting started. Soon I plan to:
- Add a full-text search for blog content
- Publish automation tutorials for Power Automate, Python, and AI workflows
- Roll out client tools for resume parsing and document extraction
If you've enjoyed reading this, check out:
Thank you for being part of the launch. This is just the beginning.