PROBLEM STATEMENT

I wanted to build my portfolio using a CMS because it would make updating and adding new content much easier. My previous hardcoded website made even small changes difficult, so moving to a dynamic system like WordPress was a more practical and scalable solution.

The project ran over 11 weeks, where I built a custom WordPress theme from the ground up. I started by setting up hosting with Bluehost and designing the layout in Figma, then implemented key WordPress features each week. The scope included building a full template hierarchy with all the main page types. Since it was a solo project, I handled everything myself; planning, design, and development all while working within WordPress’s structure and meeting course requirements.

MY ROLE

This was a solo project, so I was fully responsible for everything from start to finish. I designed and developed a custom WordPress theme for my portfolio site, handled all the planning, set up hosting with Bluehost, and built out the entire template structure. While we had reference files from the professor to guide us, I implemented everything on my own.

TECHNOLOGIES

  • Languages: PHP, CSS, HTML
  • Platform/CMS: WordPress
  • Design Tool: Figma
  • Hosting: Bluehost
  • Version Control/Repositories: Github

PROCESS

The project ran as a hands-on, week-by-week build. I designed the site layout myself in Figma at the start of the course, though there were figma templates and previous theme examples provided. Each week, we were introduced to new WordPress features or concepts, and I would implement them directly into my custom theme. We also did have access to reference files from the professor, but the design and development were entirely my own. It was a very self-driven process, which gave me full control over how the site looked and functioned.

RESULTS & OUTCOMES

In the end, the project was a success—I built a custom WordPress theme that I’m actually using for my portfolio site. I hit all the goals, including creating a full template hierarchy and improving my skills in PHP, CSS, and WordPress. The biggest takeaway was how helpful it is to plan ahead when working with a CMS, and how much easier it is to manage and scale content compared to hardcoding everything.