{"id":420,"date":"2020-05-23T11:41:25","date_gmt":"2020-05-23T11:41:25","guid":{"rendered":"https:\/\/knight.domains\/support\/uncategorized\/subdomains-vs-subdirectories-2\/"},"modified":"2022-07-15T20:03:52","modified_gmt":"2022-07-15T20:03:52","slug":"subdomains-vs-subdirectories","status":"publish","type":"post","link":"https:\/\/knight.domains\/support\/subdomains-vs-subdirectories\/","title":{"rendered":"Subdomains vs. Subdirectories"},"content":{"rendered":"\n

When you’re first getting started with a new space on a new Web host, you might think of yourself as owning a small \u201cterritory\u201d of the Web. Everything you place in your public folder on the server becomes available for anyone on the Web to see (assuming they know the address of your site and the files you’ve placed there).<\/p>\n\n\n\n

If you’re just putting up a handful of static, HTML pages which you want to make available to colleagues, friends, or family by sending them links, then working with this large, unorganized space may work. But as soon as you get to the point where you want to organize your site, you’re going to need a new strategy.<\/p>\n\n\n\n

Consider this scenario: you want to have a personal blog on your new Web space, where you share pictures and short written pieces with family, friends, and colleagues. In addition, you’re working on a large research project that requires you to build a Web-based repository of digital images related to your discipline. You want to use one application (say, WordPress<\/a>) to manage your personal blog. For your research project, you’ve settled on another open-source application (Say, Omeka<\/a>). Both of these are applications that need to be installed on your Web host, but you can’t just put them both at your main domain name \u2013 if you did, both sites would quickly experience conflicts and errors. You need to cordon off separate spaces for your different Web \u201cproperties.\u201d<\/p>\n\n\n\n

There are two primary strategies for parceling up your Web space. You can create subdomains<\/strong> or subdirectories<\/strong>. But before you can understand the difference, you need to first understand what we mean when we talk about your root<\/strong> domain.<\/p>\n\n\n\n

Root Domain<\/h4>\n\n\n\n

Let’s say you’ve registered a new domain for knight.domains called blog.knight.domains. Anything that is stored at this core\u00a0URL\u00a0is considered to be at the\u00a0root<\/strong>\u00a0of your domain. Nothing comes before the address or after the address. You can certainly decide that you simply want to have a single site on your Web host (say a blog running WordPress), and you can set that blog up at your domain’s root. To get to your site in this scenario, users would simply go to blog.knight.domains.<\/p>\n\n\n\n

Subdomains<\/h4>\n\n\n\n

When you want to do more than just have a single site at the root of your site, you need to decide now to organize your space. One way to do so is by setting up\u00a0subdomains<\/strong><\/a>.<\/p>\n\n\n\n

You’re may already be familiar with the concept of subdomains, even if you don’t know it. Consider Google’s website at https:\/\/google.com<\/a>. As you browse features of that site, you\u2019ll notice that the domain changes. When you\u2019re looking at your Gmail account, for example, the domain changes to https:\/\/mail.google.com<\/a>. Now the root of the url is mail.google.com, indicating that you\u2019re on the part of the site that is dedicated to Google’s mail services.<\/p>\n\n\n\n

In this instance, mail.google.com is a subdomain that provides a different utility than google.com. The domains serve two purposes: they help to organize the site from a technical perspective, but they also serve as indications to the users that they are in a new\/different space.<\/p>\n\n\n\n

As you work on your site, you’re welcome to create as many subdomains as you like, and in each subdomain you can actually create a distinct, individual Web site.<\/p>\n\n\n\n

Subdirectories<\/h4>\n\n\n\n

The alternative for organizing your space is to simply set up subdirectories. These function much like file folders on your computer. Instead of creating a blog at blog.yourdomain.com<\/strong> you would place it in a subdirectory called \u201cblog\u201d making the address yourdomain.com\/blog<\/strong>. Setting up subdirectory is really easy. You can create folders on the fly when installing applications (like WordPress), and you can also manually create them in your file browser.<\/p>\n\n\n\n

There is one particular issue you need to be aware of: Let’s say you’ve installed WordPress to be your primary blog at yourdomain.com<\/strong>. Later, you decide you want to install WordPress again for a separate image gallery site, and you want to place it at yourdomain.com\/gallery<\/strong>. But, if for some reason you’ve already created a page on your WordPress site called \u201cGallery\u201d then the url yourdomain.com\/gallery<\/strong> will already be taken. If you try to create a subdirectory of the same name, you’ll get a conflict and errors.<\/p>\n\n\n\n

Tips & Review<\/h4>\n\n\n\n