Creating websites are as simple as creating any other directory on a computer. The website directory is no more than a shared directory to which the public may have access. Thus, if you want to manually make a new website, it's just a matter of creating a directory with the name of your new site.
Of course the files in a website directory won't run by themselves. There is server side software, Apache in our case, to do what it takes to send the files in your website directory out into the wilds. When a request comes in to see what's in the directory, it comes in as an URL, which is suspiciously the same as a directory path with .html appended to the end. LOL It's really a simple concept and you have worked with it many times, I'm sure.
The image I posted is the root directory for my account on our Linux web server to which I have ftp access. My screen wasn't large enough to capture all the single files at the bottom, but you get the idea. The name of this directory is hidden, but I know it happens to be my account number. You will note that my account has both perl and php software installed as well as mail. The database is on some other server, I presume, and I need to use an SQL control panel to get at it. What you see here, this website, is in the highlighted directory called public_html. Therein is another list of directories similar to the one in the image and includes our website directory.
brainformation.com has an IP address of 216.85.168.253 which is all recorded in various DNS servers throughout the world. That IP address will get you to the root of public_html which has only one webpage in it: our portal. The address you type into the browser to get here is
http://bfchat.brainformation.com and it points to the bfchat folder. That is a subdomain of brainformation.com. I have three others, each of which sports it's own website. It's the subdomains that brings sanity to this place. LOL I could put all four into the same root directory of brainformation.com, but that would be a nightmare to maintain. I have enough trouble keeping this single subdomain up to date.
So, you could actually roam about the bfchat subdomain directory with an ftp client. I don't think you can get into it's parent, and certainly you will not ever get to the directory in that image. It's all a matter of permissions and that ubiquitous .htaccess file. The pictured directory, my account, is one of dozens similar to it on that server. I do not have permission to see the parent directory contents from my desktop, but there are websites that will list all the other websites hosted on that server. Not sure how they do that, but it can't be too difficult.
In your case the parent directory (domain name) for your websites is classichauslimited. That's the equivalent to my public_html directory. classichauslimited has a sub-directory called roaringfalls, thus it would have a directory path of ~classichauslimited/roaringfalls. Apparently roaringfalls is in reality a subdoman of classichouslimited. Thus the convention of stating the subdomain ahead of the parent separated by a dot roaringfalls . classichauslimited. If you look at the URL for this forum you will see the same naming convention bfchat . brainformation, meaning bfchat is a subdirectory of brainformation.
simple, eh?
![Mr Green :mrgreen:](./images/smilies/MRgreen.gif)