Today, I learned the difference between static websites and dynamic websites. What I have set up is a dynamic website, meaning that at any moment I can upload a project, and the website will populate using database queries. I thought this was something special, but it turns out that WordPress works the same way. A static website, on the other hand, is more like a PDF on the internet than a functional, interactive site.

As I researched more, I started asking questions about what to expect from a dynamic website. That’s when I came across the term "full-stack web developer." I’d heard this before, so I decided to dive deeper, seeking answers on how I could create something functional, like a virtual tabletop (VTT) or a web application.

Previously, my searches were focused on website management or software best practices. For example, I know I need to access my database and properly define a “project.” Right now, it’s just using a generic "portfolio" template, which isn’t very intuitive. If I had started with the basics instead of jumping to the finish line, I would already understand this process. In full-stack development, you build everything: the webpage, the scripts that communicate with PHP, the scripts that query the database, and all the other components in between.

I’ve had project ideas in the past, like creating a competitor to Tribal Wars or OGame. However, every time I looked into it, I realized I needed to learn four or five new skills to even get started. I thought this was unique to those projects and decided it wasn’t worth the effort. But today, I learned that these skills are fundamental for full-stack developers and apply to a wide range of dynamic websites. This realization changes everything.

Now, not only do I feel capable of tackling those projects, but the daunting knowledge gap feels worth bridging. These skills are useful for more than just tinkering with game ideas—they open doors to creating all kinds of websites. This feels like an opportunity for side income and a worthwhile adventure.

ChatGPT recommended a couple of books: HTML and CSS: Design and Build Websites by Jon Duckett, along with his book on JavaScript and jQuery. Funny enough, I’ve never heard of jQuery before, so that should be interesting.

At the time of writing, I’m on page 80 of Duckett’s 450-page HTML and CSS book. So far, I like how it’s organized and how it uses graphics to explain concepts. I’m not completely sold on the book yet, but I’ll know for sure once I finish. If it’s good, I might end up reading all three of his books.

It would be amazing to learn a new skill set and find the perfect resource for it on the same day. If that happens, I’ll blame ChatGPT for being such a helpful assistant.

Daydreaming about all this made me realize something: you don’t need to create a mobile app for your tools if you build a good enough web application. My wife once asked me to help her create an organizational app, but I found mobile app development intimidating and never got started.

With the skills I’m learning now, I can build a web server and create a planner app she can access from any device with an internet connection.