Posted on 2013-02-23 Edit on GitHub
Until yesterday, I had my blog set up at the subdomain www.blog.tianxiangxiong.com, but nothing at the site root, www.tianxiangxiong.com. However, this subdomain simply pointed to the files at my subdirectory, www.tianxiangxiong.com/blog. This will cause me a lot of headache later on.
Previously, the plan was to use a web development framework like Django to create my homepage. However, after my computer got stolen (long story), the plan simply petered out. It wasn't that I lost all my work--in fact, I hadn't done much besides familiarize myself with the basic aspects of Django. It's more so that I am forced to use the lab computer I acquired as part of my Pratt Fellows research program as my primary computer, and I don't feel that it's appropriate to install a lot of non-work-related software on it.
Therefore, after allowing my homepage to languish for about a year, I decided to simply use WordPress to power my entire site.
The process was simpler than I expecgted. I simply followed the instructions at the WordPress Codex, Giving WordPress Its Own Directory. Though the title is rather ambiguous, it's a guide intended for individuals who want WordPress to power their site root, but have it in its own subdirectory, e.g. www.tianxiangxiong.com/blog, to avoid cluttering up their root directory. The section relevant to me is "Using a pre-existing subdirectory install".
It was an easy process for the most part, but I did encounter a few problems. Recall the previous mention of subdomain and subdirectory. The key here is to use the latter for the WordPress Address URL and not the former, or else functions like previewing posts will get broken.