A New Chapter: Moving My Portfolio to Jekyll After 8 Years
After 8 long years of maintaining my portfolio in plain HTML, I’m excited to announce that I’ve finally migrated it to Jekyll! 🎉
Why the Change?
For nearly a decade, my personal site remained a static HTML page, manually updated with each career shift, project addition, and content tweak. While it served its purpose, maintaining and expanding it became cumbersome. I needed a solution that was:
- Easier to update – No more manually editing multiple HTML files.
- Scalable – A framework that could grow with my evolving needs.
- Efficient – Leveraging templates and Markdown instead of raw HTML.
- Future-proof – Supporting blog posts, projects, and seamless content management.
Why Jekyll?
Jekyll is a static site generator that integrates seamlessly with GitHub Pages, allowing me to:
- Use Markdown for content, making writing and updating posts a breeze.
- Take advantage of layouts and includes to keep my site DRY.
- Easily deploy updates via GitHub without complex configurations.
- Customize my site with themes and plugins while maintaining full control.
What’s Next?
Now that my portfolio runs on Jekyll, I plan to:
- Regularly update my blog with insights on data engineering, AI, and tech.
- Share open-source projects and contributions.
- Improve the site’s performance and design iteratively.
This transition marks a fresh beginning, and I couldn’t be more excited about the possibilities ahead. If you’re considering moving to Jekyll or have any tips, let’s connect!