Sunday, March 24, 2013

Starting Up a Website

I finally got my travel agent website domain registered (GoDaddy) and created a webpage via Weebly. It is at Fairytale Journeys by John. I thought I would get a quick website made up to at least have some type of web presence going on for my travel business - maybe just my contact info and a message stating the site was under construction. Once I got in to the Weebly site and started creating, I decided to do more than just a 'placeholder'.

Weebly makes it easy to design a webpage and you can get pretty creative with it, although their Themes (pre-designed pages) make a quick website possible. I started using a pre-designed theme and just filled in my info, pictures, links, etc. But, I have to admit, I have a little case of CDO (OCD, but with the lettters in alphabetical order, as they should be) and I couldn't stop there. I wanted to add my Facebook link - so I had to find that code to add in. Then I wanted to add a Twitter feed to the page. I decided I should start my own seperate Twitter account for my Fairytale Journeys by John business, rather than use my personal Twitter account. My personal account has a bunch of Texas Rangers, local sports stuff, and other humorous tweets and retweets that may not be business-focused. So I had to create the new Twitter account, get the code for the feed for the site, add it in, etc. That stuff adds up - time-wise that is. So my 'quick' website took about two days to get to a point that I felt I could publish to the interwebs. This was Saturday.

Sunday morning, I decided I needed a customized logo for the top of my page. So I fired up Photoshop and got to work. Several hours later, I had my new logo (yeah, I am not too proficient with Photoshop.)

My page is still a work-in-progress, or living document, whatever you want to call it. I am open to advice and suggestions - if anyone is even out there reading any of this stuff.

Oh, and I plan to attempt to try to somewhat do a few updates here and there (is that general enough?) on this blog.

1 comment: