Over the last 25 years my blogging platform moved from GeoCities to Blogspot to WordPress, and finally landed on a self‑hosted site built with Hugo and hosted on Netlify. Each transition helped me learn and understand different technologies. For the past two years I wanted to try the Astro web framework, but learning and implementing a new stack was put on the back burner.
For me, 2025 was the year AI matured for application developers. The quality of generated code improved, allowing more focus on problem solving rather than boilerplate and increasing overall throughput. Tools I used or evaluated included GitHub Copilot, Chime, Cursor, and Antigravity. By the end of 2025, Google’s Gemini 3 was leading and Antigravity IDE looked promising, so I started a hobby migration project.
Planning
I wanted AI to drive the process. This began with a brainstorming session with Gemini to define a migration plan. There were three primary asks: (1) feasibility, (2) a migration plan, and (3) additional recommendations. I supplied a spec describing the current architecture and deployment pipeline.
After a few interactions, Gemini produced a detailed plan and confirmed the migration was feasible. Based on my criteria it suggested moving hosting from Netlify to Cloudflare (Pages + Workers) to keep future serverless options open. Astro also fit the requirement for potential interactive blog features.
Antigravity was chosen for the following reasons: (1) it looked promising based on what I had read, and (2) it is part of the Google stack, which helped keep choices minimal.
The agreed stack:
- Antigravity IDE (primary), with VS Code + GitHub Copilot as fallback
- Astro as the web framework
- Tailwind CSS for styling
- GitHub for source control
- Cloudflare Pages for hosting and auto‑deploys
I reviewed the plan with ChatGPT, made minor adjustments, and then began execution.
Execution
The original Hugo setup was slightly complex: a hugo-elements theme project plus a site project that customized it. I initially migrated only the site project, so styles were broken because theme files were missing. After adding the theme project to the workspace the migration made more sense.
The process required a few iterations of review and fixes. Antigravity itself was somewhat buggy — the Agent Manager crashed occasionally — but using the right panel (similar to Copilot) worked around the issue. After a few cycles the migration completed in roughly half a day and the site ran locally.
Improvements
The original Hugo site was hand‑coded over many years and contained small, important features I hadn’t previously implemented. I documented these use cases as enhancement specs for the migrated project. Antigravity implemented many of them quickly, using Tailwind CSS for styling — for example, tweaks to the left navigation.
Content search was another enhancement. Antigravity recommended Pagefind and, after some styling feedback, it produced the desired result.
Deployment
After pushing the project to GitHub, I set up the deployment pipeline. AI assistants provided concise deployment steps; however, some guides can be outdated — I recommend asking the assistant to verify the latest documentation when following such steps. With that in mind, connecting the repo to Cloudflare Pages was straightforward and the site deployed successfully.
The solar-wind site is now live at https://www.sathishkv.com. It feels faster, cleaner, and ready for future enhancements.
Thoughts
- AI is enabling faster problem solving; many coding tasks can be automated.
- Coding knowledge remains important for reviewing and validating generated code, though higher‑level workflows are shifting toward natural language.
- With a focus on problem solving, more applications will be reimagined and consolidated across stacks.
- If AGI becomes available, the landscape could change dramatically; for now, AI is limited by energy and processing‑power constraints.