Is There a Compelling Case for Placing Wordpress @ Root?

WordPress as index.htm versus installing @ WordPress.com/blog/?

[Webwork]

Other than "this website will be and act as a blog, now and forever, not matter what" I cannot see a good reason for installing WP "at root", i.e. at default.htm/index.htm.

It seems to make more sense to install it at DomainABC.com/blog/ - in the blog directory.

Am I missing anything?

[callivert]

You're not missing anything. You can install wordpress in any subfolder or subdomain you like.
If there is a compelling reason, it is the same reason as having any type of homepage at the root. I personally haven't questioned this much, I admit, because "that's how everyone else does it."
Not all websites operate in the root directory. The Godaddy site is the first that springs to mind, that redirects you to a folder. I've seen blogs that do what you describe as well.
Obviously, if you do install in a folder, have a redirect in place from the root.

[Go60Guy]

If the site is intended to be a blog site from the get go, you can simply install WP in the root. If you need the home/index page to be sticky, there's a plugin that can accomplish just that as well as a function within WP where you can choose that option. Many WP blogs are set up that way.

My own practice is to use a folder for the blog only where the site is already a static html site or where I need it to be static at the outset.

[Marcia]

Matt Cutts has suggested not putting it in the root, in case it's ever decided to put something else on the site also.

[reprint]

If you are using wordpress as a blog addition to a static website, then put it in a folder.
If your site is going to be a wordpress blog site, then put it in root
You can also make your website in wordpress as a CMS where you put it in root but you can use a "page" as the front page and point the blog to a section within it under options. The combination of "pages" and posts can make a website with a blog all content managed.

[Webwork]

Thanks for all the input.

Has anyone ever intalled WP @ root and found that that decision made life thereafter increasingly complex as "the blog website" grew?

Anyone have a tale of woe or cautionary tale?

Is there a compelling reason to opt for installation @ root? "Yes, do that IF . . . "?

I'm pretty much convinced that all installations should be in their own directory and not @ root . . except . . I have to wonder about the future evolution of WP. At some point its development may deflect more towards CMS than strictly blog. Maybe never, but never say never - right? :)

Alrighty, sub-directory it is . . unless a force of nature arrives to alter the landscape. You out there, Ms. or Mr. Force of Nature? :)

Thanks again.

[Marcia]

You can also make your website in wordpress as a CMS where you put it in root but you can use a "page" as the front page and point the blog to a section within it under options. The combination of "pages" and posts can make a website with a blog all content managed.

That is an outstanding idea! You've just solved a problem for me with that suggestion. Thank you!