Yunus Emre Vurgun's Blog

 I think it can be a great idea to start off by explaining why me as a computer programmer ended up creating this blog/website on Blogger and not on a common hosting provider such as HostGator or NameCheap.

Well, as you may have guessed mostly the hosting costs and domain costs are the primary reason behind this decision. 

As of now I already used lots of shared hosting packages with quite enough storage and bandwidth limits and it was amazing to take things out of the localhost to an actual server.

I still have an active hosting subscription on one of my favorite hosting providers that will not expire until the end of this year.

I already make websites with PHP & JavaScript so why not make my personal blog the same way? Right?

I was not sure if I wanted to make a Blogger website as it is pretty much limited to front-end customization and plus even the front-end takes extra effort to customize compared to a regular Linux hosting with a Cpanel CMS.

I ended up choosing Blogger after all (as you can see). 

I already mentioned that the main motive for this decision is the hosting and domain costs that I need to keep track of and also of course because this blog aka. website is about writing articles on programming and explaining how to do certain things with certain technologies.

I could have used WordPress and I mean ".com", so that it has free hosting plans similar to Blogger. The truth is I don't really like WordPress. The plugins and everything are cool but I rather build my own ecosystem than to rely my projects on WP.

If I am building a website for commercial purposes, I don't think I can be happy being limited to WP. 

What I did last year was to have a folder in one of my demo websites to WP and other folders had their custom scripts. So WP for "/blog" and everything else had its own PHP going on.

Anyways, I really get stressed out keeping track of hosting and domain renewals (yes there is a chance I am broke) and that is the main reason why I chose Blogger for this website.

If I am not going to run my scripts live on a server, why would I rent one just for my articles?

I already test every web project I make on my local machine and then upload them to my GitHub.

Why an extra stress? 

Last month I had this PHP project that I wanted to test out and I felt like I had to not only test it on my local machine but also on a shared hosting. I went for it and it was great as always but then I took it down and redirected the domain I bought for it to my GitHub. Because I realized I would need to pay every month for that single web project. It is already on my GitHub and anyone can run it on their own machine so why a hosting right? That's when I realized I really don't need to pay for shared hosting for every little thing I want people to take a look at. 

 I am pretty happy with this Blogger / Blogspot blog here as of now actually. Yes, I cannot control the backend and yes the front-end is also very limiting, but it serves the purpose: a blog.

If you wonder what GUI customizations I made for this website, here are some of them (interestingly I didn't rely on JavaScript for the whole styling this time *.style.display='block';):

<meta content='width=device-width, initial-scale=1.0' name='viewport'/> <style> .content-inner { border: 5px solid; border-radius: 10px; border-image: url() 30% round; } .content-cap-top, .cap-top { display: none; } @media only screen and (max-width: 884px) { * { font-size: 25px; transform-origin: 0 0; } } .profile-img { border: 0px solid; border-radius: 30px; } .widget-content { background-color: black; color: white; border: 0px solid; border-radius: 4px; } .fauxcolumn-inner { border: 1px; border-radius: 23px; } .blog-posts { background-color: black; border: 1px solid black; border-radius: 10px; } .uncustomized-post-template { padding: 8px; } </style>