This writeup has even less structure than the last one, because these mistakes don't range in the order of biggest to smallest (even if I may say so for hyperbole). And even then, a lot of these mistakes were important for my growth as a programmer. All of these things that occurred may be mistakes, but they were my mistakes. Perhaps you shall make different mistakes. Perhaps you'll have a different programming style. In any case, this is mostly just a writeup of things I perceive as 'mistakes' and how they were important they were for me to understand what the hell I am doing.
My design kept changing again and again through development. Not deciding on a design from the beginning made it such that whenever something in particular gave me trouble, I would make my goals less ambitious. In many cases, this is a good thing, as realism is something extremely important to have. However, my ideas, although ambitious, weren't world-shatteringly unrealistic. As such, whenever I came across a difficulty, I would balk at it and decrease the height of the blueprint. The result of this was that the current website, although extremely functional, is quite dissatisfactory for me. However, it wasn't all bad. One of my mistakes had me spend 3 days on a cosmetic design even before I implemented the functional aspects of the design. It may have been a waste of time, sure. But the truth is, I do this for fun. I do this for the love of the game. So the time wasn't truly wasted, it was just invested in such a way that did not lead to a quantitative growth in the website. I learnt great a many things from that endeavor (looking back, it was barely an endeavor and just a small thing that I got stuck on), but it was necessary for me as it taught me how to approach tasks in which order of difficulty/priority.
This one may just be an oversight instead of being an outright mistake, but I'm going to include it regardless. Not implementing a global styles CSS file has made it such that each and every file has dozens of different styles that have no coherence to them with respect to different files. As such, the properties tab ends up being a huge mess of inheritances and such. Implementing a global styles CSS file could have its own hassles, however. I foresee an issue with lack of readability, because any time a class is used, one has to go to the global styles file to refer it, and may become confused by other classes present there, as well as their relations with each other. Despite this foresight, I have a feeling that it has manifested itself as a representation of my own lack of skill. There can be a lot of easy solutions to this counter-issue.
It is quite easy to call this a mistake, because what do you mean my website looks terrible on phones and tablets! What a travesty! A lot of people use phones and tablets these days to read stuff on the move! However, one thing I did not consider when I called this a mistake is the fact that I am a beginner. Had this not been my first website, and had instead been my third or fourth, this is definitely a valid self-criticism to consider. This being my first website gives me great leeway to learn and understand these issues. I personally use the laptop more than my phone, and as such, I didn't consider phone users or tablet users from the beginning. It is a bias that was spawned by personal experiences, and is completely fine, as long as I keep in mind to fix it going forward.