How I Built My Personal Portfolio Website Using Claude, Without Writing a Single Line of Code

 I have always believed that technology should work for people, not the other way around. And yet, for years, the idea of building my own personal website felt like something reserved for people with coding skills. I had the content. I had the story. I had the experience. What I lacked was the technical know-how to put it all together on a screen.

That changed recently. And the experience was something I feel compelled to write about, because I think a lot of people are in the same boat I was.

Where It All Began

I am a Project Manager and Customer Experience professional with over 22 years of experience. I have managed teams, led a team of Zendesk implementation consultants, managed 80+ client projects simultaneously, and built support systems from scratch. But ask me to code a website? That was not in my repertoire.

I had been wanting a personal portfolio site at vijit.in for a while. Not just a plain page with bullet points, but something that actually looked professional. Something that reflected who I am and what I bring to the table. Something I would not be embarrassed to share with a potential employer or a consulting client.

A colleague mentioned using AI for tasks like this. I decided to give Claude a try. What followed was one of the most surprisingly smooth experiences I have had in a long time.

Starting the Conversation

I did not hand Claude a detailed technical brief. I just talked to it the way I would talk to a person. I told it I needed a personal portfolio website. I shared my name, my professional background, and what I was hoping to communicate through the site. I wanted it to position me as a strategic problem solver with deep expertise in CX, service delivery, and project management.

Claude came back not just with a design but with an entire thought-through layout. It suggested sections for a hero area at the top, a core competencies section, an experience timeline, an impact numbers section, a case study, testimonials, and a contact section. It thought about what a visitor would want to see first and what would keep them scrolling.

That alone was impressive. It was not just writing code. It was thinking through the user experience the same way I would approach a CX project.

Feeding It the Raw Material

Once the structure was agreed upon, I started sharing my actual content. I uploaded my resume in PDF format and Claude read through it carefully. It picked up specific details that I might have glossed over if writing the content myself. The fact that I scaled the Egnyte support team from 1 to 18 specialists while maintaining 95% CSAT. The fact that I reduced customer churn by 30% through proactive escalation management. The fact that I managed 80+ Zendesk client projects simultaneously at peak.

These were real numbers from real work, and Claude wove them into the website naturally. The case study section, for instance, was written entirely around the Egnyte engagement and told a clear story: the problem, what I did, and the measurable results. That kind of storytelling structure is something I would have struggled to write about my own work because we often take our own achievements for granted.

I also uploaded my LinkedIn profile photo and my logo. Claude embedded both into the website file so they were part of the design from the start.

I shared the LinkedIn recommendations I had received from former colleagues and clients. Claude turned those into a proper testimonials section with the names and roles of the people who gave them.

The Back and Forth That Made It Better

Here is the part that I think people underestimate when they think about using AI for something like this. It is not a one-shot process. The real value came from the ongoing conversation.

After seeing the first version, I had feedback. Some of it was about content. Some of it was about design. And I gave that feedback the same way I would give feedback to a team member on a work deliverable.

For example, I pointed out that my designation at Xoriant was Senior Support Lead, not Operations and Delivery Manager. That distinction mattered to me because I did not want to misrepresent my official title even if my functional role went well beyond it. Claude updated it to read "Senior Support Lead, Acting Program Manager for Zendesk Clients" which was accurate and still communicated the scope of the role.

I gave feedback on the design too. The Skills and Proficiency section was stretching to the edges of the screen on both sides, which looked out of place compared to other sections. I described this to Claude and it identified the root cause: the section was using a proportional grid that pushed content to the full container width while other sections used fixed or narrower layouts. It fixed the column sizing so the skills section now sits centred and consistent with everything else around it.

There were smaller things too. A sentence that was repeated in two different sections. A label that said "EN, HI, MR, ML" for languages, which meant nothing to a visitor who did not know those were language codes. A button on mobile that was wrapping in a way that looked broken. The copyright year still showing 2025 when it should have been 2026. Each of these I flagged and Claude fixed, usually in seconds.

At one point, I sent a screenshot showing that the "Open to Opportunities" badge was overlapping with the quote block in the hero section. Claude explained that the badge was using absolute positioning that was designed for the old photo layout, and had not been adapted for the new design. It replaced it with an inline badge that sits naturally within the card. That kind of contextual reasoning was genuinely impressive.

Getting It Live on the Internet

Building the website file was one thing. Actually putting it on the internet was another.

Claude walked me through the entire process step by step. It explained what GitHub Pages is: a free hosting service where you can put your website files and they automatically become a live website. No monthly fees, no server to manage, nothing complex.

It told me to create a free account on GitHub, create a repository with a specific naming format, and upload my website files there. It reminded me to use the "Upload files" option rather than the built-in editor, because the editor has file size limitations that would cause issues with larger files.

Then came the part about connecting my own domain name at vijit.in. I had bought this domain through GoDaddy. Claude explained exactly what changes I needed to make in GoDaddy's DNS settings. It gave me four specific IP addresses to add as A records pointing to GitHub's servers, and a CNAME record for the www version of my domain. It told me to expect a wait of anywhere between a few minutes and 48 hours for these changes to take effect globally.

Within a couple of hours, vijit.in was live and showing my website. That feeling was genuinely satisfying. I had a professional portfolio site on my own custom domain, built entirely through conversation.

What I Learned from This Experience

A few things stood out for me as I look back on this.

First, you do not need to know how to code to build something that looks professionally coded. What you need is a clear idea of what you want to communicate and the ability to give specific, honest feedback. Both of those are skills I already had from years of working in customer experience and project management.

Second, AI works best when you treat it like a capable collaborator rather than a vending machine. The conversations that produced the best results were the ones where I shared real context. Why a certain metric mattered. Why a section felt off. What the actual truth was about my job title. That kind of input consistently led to better output.

Third, the iteration process is where the quality lives. The first version was good. The tenth version was much better. Each round of feedback sharpened something. That is no different from any other creative or professional work.

Finally, I was genuinely surprised by how much Claude thought about design as a discipline. It understood visual hierarchy, breathing room between sections, how content sitting at the edges of a screen feels less trustworthy than content that sits with proper margins. It thought about mobile responsiveness. It considered what a recruiter or a potential client would look for when landing on the page for the first time. These are not purely technical concerns. They are design and communication concerns, and Claude handled them thoughtfully.

If You Are Thinking About Doing This

If you have been putting off building your own website because you do not have coding skills, I would encourage you to try this approach. Come prepared with your resume, your photo, any recommendations people have written for you, and a rough sense of what you want the site to say about you. Then just start talking.

You do not have to get it perfect in one go. In fact, do not try to. Start with a version that covers the basics and then refine it conversation by conversation. You will be surprised how quickly it takes shape.

My portfolio is now live at vijit.in. Every number on it is real. Every story is mine. The only thing I did not do was write the code.

And I am perfectly fine with that.