Making This Blog
Published at Jul 28, 2023
Table of Contents
Welcome to My Blog!
Hey, guys! My name is Jackson, and this is my first blog post on my brand-new, shiny blog site that I built myself. Crafting this first blog post felt like it took longer than building the entire site. It’s going to be a while before I can effortlessly churn out blog posts, particularly as I feel I’m too young and inexperienced to have the most credible opinions on certain topics. But without further ado, let’s delve into my thoughts on the creation of this blog and what I liked and disliked.
Previous Experiences
As a novice in web development, I’ve got to say, SvelteKit is my favorite thing in the world. Prior to creating this site, my experience was limited to vanilla HTML, CSS, and JavaScript. After mastering the basics, I dived into a project with a good friend of mine, who was an avid AngularJS user.
I despised it. It felt so clunky and neither fast nor enjoyable to create things with. I concede that part of it was my inexperience with using a JavaScript framework, and as I found a rhythm in creating components and using the Angular CLI, I became relatively quick at making things. Regrettably, the project was abandoned due to my being in the final semester of high school at the time, which required me to prioritize other aspects.
Hello, SvelteKit!
I must admit, SvelteKit has been a delight to work with, and I’m now reluctant to switch. Having dealt with AngularJS for the week that I used it, I can’t imagine parting ways with SvelteKit. The intuitive, “everything in one file” approach of Svelte as a framework resonated with me. I’m aware there are other options out there—like ReactJS and its meta-framework, Next.js—that may increase my employability, but for now, I think I’ll stick with SvelteKit. Alternatively, I may dabble with different things, only to discover that SvelteKit was the more efficient and intuitive choice and make a return. Of course, I’m highly biased, as this is literally the only framework I’ve truly immersed myself in, making me feel extremely comfortable with SvelteKit.
When I embarked on creating this blog, I didn’t have a clear starting point. Aside from the tutorial on the SvelteKit website, I had never really built a practical website that I was proud of, and I certainly didn’t want to mess this up. Thus, I naturally did some Googling and stumbled upon an excellent tutorial on creating a markdown blog using SvelteKit. Having never written in markdown, I wasn’t sure what to expect when it came to writing blogs. But I followed the tutorial, experimented whenever I found something intriguing and managed to do some pretty cool things. My complaints about SvelteKit are few and far between, although I will admit that the file tree can feel a bit overwhelming at times, but nothing the VSCode command palette can’t fix.
Conclusion
As I continue to learn and grow as a programmer, I’m proud to be able to document my journey on this blog. The fact that I built this blog myself only enhances this sense of accomplishment. I plan to experiment with the styling on this site and add more of my style to it, so watch this space. I’m not exactly sure who my audience is right now, but if you’ve made it to the end of this post, thank you for reading. Enjoy your morning/afternoon/evening/night!