Dev Log: The Evolution of a Trophy Guide Ecosystem

Engineering Evolution: The Ignition Point

My journey began like many others: I used a default Blogger theme, relying entirely on the "Compose" visual editor. For a long time, I didn't touch the HTML view. I was comfortable, but I knew the foundation was hidden from me[cite: 1].

The "ignition" for my technical evolution was a school assignment that required me to build a website from scratch. I asked if I could use my existing trophy guide site as the project, and was given the green light. That was the moment I finally felt safe to dive into the HTML. I had the knowledge from my textbooks, and for the first time, I looked under the hood[cite: 1].

What I found was "div soup"—a dense, unformatted mess of broken tags and unnecessary <br> elements injected by the visual editor. Because I finally understood the language of the web, I knew exactly how to fix it. I refactored the entire codebase, stripping out the bloat, adding proper indentation, and transforming the site into clean, readable, and functional HTML[cite: 1].

The CSS Evolution: Moving Beyond Templates

Once the structure was clean, I turned my attention to the look and feel. I started by using AI to generate CSS for a separate, custom-built page, which led to a realization: Why couldn't I do this for my own blog?[cite: 1]

I began "injecting" custom CSS to override the default theme, piece by piece. By iterating with my AI collaborator, I moved away from template constraints and into a fully customized, responsive design that reflected the aesthetic of the games I was writing about[cite: 1].

Engineering Functionality: The JavaScript Pivot

My technical growth hit a turning point when I began experimenting with JavaScript via JSFiddle. I realized that my guides didn't just need to look better—they needed to be more functional[cite: 1].

I challenged myself: Could I build a native, in-post search bar to filter content in real-time? That question led to a total rebuild of my post architecture. I moved to a custom-engineered setup relying on DOM manipulation. I stopped treating the blog as a static document and started treating it as a dynamic application[cite: 1].

Refining the User Experience (UX)

Now, my development focus is on optimizing the trophy hunting experience:

• Visual Layouts: I experiment with post layouts that balance aesthetic appeal with high-density technical information[cite: 1].
• Dynamic UI Components: I’ve implemented a tagging system that uses JavaScript to add contextually relevant labels and tooltips to trophies. This helps users identify requirements at a glance, turning a wall of text into a highly scannable, user-centric guide[cite: 1].

The Takeaway

I didn't start this to build a portfolio. I started this because I have a passion for gaming and a drive to solve information organization problems. Today, this site serves as my living engineering log—a testament to what happens when you stop relying on "Compose" mode and start taking ownership of your code[cite: 1].