So, to recount:
This entry-point is also called an “index”, much like an index in a book. Keep in mind the fact that the web is/was made for and of documents, which is why an index of web-pages is needed.
Now, of course it would be inefficient to number webpages on your website as
then tell your customers to find your shop/business phone number or address on Page 2. What we do instead is take advantage of hypertext, a website is made up of web pages and each and every web page is a document - a single file, just like the index is.
In our case (with WAMPP) the website index in the
is an actual index.html file.
If click a link (or manually navigate) to
what you are doing is you are instructing the browser to obtain resources at this “http://localhost/pages/advertisement/create.htm” identifier - the (U)niform ®resource (I)dentifier, also known as the (U)niform ®esource (L)ocation/(L)ocator.
The browser then relays the URI to the server, who in turn takes “http://localhost/pages/advertisement/create.htm” and separates it into
http:// (the scheme (the (h)yper(t)ext (t)ransfer (p)rotocol)) localhost (the host/domain, google.com for google, wikipedia.org for wikipedia, etc) pages/ (file (or in our case a directory) by the name “pages” sitting at server root) advertisement (file (or in our case a directory) by the name advertisement sitting within the “pages” directory) create.htm (file (or in our case a file) by the name create.htm sitting within the advertisement directory)
Lastest part, create.htm is an actual file that the server reads and relays contents of to the browser. If we had a description.txt file right next to create.htm, navigating the URI of
would read the contents (state, remember) of the description.txt file and send it back to the browser, letting you read it.