“Vibe coding” means describing what you want and letting an AI assistant write most of the code. I used it to rebuild this website, and here is what worked and what didn’t.
The project
My old academic website was hard to update and wasn’t under version control. I wanted to move it to Jekyll, a static site generator, so that:
- every page is a simple Markdown or data file,
- all changes are tracked in Git,
- the site is fast and secure, with no database or server code to maintain.
First I downloaded a copy of the existing site with HTTrack (a website copier I first used as an undergraduate), which gave me its HTML, CSS, JavaScript, and images. Then I used GitHub Copilot with Claude Sonnet 4 to convert it into a Jekyll site while keeping the content and the responsive design.
How much did the AI do?
About 90% of the code the AI generated was usable as is. It was very good at the repetitive work: turning pages into layouts and includes, writing Liquid templates, and moving content into data files. That saved a lot of time.
The other 10% needed me. Quality varied from task to task, so I had to review everything it wrote for correctness, security, performance, and maintainability.
Where AI fell short
- Debugging. When something broke in a non-obvious way, asking the AI to fix it often went in circles. Finding the bug myself was faster.
- Site-specific needs. Academic websites have their own requirements, such as publication lists and teaching pages, and the AI often didn’t understand them without a lot of explanation.
- Polish. User experience testing, page speed, and accessibility checks still needed human judgment.
What I’d recommend
Use AI to get the structure and first draft in place quickly, then use your own skills to fix, customize, and optimize. AI speeds up a programmer; it doesn’t replace one, and you still need to understand the code to work with it well.
The result is the site you’re reading now, gmujtaba.com.