Okay I have to be honest: I wasn't focusing on my website very well. I wasn't productive. I wasn't serious. In fact, I wasn't enjoying it.
Remember the post that I written, it was supposed to be a site for boys and the next two posts was the beginning of it. Well actually, this site started out as a personal site just like other popular people have. Apparently, the site dwell into my life instead. I talk about why I got a sinus infection, what I got for Christmas, what I eat at lunch, among other things.
Before I purchase this domain, I wasn't into the website world anymore as I was on much of the 2000s, but rather in the writing world, where I was writing stories (which emerged and then unfinished) that are either trying to be different from the teenage genre or include action-oriented elements in it. And as a result, most of my website have been involved with my life. To be honest, I wasn't interesting in blogging. I'm not creating a blog, I'm creating a website. But since I don't have the money to invest, my website is powered by Google's Blogger site instead.
One of Malcolm Franokuski's former blogs operating from November 2014 - February 2015.
Showing posts with label website. Show all posts
Showing posts with label website. Show all posts
Sunday, January 25, 2015
Friday, January 9, 2015
Launching a sub-domain in this particular domain wouldn’t work at all
Last Monday, I was getting ready to launch a sub-domain. But after setting up a blog, I realize that there’s a problem: there is no way you can get a sub-domain from a domain that has been connected to a third-party blogging site.
At first I though it was easy. You just put the same IP code into the sub-domain and you launch it through Blogger. But it turns out that it wasn't the case. Usually it takes under about five or six minutes to get a domain updated, but in this case of a sub-domain, it actually took longer than expected.
At first I though it was easy. You just put the same IP code into the sub-domain and you launch it through Blogger. But it turns out that it wasn't the case. Usually it takes under about five or six minutes to get a domain updated, but in this case of a sub-domain, it actually took longer than expected.
Subscribe to:
Posts (Atom)