Launching My First Tool: Compress PDF Online! 🛠️

📢 Big day at Code Cultivation! Today I’m thrilled to launch my very first tool: Compress PDF online.

It’s been an exciting journey building this — from designing a simple interface to making sure it works smoothly for users. This tool is just the beginning of what I plan to create here: practical, developer-friendly tools that actually solve real problems.

Seeing it live for the first time is incredibly rewarding. It makes all the late nights and learning curve totally worth it!

This is the start of many more tools and features to come. Step by step, Code Cultivation is becoming a playground for building useful developer SaaS tools. 🚀

Migrating Blogs with Nuxt Content 📚

📚 Today marks another milestone in the remaking of Code Cultivation — I’ve begun migrating my old blog posts from another platform into this new site!

I’m using the Nuxt Content module, and honestly, it’s been super fun and easy to configure. Setting up links, organizing content, and handling markdown files feels smooth and natural. It really takes away the hassle of managing a custom CMS while still giving me full control over the structure.

A few things I love so far:

• ⚡ Writing directly in Markdown and seeing it rendered instantly
• 🔗 Easy linking between posts with simple configs
• 🎨 Flexibility to customize layouts as I grow the site
• 🛠️ No need for an external CMS — everything lives right inside the repo

This is still early days, and many pages are placeholders for now. But moving my blog over makes Code Cultivation feel more alive — it’s finally becoming both a blog and a playground for building out developer-focused SaaS tools.

Step by step, it’s starting to take shape. 🚀

Figuring Out Stage & Prod Workflows ⚙️

⚙️ Over the past few days, I’ve been working through the setup of stage and production workflows for Code Cultivation on Azure Static Web Apps.

At first, it was a bit confusing. The default GitHub Actions workflow assumed everything should deploy straight to dist, but I wanted more control. I needed a clear separation between my stage environment (for testing and experimenting) and production (for the live site).

The journey looked something like this:

• 🔍 Realizing the default workflow wasn’t enough — I kept seeing errors about deployment paths.
• 📝 Learning that I could regenerate or edit the workflow file directly in GitHub.
• 🚦 Figuring out how to configure the workflow so only the right branch (stage or prod) gets deployed.
• 🖐️ Finally deciding to use manual deployments for the stage environment so I could test changes without affecting production.

It took a few tries (and some trial and error), but now I’ve got a setup where stage and prod deployments are cleanly separated. This gives me confidence to experiment more freely with the new Code Cultivation rebuild — especially as I explore Nuxt 4 and slowly move from placeholders to real content and SaaS features.

This step may feel small, but it’s an important part of laying a solid foundation for where I want Code Cultivation to go. 🚀

The Remaking of Code Cultivation 🚀

🚀 Today marks a new chapter for Code Cultivation.

Originally started as a blog, I’m now remaking it into a blog + SaaS hybrid — a place to share ideas while also building tools that developers can use in their day-to-day work.

This rebuild is powered by Nuxt 4, and I’m excited to explore and learn more about it as I shape the platform. At this stage, the site is still in its early phase, with a lot of placeholder and sample pages left from the starter setup. Over time, I’ll gradually replace them with real content and features.

The plan moving forward:

• ✍️ Continue publishing articles and guides on the blog
• 🛠️ Build out SaaS tools aimed at solving practical problems for developers
• 🎨 Refine the design and remove starter/sample pages
• 📚 Share my learning journey with Nuxt 4 along the way

This is just the start of a bigger vision — evolving Code Cultivation into something more useful, practical, and developer-focused.