There are several ways to link to pages on the internet as well as to content and resources within a Drupal system. Pages, images and media can be linked to by means of absolute URLs, absolute paths, relative paths, node ids, or even special syntax provided by various Drupal modules. All are based in full or in part on the URL used to locate the resource. For our purposes, a URL is typically some version of the format: protocol://domain/path?query_string#fragment_id.

Thoughts?

"I recently read an article that does a great injustice to the practical implementation of the Agile process in software development. In an attempt to describe the Agile process, the author of this article, apparently the "Head of the Software Development Department", inadvertently described exactly how NOT to do it. This person actually said, "If it was possible to construct a home using the Agile approach, one could go into the kitchen on the second floor of the house under construction and look out the window, even before all the walls were installed on the ground level.

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

To understand the core challenge in deploying updated Drupal releases first we need to consider what makes up a Drupal website. A Drupal website like any web application, in simplest terms, consists of a set of files and a database. The set of files includes, but isn't limited to, image files, text files, php files, style sheets, and java script files, just to name a few.