One of the articles I was reading didn't include the ./ when linking to a local file.
should you use it? Not perse, but you could argue its more explicit to look for the file in the current directory.
Do we need the dot - ./about.html
Can we use /about.html without the dot.
The dot represent the current directory, it can be without but then it becomes
/about.html would mean looking in the root directory.
What if I save these html files in different folder??
then you would have to change the path to something like
Does it matter if you search in the route directory? I tried it without ./ and used / and nothing different happened.
On our local machine we need to be mindful of where our code is located with respect to the root directory, or volume root,
C:\. For instance,
/ => C:\
On a web server,
/ is the site root, as in where the home page is located. A web server is configured to domain roots and is able to map its drive to serve the sites it hosts.
Within a site,
/ is the same as,
http://www.domain.tld. Say we have the domain,
example.com, then we can, within our site’s pages refer to the home page with that simple forward slash. It would be the same thing to the server as,
The absolute forward slash is the reference to the site root. Any folders we have there can be got to directly…
/css/ /js/ /images/ /pdf/
Now as eloquent as that is, we don’t have the same luxury on our local machine. In most cases our content is nicely tucked away in user folders. Consider if we were to have an IDE that gave us user content space within its own file structure. Where would that folder be relative to the volume root? A long ways off, to be sure. There will be several folder layers to traverse through to find your code. The IDE is probably able to map the site root for your local project in an effort to keep us from traversing the outward tree in which it is contained.
Toss the IDE, for now. How do we emulate web server behavior in our local site project? Answer: relative path addressing.
absolute path => begins at site root up to resource relative path => traverses backward from request
Bottom line, use relative path and memorize the site architecture so you instantly know how many levels to jump back to access folders from where that resource is located in the site volume.
site/ + css/ + level1/ + level2/ + level3/
On the site root, the path to the css folder will be,
On level1 it will be,
On level2 it will be,
On level3 it will be,
It may seem an inconvenience but sure saves us a bother on our local machine if we are working directly with HTML, a site project, and using a conventional text editor that can only launch in a browser, rather an IDE mapped environment.
Don’t rush out and buy an expensive IDE until you are prepared to make a living at this craft. You really don’t need it to get an adequate learning experience. IDEs are about work flow and when that becomes an actual concern, you will be fully able to transition into that environment if you grind your way through this local machine site project model.
When a person and a computer are in the same room, there is only one brain present. Computers are dumb. Sure they may be powerful, but they only know how to do what we tell them. Document traversal is a fundamental process of a disk operating system. Explore the DOS in terms of history and command line and everything said above is reduced to its real simplicity.
Thank you so much for responding!